public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu 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: Thu, 12 Feb 2009 14:59:00 -0000 [thread overview] Message-ID: <20090212145926.25276.qmail@sourceware.org> (raw) In-Reply-To: <bug-31878-6477@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from manu at gcc dot gnu dot org 2009-02-12 14:59 ------- Updating the description. Although anyone would agree that not warning is the right thing to do, there doesn't seem to be any practical solution for this problem, so I leave it as unconfirmed. I wonder if clang/llvm gets this right. -- manu at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manu at gcc dot gnu dot org Summary|Spurious warnings generated |Spurious warnings with - |due to not optimizing first |Wreturn-type due to not | |performing CCP/VRP in the | |front-end http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31878
next prev parent reply other threads:[~2009-02-12 14:59 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 ` manu at gcc dot gnu dot org [this message] 2009-12-29 6:07 ` [Bug middle-end/31878] Spurious warnings with -Wreturn-type due to not performing CCP/VRP in the front-end sabre at nondot dot org 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=20090212145926.25276.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: 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).