On Tue, Oct 2, 2012 at 10:48 AM, Uros Bizjak <ubiz...@gmail.com> wrote:
> On Tue, Oct 2, 2012 at 7:44 PM, Gabriel Dos Reis
> <g...@integrable-solutions.net> wrote:
>
>>>> > On a related issue, it looks to me that the compiler itself should be
>>>> > compiled with -funwind-tables, otherwise there are no backtraces
>>>> > generated, even if libbacktrace is linked in and operational. Again,
>>>> > x86_64-linux-gnu host defaults to this flag, but other hosts are left
>>>> > behind.
>>>>
>>>> Compiling with C++ should always give us -funwind-tables.
>>>
>>> It doesn't give that, because the compiler is compiled with
>>> -fno-exceptions -fno-rtti.
>>
>> I believe in the long term we would to drop either of those.
>
> For the short term, I am bootstrapping attached patch, that adds
> -funwind-tables to other noexcept flags.
I think you should use -fasynchronous-unwind-tables here.  That way we
can get a backtrace if the compiler gets a segmentation violation.

I'll approve this patch with that change.  But you might want to check
whether you can see any change in bootstrap time or compiler size
(sorry).

Thanks.

Ian

Reply via email to