On 10/19/10 14:42, Ian Lance Taylor wrote:
Jeff Lawl...@redhat.com writes:
Reload has the ability to replace a pseudo with its equivalent memory
location. This is fine and good.
Imagine:
1. We have a pseudo (call is pseudo A) with a read-only memory
equivalent. Pseudo A does not get a
Jeff Law l...@redhat.com writes:
If
there is any register pressure, B is going to go onto the stack or is
going to force something else onto the stack.
Not today, which is the problem.
Well, I was implicitly anding in the clause if the compiler were
correct.
Ian
Looking for advice here -- while I haven't seen this bug trigger in
the mainline, it triggers with the range splitting code I've been
working on.
Reload has the ability to replace a pseudo with its equivalent memory
location. This is fine and good.
Imagine:
1. We have a pseudo (call
Jeff Law l...@redhat.com writes:
Reload has the ability to replace a pseudo with its equivalent memory
location. This is fine and good.
Imagine:
1. We have a pseudo (call is pseudo A) with a read-only memory
equivalent. Pseudo A does not get a hard reg
2. Pseudo A crosses a call
