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 middle-end/48087] [4.5/4.6/4.7 Regression] -Wall -Werror adds warnings over and above those generated by -Wall Date: Wed, 19 Oct 2011 17:24:00 -0000 [thread overview] Message-ID: <bug-48087-4-U8qwgso4VI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48087-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48087 --- Comment #16 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2011-10-19 17:21:51 UTC --- (In reply to comment #15) > On this PR, removing the early return *works*, we have two non-bogus warnings > with -Wall and two errors with -Werror. Maybe we should really proceed one PR > at a time, re-open PR49508. I agree. This is what I meant by (2) above. That the bogus warnings are somehow hidden by gimple_push_cleanup, but it would be better to figure what gimple_push_clenaup is fixing and see whether it is possible to avoid generating it in the first place. If it is the same issue as PR49508, then fixing (1) is not enough. > Now, in detail: do I understand correctly that you are proposing we would use > the new seen_real_errors *only* in gimple_push_cleanup? (at the moment I also > honestly don't know how to tell errors from warnings from real errors, but of > course can figure out myself) I would search where the counters are defined and add a new one for real_errors. Then, for warnings converted to errors, do not increase the new one. This should be a one-liner in diagnostic_report_diagnostic. Search for diagnostic_kind_count. This would maintain seen_error working as it is now, but one can define program_is_valid_p (or seen_real_error).
next prev parent reply other threads:[~2011-10-19 17:24 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-12 6:21 [Bug c++/48087] New: " cgd at google dot com 2011-10-18 0:54 ` [Bug c++/48087] " paolo.carlini at oracle dot com 2011-10-18 1:19 ` paolo.carlini at oracle dot com 2011-10-18 1:22 ` paolo.carlini at oracle dot com 2011-10-18 1:30 ` [Bug middle-end/48087] [4.5/4.6/4.7 Regression] " paolo.carlini at oracle dot com 2011-10-18 8:26 ` rguenther at suse dot de 2011-10-18 9:42 ` paolo.carlini at oracle dot com 2011-10-18 15:44 ` manu at gcc dot gnu.org 2011-10-18 16:03 ` paolo.carlini at oracle dot com 2011-10-18 16:10 ` paolo.carlini at oracle dot com 2011-10-18 20:23 ` manu at gcc dot gnu.org 2011-10-18 23:42 ` paolo.carlini at oracle dot com 2011-10-19 1:44 ` manu at gcc dot gnu.org 2011-10-19 7:49 ` rguenther at suse dot de 2011-10-19 15:39 ` paolo.carlini at oracle dot com 2011-10-19 15:53 ` paolo.carlini at oracle dot com 2011-10-19 17:24 ` manu at gcc dot gnu.org [this message] 2011-10-19 17:28 ` paolo.carlini at oracle dot com 2011-10-27 9:27 ` rguenth at gcc dot gnu.org 2011-10-27 9:39 ` rguenth at gcc dot gnu.org 2011-10-27 10:21 ` paolo.carlini at oracle dot com 2011-10-27 10:26 ` rguenther at suse dot de 2011-12-06 10:09 ` rguenth at gcc dot gnu.org 2012-07-02 12:23 ` [Bug middle-end/48087] [4.5/4.6/4.7/4.8 " rguenth at gcc dot gnu.org 2013-01-15 15:12 ` [Bug middle-end/48087] [4.6/4.7/4.8 " jakub at gcc dot gnu.org 2013-01-15 16:40 ` manu at gcc dot gnu.org 2013-03-21 20:03 ` [Bug middle-end/48087] [4.6/4.7/4.8/4.9 " jakub at gcc dot gnu.org 2013-04-12 15:18 ` [Bug middle-end/48087] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2014-01-23 7:21 ` law at redhat 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-48087-4-U8qwgso4VI@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).