search for: unnwind

Displaying 4 results from an estimated 4 matches for "unnwind".

Did you mean: unwind
2009 Jul 20
0
[LLVMdev] x86 unwind support[MESSAGE NOT SCANNED]
...tore registers and so forth at every stack frame. > This is extra work done at unwind time that reduces the cost of > making invoke calls by avoiding the need to save a bunch of > context. > Is there anything in the current codebase that maps an "unwind" instruction to a DWARF unnwinder? Seeing as how (I think) the DWARF info is already compiled in, this would be a useful thing.
2009 Jul 20
2
[LLVMdev] x86 unwind support[MESSAGE NOT SCANNED]
Hi Kenneth, > Is there anything in the current codebase that maps an "unwind" > instruction to a DWARF unnwinder? Seeing as how (I think) the DWARF > info is already compiled in, this would be a useful thing. in llvm from svn an "unwind" instruction is mapped to a call to _Unwind_Resume. This is no good for throwing a new dwarf exception, but it does mean that you can now implement cleanups...
2009 Jul 20
4
[LLVMdev] x86 unwind support[MESSAGE NOT SCANNED]
Hi Mark, > You are confusing stopping the unwinding at *some* levels or at *all* > levels. > Eg. > invoke > call > call > invoke > call > call > unwind the dwarf unwinder only stops and runs user code at the invokes. It does restore registers and so forth at every stack frame. This is extra work done at unwind time that reduces the cost
2009 Jul 20
0
[LLVMdev] x86 unwind support[MESSAGE NOT SCANNED]
...tion with the landing pads and the exception object selection and all that jazz? On Mon, Jul 20, 2009 at 12:12 PM, Duncan Sands<baldrick at free.fr> wrote: > Hi Kenneth, > >> Is there anything in the current codebase that maps an "unwind" >> instruction to a DWARF unnwinder?  Seeing as how (I think) the DWARF >> info is already compiled in, this would be a useful thing. > > in llvm from svn an "unwind" instruction is mapped to a call to > _Unwind_Resume.  This is no good for throwing a new dwarf exception, > but it does mean that you can...