Add support for musl-libc on Linux
Rafael Espíndola via llvm-commits
llvm-commits at lists.llvm.org
Mon Jun 13 06:02:03 PDT 2016
Should musl really be an environment? What happens when targeting ARM,
do we get a gnueabi+musl? Is it used as an environment when
On 13 June 2016 at 08:20, Lei Zhang via cfe-commits
<cfe-commits at lists.llvm.org> wrote:
> 2016-06-13 3:07 GMT+08:00 Joerg Sonnenberger <joerg at bec.de>:
>> On Sun, Jun 12, 2016 at 10:51:11AM +0800, Lei Zhang via llvm-commits wrote:
>>> I'm replying to this thread; sorry I wasn't subscribed to the list,
>>> thus cannot reply to it directly.
>>> Joerg, thanks for your reply. Could you please tell me what kind of
>>> test cases I should prepare?
>> The target/triple parser has a unit test in
>> unittests/ADT/TripleTest.cpp. The rest should get output validation in
>> clang's test/Driver directory. Not sure which one is the primary
>> GNU/Linux test.
> Thanks for the pointer :)
> The patches are re-attached with test cases included. Do they look sane enough?
> cfe-commits mailing list
> cfe-commits at lists.llvm.org
More information about the llvm-commits