This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Move insn out of the way
On Thu, Aug 11, 2011 at 1:01 AM, Vladimir Makarov <vmakarov@redhat.com> wrote:
> I can not reproduce the problem. It would be nice to give all info (the
> code without includes and all options). In this case I could have more info
> to say more definitely about the reason of the problem in IRA.
>
Let me add another example using the avr backend that produces really
strange code. The code has a similar nature:
_Bool simple(unsigned long *a, unsigned long *b) { return *a == *b; }
Generates the following assembler when compiled with -Os in gcc-4.6:
simple:
push r16
push r17
/* prologue: function */
/* frame size = 0 */
/* stack size = 2 */
.L__stack_usage = 2
mov r30,r24
mov r31,r25
ldi r24,lo8(1)
ld r16,Z
ldd r17,Z+1
ldd r18,Z+2
ldd r19,Z+3
mov r30,r22
mov r31,r23
ld r20,Z
ldd r21,Z+1
ldd r22,Z+2
ldd r23,Z+3
cp r16,r20
cpc r17,r21
cpc r18,r22
cpc r19,r23
breq .L2
ldi r24,lo8(0)
.L2:
/* epilogue start */
pop r17
pop r16
ret
Again here the placing of the return value is not very relevant
because I guess there's not much register pressure but when there is,
in my arch, the resulting code is increased by 5 words simply due to
the position of the constant assignment. In the above case, the
constant assignment is the 5th instruction, when it could be pretty
much closer to the end.
I am interested in knowing if this is indeed an IRA problem and I have
to wait for a fix, or if there's something that I need doing in the
backend to tell GCC to delay the constant assignment.
Cheers,
--
PMatos