public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/33136] [4.1/4.2 Regression] wrong code due to alias with allocation in loop
Date: Mon, 15 Oct 2007 18:52:00 -0000 [thread overview]
Message-ID: <20071015185214.29874.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33136-12956@http.gcc.gnu.org/bugzilla/>
------- Comment #31 from jakub at gcc dot gnu dot org 2007-10-15 18:51 -------
Fixed so far on the trunk.
--
jakub at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |jakub at gcc dot gnu dot org
|dot org |
URL| |http://gcc.gnu.org/ml/gcc-
| |patches/2007-
| |10/msg00900.html
Status|NEW |ASSIGNED
Last reconfirmed|2007-08-21 13:12:38 |2007-10-15 18:51:59
date| |
Summary|[4.1/4.2/4.3 Regression] |[4.1/4.2 Regression] wrong
|wrong code due to alias with|code due to alias with
|allocation in loop |allocation in loop
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33136
next prev parent reply other threads:[~2007-10-15 18:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 12:23 [Bug regression/33136] New: -Os generated code grew almost twice 4.2.1 versus 4.1.1 vda dot linux at googlemail dot com
2007-08-21 12:24 ` [Bug regression/33136] " vda dot linux at googlemail dot com
2007-08-21 12:26 ` vda dot linux at googlemail dot com
2007-08-21 12:27 ` vda dot linux at googlemail dot com
2007-08-21 13:11 ` rguenth at gcc dot gnu dot org
2007-08-21 13:12 ` [Bug tree-optimization/33136] [4.2/4.3 Regression] " rguenth at gcc dot gnu dot org
2007-08-21 16:20 ` pinskia at gcc dot gnu dot org
2007-08-22 13:27 ` jakub at gcc dot gnu dot org
2007-08-22 13:55 ` jakub at gcc dot gnu dot org
2007-08-22 13:57 ` jakub at gcc dot gnu dot org
2007-08-22 14:20 ` rguenth at gcc dot gnu dot org
2007-08-22 14:29 ` jakub at gcc dot gnu dot org
2007-08-22 15:15 ` [Bug tree-optimization/33136] [4.1/4.2/4.3 " rguenth at gcc dot gnu dot org
2007-08-22 15:53 ` [Bug tree-optimization/33136] [4.1/4.2/4.3 Regression] wrong code due to alias with allocation in loop dberlin at gcc dot gnu dot org
2007-08-22 17:24 ` jakub at gcc dot gnu dot org
2007-08-22 20:10 ` dberlin at gcc dot gnu dot org
2007-08-23 12:13 ` jakub at gcc dot gnu dot org
2007-08-23 13:45 ` dberlin at dberlin dot org
2007-08-23 14:49 ` jakub at redhat dot com
2007-08-23 17:09 ` dberlin at dberlin dot org
2007-08-24 15:39 ` jakub at gcc dot gnu dot org
2007-08-24 15:42 ` dberlin at dberlin dot org
2007-08-24 16:17 ` jakub at gcc dot gnu dot org
2007-08-24 16:21 ` dberlin at dberlin dot org
2007-08-24 16:37 ` jakub at gcc dot gnu dot org
2007-09-05 1:09 ` mmitchel at gcc dot gnu dot org
2007-09-05 5:47 ` jakub at gcc dot gnu dot org
2007-09-11 17:21 ` jakub at gcc dot gnu dot org
2007-09-11 19:26 ` jakub at gcc dot gnu dot org
2007-09-11 19:52 ` jakub at gcc dot gnu dot org
2007-09-28 4:02 ` mmitchel at gcc dot gnu dot org
2007-10-15 18:30 ` jakub at gcc dot gnu dot org
2007-10-15 18:52 ` jakub at gcc dot gnu dot org [this message]
2008-07-04 22:16 ` [Bug tree-optimization/33136] [4.2 " jsm28 at gcc dot gnu dot org
2009-03-30 22:17 ` jsm28 at gcc dot gnu 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=20071015185214.29874.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).