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 tree-optimization/29751] not optimizing access a[0] , a[1]
Date: Mon, 11 Jun 2007 00:30:00 -0000 [thread overview]
Message-ID: <20070611003003.8573.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29751-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from pinskia at gcc dot gnu dot org 2007-06-11 00:30 -------
Confirmed, this is only a tree level missed optimization.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Keywords| |alias, TREE
Last reconfirmed|0000-00-00 00:00:00 |2007-06-11 00:30:03
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29751
next prev parent reply other threads:[~2007-06-11 0:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 13:10 [Bug tree-optimization/29751] New: Missed optimization of restrict pointer assigned value burnus at gcc dot gnu dot org
2006-11-14 1:06 ` [Bug tree-optimization/29751] not optimizing access a[0] , a[1] pinskia at gcc dot gnu dot org
2007-06-11 0:30 ` pinskia at gcc dot gnu dot org [this message]
2008-03-14 21:22 ` rguenth at gcc dot gnu dot org
2008-04-07 1:29 ` pinskia at gcc dot gnu dot org
2008-04-07 8:52 ` rguenth at gcc dot gnu dot org
2009-06-09 2:35 ` pinskia at gcc dot gnu dot org
2009-08-05 17:52 ` pinskia at gcc dot gnu dot org
[not found] <bug-29751-4@http.gcc.gnu.org/bugzilla/>
2011-09-23 22:12 ` pinskia at gcc dot gnu.org
2011-11-17 22:56 ` pinskia at gcc dot gnu.org
2012-01-25 9:56 ` pinskia at gcc dot gnu.org
2012-01-25 10:41 ` rguenth 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=20070611003003.8573.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).