public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/39423] [SH] performance regression: lost mov @(disp,Rn)
Date: Wed, 11 Mar 2009 10:25:00 -0000 [thread overview]
Message-ID: <20090311102507.31730.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39423-14332@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from ebotcazou at gcc dot gnu dot org 2009-03-11 10:25 -------
> I thought that the now what as with your patch. So it looks indeed like quite
> similar to what I see. I'll try to see why it doesn't solve my case.
Reverting to the old canonicalization at the tree level is not doable, that's
why the patch does it during RTL expansion and only for offsets. It probably
would need to be extended if that's not sufficient for your testcase.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39423
next prev parent reply other threads:[~2009-03-11 10:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 13:27 [Bug target/39423] New: [ chrbr at gcc dot gnu dot org
2009-03-10 13:34 ` [Bug target/39423] [ paolo dot carlini at oracle dot com
2009-03-11 8:46 ` [Bug target/39423] [SH] performance regression: lost mov @(disp,Rn) chrbr at gcc dot gnu dot org
2009-03-11 8:53 ` chrbr at gcc dot gnu dot org
2009-03-11 9:06 ` ebotcazou at gcc dot gnu dot org
2009-03-11 9:30 ` chrbr at gcc dot gnu dot org
2009-03-11 9:36 ` ebotcazou at gcc dot gnu dot org
2009-03-11 9:46 ` chrbr at gcc dot gnu dot org
2009-03-11 10:25 ` ebotcazou at gcc dot gnu dot org [this message]
2009-03-11 14:08 ` chrbr at gcc dot gnu dot org
2009-03-12 15:04 ` chrbr at gcc dot gnu dot org
2009-03-12 15:11 ` chrbr at gcc dot gnu dot org
2009-03-31 16:09 ` [Bug target/39423] [4.3/4.4/4.5 Regression] " jsm28 at gcc dot gnu dot org
2009-03-31 19:11 ` jakub at gcc dot gnu dot org
2009-08-04 12:48 ` rguenth at gcc dot gnu dot org
2010-05-22 18:33 ` [Bug target/39423] [4.3/4.4/4.5/4.6 " 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=20090311102507.31730.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).