This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Immediates propagated wrongly in stores


Sorry about the delay in the answer (4th of July weekend...).

Anyway, I agree it might not be necessary. I put it there because of
the force_reg call. Since that call might in turn call gen_reg_rtx, it
will then start off with an assertion of can_create_pseudo_p.

That is why, I thought best to put that test.

On Wed, Jul 1, 2009 at 5:33 PM, Richard Henderson<rth@redhat.com> wrote:
> On 07/01/2009 02:02 PM, Jean Christophe Beyler wrote:
>>
>> ? ? ? ? ? ? ((reload_in_progress | reload_completed) == 0&&
>> ? ? ? ? ? ? MEM_P (op0)&& ?!REG_P (op1)))
>> ? ? {
>> ? ? ? ? op1 = force_reg (GET_MODE (op0), op1);
>> ? ? ? ? emit_move_insn (op0, op1);
>> ? ? ? ? return 1;
>
> I wouldn't think you'd actually need these reload checks.
> At least some other ports I glanced at don't need them.
>
>
> r~
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]