public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/48088] -Werror=frame-larger-than=100 does not work as expected
Date: Tue, 15 Mar 2011 09:34:00 -0000	[thread overview]
Message-ID: <bug-48088-4-o5dJBimQ1d@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48088-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48088

--- Comment #4 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2011-03-15 09:20:47 UTC ---
(In reply to comment #3)
> (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-)

These are indeed several bugs related to not handling W options with parameters
properly. Check in options.c (enable_warning_as_error) for how -Werror=option
is handled and...

> /tmp/x.c:3:1: error: the frame size of 32 bytes is larger than 1 bytes
> [-Werror=frame-larger-than=]

diagnostics.c for how this is printed. This should print
-Werror=frame-larger-than=1 (without -Werror, does it print
[-Wframe-larger-than=1]) ?

I guess similar problems arise with Wlarger-than=, Woverflow= and
Wstrict-aliasing= (but perhaps the two latter are handled differently).

Fixing it should be fairly trivial.


  parent reply	other threads:[~2011-03-15  9:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12  7:25 [Bug c/48088] New: " cgd at google dot com
2011-03-12 13:45 ` [Bug c/48088] " manu at gcc dot gnu.org
2011-03-14 10:30 ` rguenth at gcc dot gnu.org
2011-03-14 22:56 ` cgd at google dot com
2011-03-15  9:34 ` manu at gcc dot gnu.org [this message]
2013-05-24 14:18 ` slyfox at inbox dot ru
2013-05-27 11:37 ` manu at gcc dot gnu.org

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=bug-48088-4-o5dJBimQ1d@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).