[cfe-dev] [buildbots][libunwind] Why is libunwind not built / tested on most bots?

[Daniel Sanders via cfe-dev]

> Is this an intentional omission? If not, I think it would be good to make them build+test libunwind as well, I don't think it adds a lot of overhead. I can update the bot configurations if you are all happy with allowing libunwind testing.

It's intentional for MIPS. We haven't added MIPS to that libunwind yet.

From: cfe-dev [mailto:cfe-dev-bounces at lists.llvm.org] On Behalf Of Asiri Rathnayake via cfe-dev
Sent: 27 May 2016 13:11
To: Asiri Rathnayake
Cc: nd; cfe-dev at lists.llvm.org
Subject: Re: [cfe-dev] [buildbots][libunwind] Why is libunwind not built / tested on most bots?

Come to think of it, should we make -DLIBCXXABI_USE_LLVM_UNWINDER=ON the default cmake option?

- Asiri

On Fri, May 27, 2016 at 10:38 AM, Asiri Rathnayake via cfe-dev <cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>> wrote:
Hello,

While going through the list of buildbots for libcxx [1], I realized that only the arm buildbot (Renato) is setup to build+test libunwind [2]. None of the other bots seem to pass the -DLIBCXXABI_USE_LLVM_UNWINDER=ON option. They all seem to checkout the sources but then forgets about libunwind.

Is this an intentional omission? If not, I think it would be good to make them build+test libunwind as well, I don't think it adds a lot of overhead. I can update the bot configurations if you are all happy with allowing libunwind testing.

WDYT?

Thanks.

/ Asiri

[1] http://lab.llvm.org:8011/console
[2] http://lab.llvm.org:8011/builders/libcxx-libcxxabi-arm-linux/builds/1009/steps/cmake/logs/stdio

_______________________________________________
cfe-dev mailing list
cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20160527/9dc31a6c/attachment.html>