[LLVMdev] unwind's permanent residence

Dan Albert
Sat, 31 Jan 2015 02:02:01 -0000

Talked it over with Saleem on IRC, and I've come around to thinking
libunwind is a better default for --rtlib=compiler-rt. Reason being that
--rtlib=compiler-rt means libgcc probably isn't even available.

On Fri, Jan 30, 2015 at 5:30 PM, Saleem Abdulrasool <compnerd at
compnerd.org>
wrote:

> On Fri, Jan 30, 2015 at 4:15 PM, Dan Albert <danalbert at google.com>
wrote:
>
>> On Fri, Jan 30, 2015 at 4:12 PM, Saleem Abdulrasool <
>> compnerd at compnerd.org> wrote:
>>
>>> On Fri, Jan 30, 2015 at 3:35 PM, Dan Albert <danalbert at
google.com>
>>> wrote:
>>>
>>>> Shouldn't it just use the default unwinder for the given
platform?
>>>>
>>>
>>> Sure, but what is the default unwinder for a given platform?
>>>
>>> Lets go with Linux.  I have two different images (okay, I have one,
but
>>> Im sufficiently familiar with Gentoo as well):
>>> - Gentoo w/ GCC
>>> - exherbo w/o GCC
>>>
>>> Both are Linux.  Whats the default unwinder?
>>>
>>
>> From a triple standpoint, aren't targets marked as linux-gnu? That
should
>> be enough to determine that, right?
>>
>
> Yeah, both are linux-gnu.  How do you differentiate between libunwind vs
> libgcc (-static-libgcc) or libgcc_s between the two?  What about when you
> are cross-compiling, so, host != target, and therefore cannot use
> /etc/*-release?
>
> --
> Saleem Abdulrasool
> compnerd (at) compnerd (dot) org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20150130/e4fb6026/attachment.html>