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 frame ointer to stack pointer elimination can fail. If this is the case, is it because the difference between frame pointer and stack pointer is not a constant or some other reason? I'm just curious and would like to read more. -- Øyvind Harboe http://www.zylin.com
