From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Denys Vlasenko <dvlasenk@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jan Kara <jack@suse.cz>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH resend] x86: Fix detection of GCC -mpreferred-stack-boundary support
Date: Wed, 22 Jul 2015 10:04:36 +0200 [thread overview]
Message-ID: <20150722080436.GE7979@nazgul.tnic> (raw)
In-Reply-To: <f5297c192969adfa0d28b84cf8a22d59573db26d.1436126872.git.luto@kernel.org>
On Tue, Jul 21, 2015 at 09:27:18AM -0700, Andy Lutomirski wrote:
> +# prevent gcc from generating any FP code by mistake
> +# This must be before we try -mpreferred-stack-boundary -- see
> +# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53383
> +KBUILD_CFLAGS += -mno-sse -mno-mmx -mno-sse2 -mno-3dnow
> +KBUILD_CFLAGS += $(call cc-option,-mno-avx,)
Should we unify all FPU-generating switches to one place? I've added
this
# Don't autogenerate traditional x87 instructions
KBUILD_CFLAGS += $(call cc-option,-mno-80387)
KBUILD_CFLAGS += $(call cc-option,-mno-fp-ret-in-387)
to the 64-bit build a while back but I don't see why it shouldn't be in
the generic part of the Makefile...
Also, 32-bit has -msoft-float which, according to the gcc manpage is
ignored but I guess should be kept for older gccs...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-07-22 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 16:27 Andy Lutomirski
2015-07-22 8:04 ` Borislav Petkov [this message]
2015-07-27 15:51 ` [tip:x86/asm] x86/build: " tip-bot for Andy Lutomirski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150722080436.GE7979@nazgul.tnic \
--to=bp@alien8.de \
--cc=dvlasenk@redhat.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®