DJ Delorie <[EMAIL PROTECTED]> writes:
> > The destination register which is set by a CALL will normally be
> > FUNCTION_VALUE, which is normally a hard register.
>
> dst is not the destination of the call, it's the destination of the
> SET/PLUS that's being optimized.
Sorry, I misread.
In fact
> The destination register which is set by a CALL will normally be
> FUNCTION_VALUE, which is normally a hard register.
dst is not the destination of the call, it's the destination of the
SET/PLUS that's being optimized.
Ian Lance Taylor wrote:
>> Any reason why we blindly assume destination registers will be hard
>> registers here?
>>
>> Index: regmove.c
>> ===
>> RCS file: /cvs/gcc/gcc/gcc/regmove.c,v
>> retrieving revision 1.173
>> diff -p -U3 -r
DJ Delorie <[EMAIL PROTECTED]> writes:
> Any reason why we blindly assume destination registers will be hard
> registers here?
>
> Index: regmove.c
> ===
> RCS file: /cvs/gcc/gcc/gcc/regmove.c,v
> retrieving revision 1.173
> diff -p
Any reason why we blindly assume destination registers will be hard
registers here?
Index: regmove.c
===
RCS file: /cvs/gcc/gcc/gcc/regmove.c,v
retrieving revision 1.173
diff -p -U3 -r1.173 regmove.c
--- regmove.c 25 Aug 2005 06:44
