This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RELOAD_OTHER bug?
> That test checks that the value can actually live in the reload
> register not only during, but also in-between (if there is such a
> time) the two reloads. If there is a reload type available that is
> suitable for the merged reload is another matter. I see now that
> this code is in merge_assigned_reloads, so it might even be safe
> there to set the reload type to RELOAD_FOR_OTHER_ADDRESS.
Well, this is the case where the reload in question is changed, and
where I proposed adding the test for RELOAD_FOR_OTHER_ADDRESS.