Displaying 1 result from an estimated 1 matches for "badincomingargoffset".
2010 May 13
1
[LLVMdev] Attention: About to Break SystemZ and possibly other Back Ends
...sCalls" is calculated. Basically, the way it's calculated now is in PEI. And it only looks for frame adjustments (or inline ASM) to determine if the function has a call or not. This way is much more accurate and occurs much sooner. But it breaks this test:
test/CodeGen/SystemZ/2009-07-10-BadIncomingArgOffset.ll
(See below for the output with this patch.)
The problem is that SystemZ is using "hasCalls()" in the back end to determine if a frame pointer is needed or not. My guess is that several of the places where it calls hasCalls() should really be hasFP(). I don't have enough expertise...