public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cgd at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/48088] New: -Werror=frame-larger-than=100 does not work as expected
Date: Sat, 12 Mar 2011 07:25:00 -0000	[thread overview]
Message-ID: <bug-48088-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: -Werror=frame-larger-than=100 does not work as
                    expected
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: cgd@google.com


the gcc manual says:

Note that specifying @option{-Werror=}@var{foo} automatically implies
@option{-W}@var{foo}.  However, @option{-Wno-error=}@var{foo} does not
imply anything.

That's easily understood to mean that, for instance:
   -Werror=frame-larger-than=500
implies
   -Wframe-larger-than=500

however, it doesn't.  it seems to imply -Wframe-larger-than=1.

Worse, -Werror=frame-larger-than= clobbers any previous -Wframe-larger-than=
value.


/tmp/x.c:
int x() {
  int x[5];
}


$ gcc-svn/inst/bin/gcc -Wframe-larger-than=100 /tmp/x.c -c
$ 

-> OK, the frame is smaller than 100.


$ gcc-svn/inst/bin/gcc -Werror=frame-larger-than=100 /tmp/x.c -c
/tmp/x.c: In function 'x':
/tmp/x.c:3:1: error: the frame size of 32 bytes is larger than 1 bytes
[-Werror=frame-larger-than=]
cc1: some warnings being treated as errors

$ 

-> OK, that's kinda odd.


$ gcc-svn/inst/bin/gcc -Wframe-larger-than=100 -Werror=frame-larger-than=100
/tmp/x.c -c
/tmp/x.c: In function 'x':
/tmp/x.c:3:1: error: the frame size of 32 bytes is larger than 1 bytes
[-Werror=frame-larger-than=]
cc1: some warnings being treated as errors

$ 

-> eh?


$ gcc-svn/inst/bin/gcc -Wframe-larger-than=100 -Werror=frame-larger-than=
/tmp/x.c -c
/tmp/x.c: In function 'x':
/tmp/x.c:3:1: error: the frame size of 32 bytes is larger than 1 bytes
[-Werror=frame-larger-than=]
cc1: some warnings being treated as errors

$ 

-> eh?


$ gcc-svn/inst/bin/gcc -Werror=frame-larger-than= -Wframe-larger-than=100
/tmp/x.c -c
$ 

-> order apparently matters.


             reply	other threads:[~2011-03-12  7:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12  7:25 cgd at google dot com [this message]
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
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@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).