On Mon, 14 Jul 2008, DJ Delorie wrote:
Been getting this for a while, finally had time and resources to track it
down.
It was introduced by 137639:
2008-07-08 Joseph Myers [EMAIL PROTECTED]
* reload.c (find_reloads_subreg_address): Do not require validity
of address in
You should file a PR in any case.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36827
Does m32c handle some addresses specially in any way at all similar to the
special SH handling discussed in PR 36780 and
http://gcc.gnu.org/ml/gcc-patches/2008-07/msg00932.html? Because some
sort of
On Mon, 14 Jul 2008, DJ Delorie wrote:
I did some work a while back to try to rearrange the reloads so that
registers could be reused, but IMHO the right solution is for gcc to
realize that it needs to break the insn up and reload the parts
separately, perhaps a relaxing reloader that can
If reload is generally flaky like this for m32c, perhaps a target macro to
say not to reload addresses in the particular case my patch affects would
be a sensible approach, if things worked better without reloading them
even though as far as reload knows they need reloading.
I wouldn't
