This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/48088] -Werror=frame-larger-than=100 does not work as expected
- From: "cgd at google dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 14 Mar 2011 22:56:17 +0000
- Subject: [Bug c/48088] -Werror=frame-larger-than=100 does not work as expected
- Auto-submitted: auto-generated
- References: <bug-48088-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48088
--- Comment #3 from Chris Demetriou <cgd at google dot com> 2011-03-14 22:56:06 UTC ---
(In reply to comment #2)
> Yeah. Confirmed.
>
> You need -Wframe-larger-than=500 -Werror=frame-larger-than which hopefully
> doesn't reset the value to 1.
It doesn't, but not for the reason you would hope. 8-)
[cgd@cgda gcc-svn]$ inst/bin/gcc --version | head -1
gcc (GCC) 4.6.0 20110311 (experimental)
[cgd@cgda gcc-svn]$ inst/bin/gcc -Wframe-larger-than=500
-Werror=frame-larger-than -c /tmp/x.c
cc1: error: -Werror=frame-larger-than: no option -Wframe-larger-than
IMO this suggestion disagrees with my reading of the usage -Werror in the
manual (before or my after my recent change), and also disagrees with the
warning name output by -fdiagnostics-show-option:
/tmp/x.c:3:1: error: the frame size of 32 bytes is larger than 1 bytes
[-Werror=frame-larger-than=]
[note that this compiler is a few days old -- my assumption is that this
behaviour didn't change since then, given the relative lockdown of GCC sources
in prep for the 4.6 branch. Sorry if my assumption was incorrect.]