Commit:     c8fdd247255a3a027cd9f66dcf93e6847d1d2f85
Parent:     2a12652c0335ec90747d3402a82b6699ae883b58
Author:     Andi Kleen <[EMAIL PROTECTED]>
AuthorDate: Wed May 2 19:27:06 2007 +0200
Committer:  Andi Kleen <[EMAIL PROTECTED]>
CommitDate: Wed May 2 19:27:06 2007 +0200

    [PATCH] x86: Drop cc-options call for all options supported in gcc 3.2+
    The kernel only supports gcc 3.2+ now so it doesn't make sense
    anymore to explicitely check for options this compiler version
    already has.
    This actually fixes a bug. The -mprefered-stack-boundary check
    never worked because gcc rightly complains
      CC      arch/i386/kernel/asm-offsets.s
    cc1: -mpreferred-stack-boundary=2 is not between 4 and 12
    We just never saw the error because of cc-options.
    I changed it to 4 to actually work.
    Tested by compiling i386 and x86-64 defconfig with gcc 3.2.
    Should speed up the build time a tiny bit and improve
    stack usage on i386 slightly.
    Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
 Makefile           |    2 +-
 arch/i386/Makefile |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Makefile b/Makefile
index d970cb1..387526b 100644
--- a/Makefile
+++ b/Makefile
@@ -491,7 +491,7 @@ endif
 include $(srctree)/arch/$(ARCH)/Makefile
-CFLAGS         += -fno-omit-frame-pointer $(call 
+CFLAGS         += -fno-omit-frame-pointer -fno-optimize-sibling-calls
 CFLAGS         += -fomit-frame-pointer
diff --git a/arch/i386/Makefile b/arch/i386/Makefile
index bd28f9f..6dc5e5d 100644
--- a/arch/i386/Makefile
+++ b/arch/i386/Makefile
@@ -34,7 +34,7 @@ CHECKFLAGS    += -D__i386__
 CFLAGS += -pipe -msoft-float -mregparm=3 -freg-struct-return
 # prevent gcc from keeping the stack 16 byte aligned
-CFLAGS += $(call cc-option,-mpreferred-stack-boundary=2)
+CFLAGS += -mpreferred-stack-boundary=4
 # CPU-specific tuning. Anything which can be shared with UML should go here.
 include $(srctree)/arch/i386/Makefile.cpu
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to