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] New: pragma GCC diag ignored then warning of Winline activates -fno-inline
Date: Sat, 03 Dec 2011 03:09:00 -0000	[thread overview]
Message-ID: <bug-51391-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51391
           Summary: pragma GCC diag ignored then warning of Winline
                    activates -fno-inline
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: preprocessor
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: pnewell@cs.cmu.edu


In the test program I will be submitting after the bug is in bugzilla, I am
using -Winline with g++ -g. Everything works until I try to disable the check
in a file with #pragma GCC diagnostic {ignored,warning} "-Winline" ... then it
complains that it can't inline as -fno-inline is active ... which it isn't (per
what I can see).

The two files I have included are inlineBug.cpp and inlineBug.h. The offending
pragmas are in inlineBug.cpp. I am sending the file with them active. I think
the problem is with the second one as it seems that it doesn't matter whether I
ask it to ignore, its the re-activation as warning that seems to do it.

The command I am using to compile is: g++ -g -Winline -o inlineBug
inlineBug.cpp

I have also attached the output of a bad make/build

This is being run on a Fedora14 x86_64 system with their latest yum update of
4.5.1 which g++ -v give as "gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC)"

As this is the first bug I have submitted to gcc bugzilla, please let me know
if I have forgotten anything that I need to tell you.

And, of course, let me know if I can run any more tests to help resolve this
(assuming that it is a bug and not already fixed -- I didn't see anything when
searching under "Winline fno-inline")

Thanks,
Paul


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

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-03  3:09 pnewell at cs dot cmu.edu [this message]
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
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@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).