Should musl really be an environment? What happens when targeting ARM, do we get a gnueabi+musl? Is it used as an environment when configuring gcc?
Cheers, Rafael On 13 June 2016 at 08:20, Lei Zhang via cfe-commits <cfe-commits@lists.llvm.org> wrote: > 2016-06-13 3:07 GMT+08:00 Joerg Sonnenberger <jo...@bec.de>: >> On Sun, Jun 12, 2016 at 10:51:11AM +0800, Lei Zhang via llvm-commits wrote: >>> Hi, >>> >>> I'm replying to this thread; sorry I wasn't subscribed to the list, >>> thus cannot reply to it directly. >>> >>> http://lists.llvm.org/pipermail/cfe-commits/Week-of-Mon-20160606/161733.html >>> >>> 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? > > > Lei > > _______________________________________________ > cfe-commits mailing list > cfe-commits@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits > _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
