public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sabre at nondot dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/31878] Spurious warnings with -Wreturn-type due to not performing CCP/VRP in the front-end
Date: Tue, 29 Dec 2009 06:07:00 -0000 [thread overview]
Message-ID: <20091229060747.19981.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31878-6477@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from sabre at nondot dot org 2009-12-29 06:07 -------
Clang does not produce diagnostics from the optimizer. We intentionally do not
want to do this, because of the fragility of the diagnostics as the optimizer
evolves. IMO it is much better to produce a consistent and predictable set of
diagnostics rather than trying to avoid all false positives by relying on the
optimizer to be tricky.
--
sabre at nondot dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sabre at nondot dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31878
next prev parent reply other threads:[~2009-12-29 6:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 13:12 [Bug c/31878] New: Spurious warnings generated due to not optimizing first lloyd at randombit dot net
2007-05-09 21:07 ` [Bug c/31878] " pinskia at gcc dot gnu dot org
2007-05-09 21:16 ` lloyd at randombit dot net
2007-05-10 14:50 ` manu at gcc dot gnu dot org
2007-05-10 16:51 ` lloyd at randombit dot net
2007-05-11 10:38 ` manu at gcc dot gnu dot org
2008-11-14 23:39 ` [Bug middle-end/31878] " pinskia at gcc dot gnu dot org
2009-02-12 14:59 ` [Bug middle-end/31878] Spurious warnings with -Wreturn-type due to not performing CCP/VRP in the front-end manu at gcc dot gnu dot org
2009-12-29 6:07 ` sabre at nondot dot org [this message]
2009-12-30 1:43 ` manu at gcc dot gnu dot org
2009-12-30 1:46 ` sabre at nondot dot 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=20091229060747.19981.qmail@sourceware.org \
--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).