[LLVMdev] unwind's permanent residence

[Dan Albert]

The build for the unwinder is already structured such that moving it should
be easy enough. I don't really care if it ends up in its own repo or in
compiler-rt, but I think either makes more sense than its current residence.

One argument for putting it in compiler-rt is that compiler-rt aims to be a
replacement for libgcc, and libgcc contains an unwinder. That said, I've
always thought it was strange (and downright inconvenient) that libgcc does
this, so I think a separate repo might be best.

It would be nice if we had some libunwind-specific tests too. Currently we
> have none, other than the c++ abi tests.  Nick, does Apple have any they're
> willing to upstream?


Yes please :)

On Fri, Jan 30, 2015 at 1:03 PM, Renato Golin <renato.golin at linaro.org>
wrote:
>
> That's precisely the point. People should use unwinders they want, and
> libc++abi should be completely agnostic of which one you use.
>

Agreed. libc++abi is already built this way, but I don't think I ever moved
the same configuration options into libc++.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150130/a39eb127/attachment.html>