From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7199 invoked by alias); 15 Mar 2011 09:21:07 -0000 Received: (qmail 7191 invoked by uid 22791); 15 Mar 2011 09:21:07 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 15 Mar 2011 09:21:02 +0000 From: "manu at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/48088] -Werror=frame-larger-than=100 does not work as expected X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: manu at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Date: Tue, 15 Mar 2011 09:34:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-03/txt/msg01516.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D48088 --- Comment #4 from Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez 2011-03-15 09:20:47 UTC --- (In reply to comment #3) > (In reply to comment #2) > > Yeah. Confirmed. > >=20 > > You need -Wframe-larger-than=3D500 -Werror=3Dframe-larger-than which ho= pefully > > doesn't reset the value to 1. >=20 > It doesn't, but not for the reason you would hope. 8-) These are indeed several bugs related to not handling W options with parame= ters properly. Check in options.c (enable_warning_as_error) for how -Werror=3Dop= tion is handled and... > /tmp/x.c:3:1: error: the frame size of 32 bytes is larger than 1 bytes > [-Werror=3Dframe-larger-than=3D] diagnostics.c for how this is printed. This should print -Werror=3Dframe-larger-than=3D1 (without -Werror, does it print [-Wframe-larger-than=3D1]) ? I guess similar problems arise with Wlarger-than=3D, Woverflow=3D and Wstrict-aliasing=3D (but perhaps the two latter are handled differently). Fixing it should be fairly trivial.