Øyvind Harboe wrote:
Is there an existing technique to figure out the difference between
the frame address and the stack pointer during code generation of
arbitary instructions?
You can get the current offset through INITIAL_ELIMINATION_OFFSET. But
this offset is not final until reload pass i
Is there an existing technique to figure out the difference between
the frame address and the stack pointer during code generation of
arbitary instructions?
This is kinda related to frame pointer -> stack pointer elimination, but
available during code generation.
I'm not quite sure, but I think
