public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/51721] -Warray-bounds false positives and inconsistencies Date: Sat, 31 Dec 2011 01:55:00 -0000 [thread overview] Message-ID: <bug-51721-4-gBhB8xQZzK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51721-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51721 --- Comment #1 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> 2011-12-31 01:50:59 UTC --- Oops, gcc-snapshot was not GCC 4.6.2. Anyway, I get the same warnings with GCC 4.6.2 and gcc-snapshot, which is: gcc (Debian 20111210-1) 4.7.0 20111210 (experimental) [trunk revision 182188]
next prev parent reply other threads:[~2011-12-31 1:51 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-31 1:51 [Bug tree-optimization/51721] New: " vincent-gcc at vinc17 dot net 2011-12-31 1:55 ` vincent-gcc at vinc17 dot net [this message] 2011-12-31 17:25 ` [Bug tree-optimization/51721] " jakub at gcc dot gnu.org 2012-01-01 0:18 ` jakub at gcc dot gnu.org 2012-01-02 10:19 ` rguenth at gcc dot gnu.org 2012-01-02 10:25 ` jakub at gcc dot gnu.org 2012-01-03 10:18 ` jakub at gcc dot gnu.org 2012-03-05 12:29 ` jakub at gcc dot gnu.org 2012-03-12 11:13 ` jakub at gcc dot gnu.org 2012-11-09 23:26 ` steven at gcc dot gnu.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=bug-51721-4-gBhB8xQZzK@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).