<div dir="ltr">Come to think of it, should we make -DLIBCXXABI_USE_LLVM_UNWINDER=ON the default cmake option?<div><br></div><div>- Asiri</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 27, 2016 at 10:38 AM, Asiri Rathnayake via cfe-dev <span dir="ltr"><<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
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.<br>
<br>
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.<br>
<br>
WDYT?<br>
<br>
Thanks.<br>
<br>
/ Asiri<br>
<br>
[1] <a href="http://lab.llvm.org:8011/console" rel="noreferrer" target="_blank">http://lab.llvm.org:8011/console</a><br>
[2] <a href="http://lab.llvm.org:8011/builders/libcxx-libcxxabi-arm-linux/builds/1009/steps/cmake/logs/stdio" rel="noreferrer" target="_blank">http://lab.llvm.org:8011/builders/libcxx-libcxxabi-arm-linux/builds/1009/steps/cmake/logs/stdio</a><br>
<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
</blockquote></div><br></div>