public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/41279] [4.5 Regression] 252.eon performance regression
Date: Mon, 07 Sep 2009 12:06:00 -0000 [thread overview]
Message-ID: <20090907120557.683.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41279-10053@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from jamborm at gcc dot gnu dot org 2009-09-07 12:05 -------
Hm, I wonder how come we did not come across this when testing the
patch for exactly these kinds of problems in July. Anyway, I will
have a look at it.
Nevertheless, I believe we should split this bug in two so that we can
track the SRA and VTA regressions separately. So unless someone
objects or I realize the fix is so trivial it does not really deserve
its own PR, I'll create a new Pr for the SRA issue when I come across
something interesting.
--
jamborm at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|mjambor at suse dot cz |jamborm at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41279
next prev parent reply other threads:[~2009-09-07 12:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-05 16:05 [Bug target/41279] New: " rguenth at gcc dot gnu dot org
2009-09-05 16:07 ` [Bug target/41279] " rguenth at gcc dot gnu dot org
2009-09-05 16:13 ` rguenth at gcc dot gnu dot org
2009-09-05 16:14 ` rguenth at gcc dot gnu dot org
2009-09-06 10:17 ` rguenth at gcc dot gnu dot org
2009-09-07 12:06 ` jamborm at gcc dot gnu dot org [this message]
2009-09-08 11:58 ` jamborm at gcc dot gnu dot org
2009-09-29 21:42 ` jakub at gcc dot gnu dot org
2009-09-30 9:58 ` jakub at gcc dot gnu dot org
2009-09-30 20:09 ` rguenth at gcc dot gnu dot org
2009-10-30 20:42 ` sje at cup dot hp dot com
2009-10-30 22:11 ` rguenth at gcc dot gnu dot org
2009-12-16 22:49 ` rguenth 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=20090907120557.683.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).