public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/44300] Spurious array subscript warning Date: Thu, 27 May 2010 20:04:00 -0000 [thread overview] Message-ID: <20100527200356.3002.qmail@sourceware.org> (raw) In-Reply-To: <bug-44300-19243@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from pinskia at gcc dot gnu dot org 2010-05-27 20:03 ------- "&b[0] > &a[0]" is not well defined in C or C++. That is what it gets optimized to. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44300
next prev parent reply other threads:[~2010-05-27 20:04 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-27 20:00 [Bug c/44300] New: " jmattson at vmware dot com 2010-05-27 20:01 ` [Bug c/44300] " jmattson at vmware dot com 2010-05-27 20:04 ` pinskia at gcc dot gnu dot org [this message] 2010-05-27 20:31 ` jmattson at vmware dot com 2010-05-28 10:30 ` rguenth at gcc dot gnu dot org 2010-05-28 14:39 ` jmattson at vmware dot com 2010-05-28 14:44 ` rguenth at gcc dot gnu dot org 2010-05-28 15:55 ` jmattson at vmware dot com 2010-05-28 16:40 ` rguenth at gcc dot gnu dot org 2010-05-28 16:53 ` jmattson at vmware dot com 2010-05-28 17:52 ` [Bug middle-end/44300] Spurious array subscript warning, &b[0] == &a[1] is not folded rguenth at gcc dot gnu dot org 2010-05-29 0:34 ` segher at kernel dot crashing 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=20100527200356.3002.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).