public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61867] gcc can't detect obviously false test Date: Wed, 23 Jul 2014 12:44:00 -0000 [thread overview] Message-ID: <bug-61867-4-mBs77lMrIm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61867-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61867 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Indeed we don't want to warn here. The knowledge is spread across two different statements and that's already too far for this kind of thing. Remember we just "weakened" the transposed memset arg warning to not warn about n = 0; memset (p, 'x', n); but only about memset (p, 'x', 0);
prev parent reply other threads:[~2014-07-23 12:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-61867-4@http.gcc.gnu.org/bugzilla/> 2014-07-21 19:34 ` manu at gcc dot gnu.org 2014-07-21 19:51 ` dcb314 at hotmail dot com 2014-07-22 10:10 ` redi at gcc dot gnu.org 2014-07-23 12:44 ` rguenth 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-61867-4-mBs77lMrIm@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).