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/50624] detecting array overflows regressed
Date: Thu, 06 Oct 2011 15:11:00 -0000 [thread overview]
Message-ID: <bug-50624-4-QNAfv8SZKW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50624-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50624
--- Comment #6 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-10-06 15:10:45 UTC ---
(In reply to comment #5)
> Easy case = constant expressions as index?
>
> Would the frontend be able to handle
>
> short array[1];
>
> i = 1;
> array[i]
Probably not.
It's also the usual trade-off between warnings for dead code or not.
prev parent reply other threads:[~2011-10-06 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 18:23 [Bug c/50624] New: " andi-gcc at firstfloor dot org
2011-10-05 18:50 ` [Bug c/50624] " jakub at gcc dot gnu.org
2011-10-05 18:57 ` andi-gcc at firstfloor dot org
2011-10-05 19:23 ` jakub at gcc dot gnu.org
2011-10-06 8:31 ` rguenth at gcc dot gnu.org
2011-10-06 14:50 ` andi-gcc at firstfloor dot org
2011-10-06 15:11 ` 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-50624-4-QNAfv8SZKW@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: 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).