[Bug target/52049] SH Target: Inefficient constant address access

[olegendo at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52049

--- Comment #2 from Oleg Endo olegendo at gcc dot gnu.org ---
There is a GSoC 2015 project which will try to address the AMS problem.
https://www.google-melange.com/gsoc/project/details/google/gsoc2015/erikvarga/5693417237512192

It will be initially for SH.  If it works out, it can be generalized so that
other targets can benefit from it, too.

[Bug target/52049] SH Target: Inefficient constant address access

[olegendo at gcc dot gnu.org]

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

olegendo at gcc dot gnu.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2012-02-26
 CC||olegendo at gcc dot gnu.org
 Ever Confirmed|0   |1

[Bug target/52049] SH Target: Inefficient constant address access

[kkojima at gcc dot gnu.org]

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

--- Comment #1 from Kazumoto Kojima kkojima at gcc dot gnu.org 2012-01-30 
00:15:16 UTC ---
(In reply to comment #0)
 I'm not sure whether this is actually a problem of the SH back-end or of some
 middle-end passes.  It happens for all sub-targets and regardless of the
 endianess.

I've tried these cases on arm/thumb and got similar results
which look not very good.  From the rtl dumps, it looks a general
issue with postreload optimization on some targets.