search for: xyzframelow

Hello, I have a few general questions. 1. Whether the memory contents assigned for a function are accessible after we return from that function? If yes, how can we access it? 2. Does llvm delete the stackframe assigned for a specific function, after we return from that function? 3. If not, how can we delete the stackframe or clear the memory content after we return from the function? Where do

Hi, Is it possible to add a spill code (a pair of store /load ) to the machinecode in a pass before the instruction emitter? If so, how can I calculate the address (offset to the sp) for the spill store/load instructions? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL:

...hen the source code itself contains "throw X"). So normally the directives are emitted in the prologue when the registers actually get saved. Sometimes all in a bunch, sometimes interspersed with the saves, but it usually doesn't matter which. As you've discovered that happens in XYZFrameLowering > - getExceptionPointerRegister and getExceptionSelectorRegister: > > TargetLowering subclass should implement both functions. The former > specifies the register used to pass the exception object to the landing pad > (or catch clause), and the latter specifies the regist...

Dear all, I don't get how llvm handles functions with __attribute__((noreturn)). It seems that LR register is backed up on the stack whilst it will never be used to return from a 'noreturn' function. I have this problem with a home-made backend but it seems that ARM flavour of clang has same behaviour. By the way, SP is also saved, I don't understand why. Is there a syntax error

Hi All, I would like to know in order to support exception handling for particular target, what need to be done. After doing some investigation, I can think of the following items with questions: - CFI directives: This is for .eh_frame section. Basically all the targets insert CFI directives in FrameLowering, but I am not sure exactly when/where I should do so. -

Hi all, I've been working on a backend of our architecture and noticed llvm performs following combining although one of operands is FrameIndex. Combining: t114: i64 = add FrameIndex:i64<0>, Constant:i64<56> Creating new node: t121: i64 = or FrameIndex:i64<0>, Constant:i64<56> ... into: t121: i64 = or FrameIndex:i64<0>, Constant:i64<56> This

Hi all, Sorry to bother those not interested. I am a newbie to LLVM. I have a problem on allocating additional stack slot for checkpointing. However, I have no idea on how to allocate redundant stack slot in llvm. Any suggestions? Thanks, Ray -------------- next part -------------- An HTML attachment was scrubbed... URL:

...lf contains "throw X"). > > So normally the directives are emitted in the prologue when the > registers actually get saved. Sometimes all in a bunch, sometimes > interspersed with the saves, but it usually doesn't matter which. As > you've discovered that happens in XYZFrameLowering ​Do we have to emit directives in the epilogue, too?​ One of my test case fail due to the directives in the epilogue have been executed. After remov ​ing them from epilogue, the exception is caught as expected. Also, the directives are also for debug purpose (.debug_frame), right? I guess I...