public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66966] Missing diagnostic message for ill-formed program with anonymous enum Date: Wed, 22 Jul 2015 15:07:00 -0000 [thread overview] Message-ID: <bug-66966-4-mJRfnynYrI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66966-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66966 --- Comment #8 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Anders Granlund from comment #7) > OK. Seems to work differently in Clang but I guess they don't have the same > problem with legacy. Changing defaults in GCC to match Clang is possible (we added caret, colors, changed the behavior of https://gcc.gnu.org/wiki/FAQ#wnowarning), but someone who thinks this is important enough needs to make the effort of implementing the change, arguing convincingly for it and handling any issues that may arise. The change is likely to be just splitting diagnostic_report_warnings_p so that the check for inhibit_warnings in diagnostic.c:diagnostic_report_diagnostic() can be moved after diagnostic->kind is reclassified while keeping the check for system-headers as early as possible, so that warnings from system-headers converted into errors are still suppressed. >From gcc-bugs-return-493031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 22 15:13:53 2015 Return-Path: <gcc-bugs-return-493031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 6265 invoked by alias); 22 Jul 2015 15:13:53 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 6218 invoked by uid 48); 22 Jul 2015 15:13:49 -0000 From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66731] vnmul, fnmul patterns incorrect for -frounding-math Date: Wed, 22 Jul 2015 15:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: ramana at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: nsz at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed Message-ID: <bug-66731-4-Uu0C43TUWm@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-66731-4@http.gcc.gnu.org/bugzilla/> References: <bug-66731-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-07/txt/msg01921.txt.bz2 Content-length: 568 https://gcc.gnu.org/bugzilla/show_bug.cgi?idf731 Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-07-22 CC| |ramana at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #3 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> --- Confirmed.
prev parent reply other threads:[~2015-07-22 15:07 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-22 11:32 [Bug c++/66966] New: " anders.granlund.0 at gmail dot com 2015-07-22 11:42 ` [Bug c++/66966] " redi at gcc dot gnu.org 2015-07-22 11:44 ` redi at gcc dot gnu.org 2015-07-22 11:45 ` anders.granlund.0 at gmail dot com 2015-07-22 11:49 ` anders.granlund.0 at gmail dot com 2015-07-22 12:25 ` anders.granlund.0 at gmail dot com 2015-07-22 14:16 ` manu at gcc dot gnu.org 2015-07-22 14:43 ` anders.granlund.0 at gmail dot com 2015-07-22 15:07 ` manu at gcc dot gnu.org [this message]
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-66966-4-mJRfnynYrI@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).