Displaying 3 results from an estimated 3 matches for "eh_table".
Did you mean:
_table
2014 Mar 20
3
[LLVMdev] So what's the deal with debug_frame V eh_frame
While comparing debug info between GCC and Clang I found a section
that only Clang produces and GCC never produces: debug_frame.
It seems (though I haven't verified this with absolute certainty) as
though GCC just always uses eh_frame. LLVM on the other hand sometimes
uses eh_frame and sometimes uses debug_frame.
Here's an example:
int f1();
int i = f1();
void func() { }
Compiled with
2014 Mar 20
2
[LLVMdev] So what's the deal with debug_frame V eh_frame
...gt; flagged as nounwind but also as uwtable (why? I don't really
>> understand these semantics & haven't tracked down where that attribute
>> gets applied)
>
> Is this x86-64? If so, uwtable is a abi requirement. It says that that
> function should have an entry in .eh_table.
Hmm, OK then - because I've certainly seen LLVM emit object files with
no eh_frame (as in the above example, if "func" is omitted).
>
>> Without 'func' in this translation unit, LLVM emits a debug_frame
>> section (because no functions actually need an unwind...
2014 Feb 17
3
[LLVMdev] [cfe-dev] Unwind behaviour in Clang/LLVM
Hi all,
I feel that there are two problems with the existing infrastructure:
* The nounwind attribute is ambiguous for (1) not throwing exceptions and
(2) not performing stack unwinding. I feel that it will be better to
separate this in two different attributes
* There is some problem when the function has both uwtable and nounwind.
Although, I think it fine to keep the current definition of