public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "magnus.reftel at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/56824] [4.8/4.9 regression] pragma GCC diagnostic push/pop fail with GCC diagnostic ignored "-Waggregate-return"
Date: Fri, 07 Feb 2014 07:03:00 -0000	[thread overview]
Message-ID: <bug-56824-4-u77jreBUsv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56824-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Magnus Reftel <magnus.reftel at gmail dot com> ---
Thanks for the patch! I applied it on top of
53c3c39b96df9c6a6368bf0d6acfd28a7af3cb63 and tested.

Without the patch, the error was still printed when compiling the testcase.
With the patch, the error was not printed. Removing the "#pragma GCC diagnostic
ignored" made the error print again, as expected. The fix is thus working as it
should on the testcase. I no longer have access to the code base where the
problem was discovered, so I guess this verification will have to do.

I'm not sure what the criteria for updating the status field are, though, so I
leave it at "ASSIGNED".


  parent reply	other threads:[~2014-02-07  7:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03  7:40 [Bug c/56824] New: pragma GCC diagnostic push/pop regression for " magnus.reftel at gmail dot com
2013-04-10  8:10 ` [Bug c/56824] " magnus.reftel at gmail dot com
2013-04-10 18:32 ` manu at gcc dot gnu.org
2013-04-12  7:42 ` magnus.reftel at gmail dot com
2013-04-12  9:12 ` manu at gcc dot gnu.org
2013-08-08 18:37 ` magnus.reftel at gmail dot com
2013-08-10 16:14 ` mikpe at it dot uu.se
2013-11-19  9:46 ` [Bug c/56824] [4.8/4.9 regression] pragma GCC diagnostic push/pop fail with " rguenth at gcc dot gnu.org
2013-11-22 10:45 ` rguenth at gcc dot gnu.org
2014-02-05 14:15 ` [Bug preprocessor/56824] " jakub at gcc dot gnu.org
2014-02-07  7:03 ` magnus.reftel at gmail dot com [this message]
2014-02-07 16:43 ` jakub at gcc dot gnu.org
2014-02-08  0:10 ` [Bug preprocessor/56824] [4.8 " jakub at gcc dot gnu.org
2014-02-10 15:56 ` magnus.reftel at gmail dot com
2014-03-06  7:58 ` jakub at gcc dot gnu.org
2014-03-06  8:27 ` jakub 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-56824-4-u77jreBUsv@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).