public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/56932] [regression 4.8]: vrp and/or niter-related wrong-code bug Date: Fri, 12 Apr 2013 18:31:00 -0000 [thread overview] Message-ID: <bug-56932-4-mHmaTyRw43@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56932-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56932 --- Comment #4 from Kai Tietz <ktietz at gcc dot gnu.org> 2013-04-12 18:31:05 UTC --- Well, indeed increasing the array-size helps to avoid this issue. Nevertheless I don't get why it produces wrong code for argument of call of function t here. That there is a out-of-bounds access is one thing, but there is still wrong code produced. Also why - if gcc already detects an out-of-bounds access - there is no warning for that?
next prev parent reply other threads:[~2013-04-12 18:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-12 10:08 [Bug middle-end/56932] New: " ktietz at gcc dot gnu.org 2013-04-12 11:28 ` [Bug middle-end/56932] " pinskia at gcc dot gnu.org 2013-04-12 11:50 ` glisse at gcc dot gnu.org 2013-04-12 12:22 ` graham.stott at btinternet dot com 2013-04-12 18:31 ` ktietz at gcc dot gnu.org [this message] 2013-04-12 19:00 ` pinskia at gcc dot gnu.org 2013-04-12 20:02 ` glisse 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-56932-4-mHmaTyRw43@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).