That was also the conclusion I came to. I was now wondering why GREG
allows itself to change that register from r0 to r3. Is there any
reason?
It seems to me that the most likely reason is that it considers in
this case r0 as undefined and thus can modify it to r3 because of
this. I was wondering
On 08/21/2009 04:01 PM, Jean Christophe Beyler wrote:
/* If we have a 0, use r0 instead */
Don't do this. See how, e.g. alpha and mips handle the zero register.
You want to leave this as (const_int 0) throughout compilation.
r~
Dear all,
I actually have determined that doing what I say below is a bad idea
since it will probably lessen the impact of future optimizations in
the compiler. However, I'm curious to know why it didn't work :-)
Here goes: I've been working on getting better code generation and one
thing I notic
