Displaying 4 results from an estimated 4 matches for "_unwindresume".
Did you mean:
_unwind_resume
2012 Dec 26
1
[LLVMdev] Value not in slotcalculator! error
...t; call V->dump()
output>> declare void @_Unwind_Resume(i8*)
Now the funny thing is I don't call this function, it gets inserted into my code when I generate a "resume" instruction using IRBuilder::CreateResume for exception handling. I've tried adding a declaration for _UnwindResume myself but that doesn't do anything.
Any help would be appreciated.
Best,
Christian Schafmeister
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121225/02b7a326/attachment.html>
2014 Nov 10
2
[LLVMdev] RFC: How to represent SEH (__try / __except) in LLVM IR
...__finally, but cleanups in
> general are implemented with a fundamentally different approach.
>
> During phase 2 of Itanium EH unwinding, control is propagated back up the
> stack. To run a cleanup, the stack is cleared, control enters the landing
> pad, and propagation resumes when _UnwindResume is called.
>
> On Windows, things work differently. Instead, during phase 2, each
> personality function is invoked a second time, wherein it must execute all
> cleanups *without clearing the stack* before returning control to the
> runtime where the runtime continues its loop over t...
2014 Nov 13
2
[LLVMdev] RFC: How to represent SEH (__try / __except) in LLVM IR
...plementing cleanups with __finally, but cleanups in general are implemented with a fundamentally different approach.
During phase 2 of Itanium EH unwinding, control is propagated back up the stack. To run a cleanup, the stack is cleared, control enters the landing pad, and propagation resumes when _UnwindResume is called.
On Windows, things work differently. Instead, during phase 2, each personality function is invoked a second time, wherein it must execute all cleanups *without clearing the stack* before returning control to the runtime where the runtime continues its loop over the stack frames. You can...
2010 Dec 01
8
[LLVMdev] Alternative exception handling proposal
...r and selector value as arguments:
rewind <ptr>, <i32>
The codegenerators would lower this to a call to _Unwind_Resume (the second
selector argument would not be used - it only exists to simplify inlining,
see below - the first, exception, argument would be passed as the parameter of
_UnwindResume). The goal here is to simplify inlining and avoid explicitly
dragging in library functions like _Unwind_Resume. It is possible to do without
this new instruction, but I think it represents an improvement so I include it
here.
An example
----------
Here is a technique for auto-generating example...