public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/36902] Array bound warning with dead code after optimization
Date: Tue, 18 Nov 2008 15:45:00 -0000	[thread overview]
Message-ID: <20081118154353.25424.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36902-682@http.gcc.gnu.org/bugzilla/>



------- Comment #31 from manu at gcc dot gnu dot org  2008-11-18 15:43 -------
(In reply to comment #30)
> Thanks Manuel. I'm not sure that this is technically a regression, but in any
> case I consider it a serious problem and really hope we can have a fix for
> 4.4.0.

I submitted the patch long ago. We are in regressions-only mode. This is not a
regression. Not sure what else you want me to do.

(It doesn't fix PR37921, though. I haven't tested PR35392.)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36902


  parent reply	other threads:[~2008-11-18 15:45 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 18:44 [Bug c/36902] New: [4.3/4.4 Regression]: Bogus array bound warning hjl dot tools at gmail dot com
2008-07-22 20:51 ` [Bug middle-end/36902] " pinskia at gcc dot gnu dot org
2008-07-22 21:13 ` hjl dot tools at gmail dot com
2008-07-22 21:19 ` [Bug middle-end/36902] Array bound warning with dead code after optimization pinskia at gcc dot gnu dot org
2008-07-22 21:27 ` paolo dot carlini at oracle dot com
2008-07-22 21:29 ` hjl dot tools at gmail dot com
2008-07-22 21:31 ` hjl dot tools at gmail dot com
2008-07-22 21:33 ` paolo dot carlini at oracle dot com
2008-07-22 21:43 ` hjl dot tools at gmail dot com
2008-07-22 22:54 ` paolo dot carlini at oracle dot com
2008-07-23  1:05 ` hjl dot tools at gmail dot com
2008-07-23  1:16 ` paolo dot carlini at oracle dot com
2008-07-23  1:24 ` hjl dot tools at gmail dot com
2008-07-23  1:29 ` paolo dot carlini at oracle dot com
2008-08-15 20:12 ` manu at gcc dot gnu dot org
2008-08-15 20:19 ` manu at gcc dot gnu dot org
2008-08-15 20:38 ` paolo dot carlini at oracle dot com
2008-08-22 16:45 ` manu at gcc dot gnu dot org
2008-08-22 17:06 ` manu at gcc dot gnu dot org
2008-08-22 17:31 ` pinskia at gcc dot gnu dot org
2008-08-22 17:38 ` hjl dot tools at gmail dot com
2008-08-22 17:55 ` manu at gcc dot gnu dot org
2008-08-25  8:01 ` mueller at gcc dot gnu dot org
2008-08-25 10:51 ` manu at gcc dot gnu dot org
2008-10-26 22:07 ` hjl dot tools at gmail dot com
2008-10-27  0:18 ` pinskia at gcc dot gnu dot org
2008-11-15  0:09 ` pinskia at gcc dot gnu dot org
2008-11-18 10:18 ` paolo dot carlini at oracle dot com
2008-11-18 14:43 ` hjl dot tools at gmail dot com
2008-11-18 15:23 ` manu at gcc dot gnu dot org
2008-11-18 15:27 ` paolo dot carlini at oracle dot com
2008-11-18 15:45 ` manu at gcc dot gnu dot org [this message]
2008-11-18 15:49 ` paolo dot carlini at oracle dot com
2008-11-18 16:07 ` manu at gcc dot gnu dot org
2009-04-18  9:25 ` manu at gcc dot gnu dot org
2009-04-18  9:30 ` manu at gcc dot gnu dot org
     [not found] <bug-36902-4@http.gcc.gnu.org/bugzilla/>
2021-10-21  2:03 ` pinskia 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=20081118154353.25424.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: 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).