linux-kernel - Re: [PATCH] [5/5] kbuild: Set -fconserve-stack option for gcc 4.5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090914143615.9ee47a1a.akpm@linux-foundation.org>
Date:	Mon, 14 Sep 2009 14:36:15 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org, sam@...nborg.org
Subject: Re: [PATCH] [5/5] kbuild: Set -fconserve-stack option for gcc 4.5

On Mon, 14 Sep 2009 22:18:11 +0200 (CEST)
Andi Kleen <andi@...stfloor.org> wrote:

> 
> The upcomming gcc 4.5 has a new -fconserve-stack option 
> that tells the inliner to take stack frame size in account.
> Set it if the compiler supports it.
> 
> Signed-off-by: Andi Kleen <ak@...ux.intel.com>
> 
> ---
>  Makefile |    3 +++
>  1 file changed, 3 insertions(+)
> 
> Index: linux-2.6.31-rc3-ak/Makefile
> ===================================================================
> --- linux-2.6.31-rc3-ak.orig/Makefile
> +++ linux-2.6.31-rc3-ak/Makefile
> @@ -575,6 +575,9 @@ KBUILD_CFLAGS	+= $(call cc-option,-fno-s
>  # revert to pre-gcc-4.4 behaviour of .eh_frame
>  KBUILD_CFLAGS	+= $(call cc-option,-fno-dwarf2-cfi-asm)
>  
> +# conserve stack if available
> +KBUILD_CFLAGS   += $(call cc-option,-fconserve-stack)

Do we have any info about what effects this option has upon the
generated code?  Text size changes, runtime stack usage changes, etc?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/