llvm dev - Jan 2018 - Exception handling support for a target

2018-01-19 23:00 GMT+08:00 Krzysztof Parzyszek via llvm-dev <
llvm-dev at lists.llvm.org>:
> On 1/15/2018 6:49 AM, 陳韋任 via llvm-dev wrote:
>
>> - EH_RETURN:
>>
>>    I see some targets define their own EH_RETURN SDNode, others
don't.
>> What is EH_RETURN, and under what circumstances I should define my own
>> EH_RETURN SDNode?
>>
>
> This corresponds to a GCC intrinsic used in their unwind routines. It's
> not really known for its exemplary documentation, so you may need to read
> GCC's sources to see what they are doing with it.
> Unless you plan to compile GCC's unwind library, you don't really
need to
> worry about it.

I see X86, Mips, XCore and Hexagon define their own EH_RETURN and lower to
it, but others don't. May I know why it's so on Hexagon?
​​


-- 
Wei-Ren Chen (陳韋任)
Homepage: https://people.cs.nctu.edu.tw/~chenwj
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20180120/a8f91326/attachment.html>

On 1/19/2018 7:21 PM, 陳韋任 wrote:
> I see X86, Mips, XCore and Hexagon define their own EH_RETURN and lower 
> to it, but others don't. May I know why it's so on Hexagon?
Our exception handling runtime uses __builtin_eh_return.

-Krzysztof

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, 
hosted by The Linux Foundation

On 22 Jan 2018, at 14:15, Krzysztof Parzyszek via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> On 1/19/2018 7:21 PM, 陳韋任 wrote:
>> I see X86, Mips, XCore and Hexagon define their own EH_RETURN and lower
to it, but others don't. May I know why it's so on Hexagon?
> 
> Our exception handling runtime uses __builtin_eh_return.
Does this mean that you know what it does?  If so, please could you document it
somewhere?

David