public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pnewell at cs dot cmu.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/51391] pragma GCC diag ignored then warning of Winline activates -fno-inline
Date: Sat, 03 Dec 2011 03:29:00 -0000	[thread overview]
Message-ID: <bug-51391-4-pHgTlcAKOn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51391-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from pnewell at cs dot cmu.edu 2011-12-03 03:29:03 UTC ---
I just tested on my Linux box and I am getting the results you suggest for -O2
and -O3. It is finding issues with -O, -Os, and -O1, but I think that is my
problem (barking on the inlined destructor).

However, -O0 still gives me the -fno-inline warnings

I just got your email about "Because there is code to explicitly turn off the
warning for -O0 but not when using the pragma". I've never seen any
documentation about the pragma GCC diagnostic warning having different actions
than just on the compile line. Is there any more info on this?

Please pardon my questioning this, but does that seem right? I would expect
same behavior between a compile line -Winline and a pragma in the code stating
"#pragma GCC diagnostic warning "-Winline"?

Thanks,
Paul


  parent reply	other threads:[~2011-12-03  3:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-03  3:09 [Bug preprocessor/51391] New: " pnewell at cs dot cmu.edu
2011-12-03  3:10 ` [Bug preprocessor/51391] " pnewell at cs dot cmu.edu
2011-12-03  3:10 ` pnewell at cs dot cmu.edu
2011-12-03  3:11 ` pnewell at cs dot cmu.edu
2011-12-03  3:14 ` pinskia at gcc dot gnu.org
2011-12-03  3:14 ` pnewell at cs dot cmu.edu
2011-12-03  3:16 ` pinskia at gcc dot gnu.org
2011-12-03  3:19 ` pnewell at cs dot cmu.edu
2011-12-03  3:24 ` pinskia at gcc dot gnu.org
2011-12-03  3:29 ` pnewell at cs dot cmu.edu [this message]
2011-12-03  3:31 ` pnewell at cs dot cmu.edu
2011-12-03  3:33 ` pinskia at gcc dot gnu.org
2011-12-03  3:37 ` pnewell at cs dot cmu.edu
2011-12-03 11:00 ` [Bug c/51391] Differences between setting Winline in command-line and through pragma GCC diagnostic manu at gcc dot gnu.org
2011-12-03 11:05 ` manu at gcc dot gnu.org
2011-12-03 19:11 ` pnewell at cs dot cmu.edu
2011-12-05  9:50 ` rguenth at gcc dot gnu.org
2011-12-06  8:00 ` pnewell at cs dot cmu.edu
2021-09-17  7:56 ` [Bug middle-end/51391] " pnewell0705 at gmail dot com
2021-09-17  7:57 ` pnewell0705 at gmail dot com
2021-09-17  8:05 ` pinskia at gcc dot gnu.org
2021-09-17  8:08 ` pnewell0705 at gmail dot com
2021-09-17  8:27 ` pinskia at gcc dot gnu.org
2021-09-17  8:56 ` pnewell0705 at gmail dot com

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-51391-4-pHgTlcAKOn@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).