[llvm-bugs] [Bug 43140] libcxx tests fail when built with gcc (symbol visibility problem) std::__1::__vector_base_common<true>::__throw_length_error() const'

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=43140

Peter Smith <peter.smith at linaro.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|CONFIRMED                   |RESOLVED

--- Comment #6 from Peter Smith <peter.smith at linaro.org> ---
The Arm builder hasn't finished yet, but the other gcc libcxx bots have and
I've done a local build on an Arm machine and this error is now gone.

I'm still getting some failures, as are the bots, but they look to be separate
from this one. Will be worth a look to see if there are other problems when
compiling with gcc.

Finished GCC builders (28 Failures, down from over 400)
http://lab.llvm.org:8011/builders/libcxx-libcxxabi-x86_64-linux-ubuntu-gcc-tot-latest-std/builds/1348
http://lab.llvm.org:8011/builders/libcxx-libcxxabi-x86_64-linux-ubuntu-gcc5-cxx11/builds/373

Some of the errors are static asserts, but there are also a few undefined
symbol link errors.

Arm v7 builder, currently testing, will be finished in a few hours:
http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-armv7-linux-noexceptions/builds/1103/steps/test.libcxx/logs/stdio

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190828/daed1fdb/attachment-0001.html>