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 c/51391] Differences between setting Winline in command-line and through pragma GCC diagnostic Date: Sat, 03 Dec 2011 19:11:00 -0000 [thread overview] Message-ID: <bug-51391-4-VM0Y7teR39@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 #15 from pnewell at cs dot cmu.edu 2011-12-03 19:10:39 UTC --- Manu: Yes, Andrew did a great job of letting me know what the issue was and gave me the necessary information to have a work-around within 1/2 hour. Fantastic turnaround in my book, many thanks to him! I appreciate the confirm that it is a bug. I can also believe that if they go through different code paths there is a good chance there are more of these "opps" situations. I'd rather not use #pragmas, but with third party code it becomes necessary to get rid of all the warnings one can't do anything about (except tell the third party ... and that hasn't produced any results yet). I am not surprised that the fix is quick but the build/testing makes it a bit of a question whether someone is going to want to do all that legwork. It isn't exactly a show-stopper (smile) and, since I am stuck on F14 until spring of 2012, I wouldn't be able to make use of the patch until I upgrade. But the fix is there (thanks) and I'll just see what happens. Mostly, I wanted to tell both Andrew and you that I very impressed with how this bug was handled. A very prompt response, solid info on what the issue is, and an honest assessment of its chances for fixing. This is the first bug I have submitted to gcc bugzilla and I certainly feel that it was worth the effort for me to package up an example to send to you. Thanks, Paul
next prev parent reply other threads:[~2011-12-03 19:11 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-03 3:09 [Bug preprocessor/51391] New: pragma GCC diag ignored then warning of Winline activates -fno-inline 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 ` pnewell at cs dot cmu.edu 2011-12-03 3:14 ` pinskia at gcc dot gnu.org 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 [this message] 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-VM0Y7teR39@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: linkBe 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).