All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: hpa@zytor.com, linux-kernel@vger.kernel.org, tglx@linutronix.de,
	hpa@linux.intel.com, kevin.b.smith@intel.com,
	hjl.tools@gmail.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86-64, build: Always pass in -mno-sse
Date: Wed, 4 Dec 2013 09:54:48 +0100	[thread overview]
Message-ID: <20131204085448.GA31778@gmail.com> (raw)
In-Reply-To: <tip-j21wzqv790q834n7yc6g80j1@git.kernel.org>


* tip-bot for H. Peter Anvin <tipbot@zytor.com> wrote:

> Commit-ID:  5551a34e5aeab868f8d37f70d8754868921b4ee5
> Gitweb:     http://git.kernel.org/tip/5551a34e5aeab868f8d37f70d8754868921b4ee5
> Author:     H. Peter Anvin <hpa@linux.intel.com>
> AuthorDate: Wed, 20 Nov 2013 13:31:49 -0800
> Committer:  H. Peter Anvin <hpa@linux.intel.com>
> CommitDate: Tue, 3 Dec 2013 17:40:22 -0800
> 
> x86-64, build: Always pass in -mno-sse
> 
> Always pass in the -mno-sse argument, regardless if
> -preferred-stack-boundary is supported.  We never want to generate SSE
> instructions in the kernel unless we *really* know what we're doing.
> 
> According to H. J. Lu, any version of gcc new enough that we support
> it at all should handle the -mno-sse option, so just add it
> unconditionally.
> 
> Reported-by: Kevin B. Smith <kevin.b.smith@intel.com>
> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
> Cc: H. J. Lu <hjl.tools@gmail.com>
> Link: http://lkml.kernel.org/n/tip-j21wzqv790q834n7yc6g80j1@git.kernel.org
> Cc: <stable@vger.kernel.org> # build fix only
> ---
>  arch/x86/Makefile | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/Makefile b/arch/x86/Makefile
> index 41250fb..eda00f9 100644
> --- a/arch/x86/Makefile
> +++ b/arch/x86/Makefile
> @@ -31,6 +31,9 @@ ifeq ($(CONFIG_X86_32),y)
>  
>          KBUILD_CFLAGS += -msoft-float -mregparm=3 -freg-struct-return
>  
> +        # Don't autogenerate SSE instructions
> +	KBUILD_CFLAGS += -mno-sse
> +
>          # Never want PIC in a 32-bit kernel, prevent breakage with GCC built
>          # with nonstandard options
>          KBUILD_CFLAGS += -fno-pic
> @@ -57,8 +60,11 @@ else
>          KBUILD_AFLAGS += -m64
>          KBUILD_CFLAGS += -m64
>  
> +        # Don't autogenerate SSE instructions
> +	KBUILD_CFLAGS += -mno-sse
> +
>  	# Use -mpreferred-stack-boundary=3 if supported.
> -	KBUILD_CFLAGS += $(call cc-option,-mno-sse -mpreferred-stack-boundary=3)
> +	KBUILD_CFLAGS += $(call cc-option,-mpreferred-stack-boundary=3)
>  
>          # FIXME - should be integrated in Makefile.cpu (Makefile_32.cpu)
>          cflags-$(CONFIG_MK8) += $(call cc-option,-march=k8)

Just a detail I noticed: in kbuild we intentionally use 8 spaces for 
tabs in Makefiles and only use tabs for commands where tabs are 
required.

The above code introduces tabs in the middle of 8-space sequences. It 
works but is inconsistent.

Thanks,

	Ingo

  reply	other threads:[~2013-12-04  8:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04  1:42 [tip:x86/urgent] x86-64, build: Always pass in -mno-sse tip-bot for H. Peter Anvin
2013-12-04  8:54 ` Ingo Molnar [this message]
2013-12-04 15:31   ` H. Peter Anvin
2013-12-04 15:37     ` Ingo Molnar

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=20131204085448.GA31778@gmail.com \
    --to=mingo@kernel.org \
    --cc=hjl.tools@gmail.com \
    --cc=hpa@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kevin.b.smith@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.