Displaying 4 results from an estimated 4 matches for "unwnd".
Did you mean:
unwind
2009 Jun 15
2
[LLVMdev] unwind/invoke design
...t doesn't
>> work with the JIT or native codegen [1].
>
> DWARF EH maybe what you want, it has zero overhead on normal calls and I
> believe it is built into LLVM's assemblers. A DWARF style EH is also built
> into the JIT too.
How do I tell llc to output dwarf-style 'unwnd' ? Both -enable-eh and
-enable-correct-eh-support compile 'unwind' to nothing on x86 with llc
v2.5.
2009 Jun 15
0
[LLVMdev] unwind/invoke design
> The documentation of unwind/invoke is quite clear and does exactly
> what I need: unwinding the stack. I don't need it to carry an object
> back. I don't need it to figure out what the type of the object is or
> what catch() blocks it matches. I just need it to unwind the stack.
> The rest is my job as a part of the runtime. Unfortunately, I have
> learned that while
2009 Jun 15
0
[LLVMdev] unwind/invoke design
...codegen [1].
>>>
>> DWARF EH maybe what you want, it has zero overhead on normal calls and I
>> believe it is built into LLVM's assemblers. A DWARF style EH is also built
>> into the JIT too.
>>
>
> How do I tell llc to output dwarf-style 'unwnd' ? Both -enable-eh and
> -enable-correct-eh-support compile 'unwind' to nothing on x86 with llc
> v2.5.
>
Write some C++ code into llvm.org/demo, and watch the output assembly,
for example:
int foo() {
throw 1;
}
int bar() {
try {
foo();
} catch (...) {
}
}
That should...
2009 Jun 15
6
[LLVMdev] unwind/invoke design
The documentation of unwind/invoke is quite clear and does exactly
what I need: unwinding the stack. I don't need it to carry an object
back. I don't need it to figure out what the type of the object is or
what catch() blocks it matches. I just need it to unwind the stack.
The rest is my job as a part of the runtime. Unfortunately, I have
learned that while this works with the bytecode