search for: libcxxrt

...o libunwind, but it doesn’t (or, at least, shouldn’t) need a specific version of LLVM’s implementations of these. In contrast, clang needs a bunch of LLVM libraries and depends on precise versions. In FreeBSD, we used to ship libsupc++, libstdc++ and GCC’s libunwind. We then switched to shipping libcxxrt, libstdc++, and GCC’s libunwind, then to shipping libcxxrt, libc++, and GCC’s libunwind, and are now switching to shipping libcxxrt, libc++, and LLVM’s libunwind. We build all of these with clang and gcc. When we import a new lldb and clang (and, soon, when we start to import lld), we need to do...

On 28 Jul 2016 8:36 a.m., "David Chisnall via llvm-dev" < llvm-dev at lists.llvm.org> wrote: > This does not apply to libc++. We support building the entire LLVM suite with other C++ standard library implementations (at least libstdc++, and I think also with Visual Studio’s implementation), so there is no dependency of anything on libc++. Similarly, we support building libc++

...rs are set up at the /usr/include/c++/v1 directory--it's where clang expects them to be on FreeBSD, so no need for the "-I" options in the CMAKE_CXX_FLAGS variable. Unfortunately, clang (both v3.3 used to be the default compiler on FreeBSD 9.2 and recent revisions) do not add the libcxxrt run-time lib to ld options what means we have to ask cmake to add it for us (see the cmake invocation at the end of the config list). This approach let us build and run the common sanitizers tests with no unexpected failures. The only issue is that the HAVE_UNIT64_T & Co. tests fail to link...

...l these test failures? Does it seems like they have a >> common root cause and do we have a bug for it? ... > The Clang Tools and Extra Tools Unit tests all appear to crash with: > > exception_ptr not yet implemented This turns out to be caused by libc++ being compiled without -DLIBCXXRT. (In the FreeBSD base system build, we always add this option, so libc++ knows how to handle exceptions.) In the libc++ CMakeFiles, it appears to be governed by LIBCXX_CXX_ABI_LIBNAME, but it isn't being set to the correct value of "cxxrt" on FreeBSD. I am going to try the followin...

On 10/29/13 07:01 AM, Richard Smith wrote: > > [As an aside: I use libc++ for my Clang development (on Ubuntu Linux), > and it works for me (tm). This is with libstdc++ providing the ABI > pieces, rather than libc++abi or libcxxrt, though.] libc++ "works" for us as well, but it can't self host. I don't know if your "works" and my definition of works is 1:1. Can your clang+libc++ build itself multiple levels deep? I believe both ABI alternatives are drop-in replacements and I hope not the root...

...seems like they have a >>> common root cause and do we have a bug for it? > ... >> The Clang Tools and Extra Tools Unit tests all appear to crash with: >> >> exception_ptr not yet implemented > > This turns out to be caused by libc++ being compiled without -DLIBCXXRT. (In the FreeBSD base system build, we always add this option, so libc++ knows how to handle exceptions.) > > In the libc++ CMakeFiles, it appears to be governed by LIBCXX_CXX_ABI_LIBNAME, but it isn't being set to the correct value of "cxxrt" on FreeBSD. I am going to try th...

...;>>> common root cause and do we have a bug for it? >> ... >>> The Clang Tools and Extra Tools Unit tests all appear to crash with: >>> >>> exception_ptr not yet implemented >> >> This turns out to be caused by libc++ being compiled without -DLIBCXXRT. (In the FreeBSD base system build, we always add this option, so libc++ knows how to handle exceptions.) >> >> In the libc++ CMakeFiles, it appears to be governed by LIBCXX_CXX_ABI_LIBNAME, but it isn't being set to the correct value of "cxxrt" on FreeBSD. I am going t...

...-lstdc++ to the link line (or, ideally, -lsupc++, if your distribution ships a separate libsupc++.so). On FreeBSD, we don’t link libc++ to any ABI library. Instead, both libc++.so and libstdc++.so are linker scripts that instruct anything that tries to link libc++ to link libc++.so.{version} and libcxxrt.so.{version}. David

On 12/19/11 7:19 PM, Howard Hinnant wrote: > On Dec 19, 2011, at 7:14 PM, Shea Levy wrote: > >> Hello all, >> >> Is it possible, if using libc++ and compiler-rt, to have a clang with no >> runtime dependencies on any GCC components on Linux? If not, will this >> ever be possible? > We are working on a new libc++abi: http://libcxxabi.llvm.org/ which carries

...oot cause and do we have a bug for it? >>> ... >>>> The Clang Tools and Extra Tools Unit tests all appear to crash with: >>>> >>>> exception_ptr not yet implemented >>> >>> This turns out to be caused by libc++ being compiled without -DLIBCXXRT. (In the FreeBSD base system build, we always add this option, so libc++ knows how to handle exceptions.) >>> >>> In the libc++ CMakeFiles, it appears to be governed by LIBCXX_CXX_ABI_LIBNAME, but it isn't being set to the correct value of "cxxrt" on FreeBSD. I am...

Hello, I wanted to try the new c++ stuff, ie clang-3.2, libc++ and libcxxrt, so I used poudriere to build a jail setup for that ( WITH_LIBCPLUSPLUS=yes in src.conf, CXXFLAGS+=-stdlib=libc++ and libsupc++.so.1 libcxxrt.so.1 in libmap.conf ), and started to build my normal set of packages ( see desktop.list ). Please note that I also have WITH_NEW_XORG=yes and WITH_KMS=yes,...

...doesn’t (or, at least, shouldn’t) need a specific version of LLVM’s implementations of these. In contrast, clang needs a bunch of LLVM libraries and depends on precise versions. Absolutely! > In FreeBSD, we used to ship libsupc++, libstdc++ and GCC’s libunwind. We then switched to shipping libcxxrt, libstdc++, and GCC’s libunwind, then to shipping libcxxrt, libc++, and GCC’s libunwind, and are now switching to shipping libcxxrt, libc++, and LLVM’s libunwind. We build all of these with clang and gcc. When we import a new lldb and clang (and, soon, when we start to import lld), we need to do...

...a bug for it? >>>> ... >>>>> The Clang Tools and Extra Tools Unit tests all appear to crash with: >>>>> >>>>> exception_ptr not yet implemented >>>> >>>> This turns out to be caused by libc++ being compiled without -DLIBCXXRT. (In the FreeBSD base system build, we always add this option, so libc++ knows how to handle exceptions.) >>>> >>>> In the libc++ CMakeFiles, it appears to be governed by LIBCXX_CXX_ABI_LIBNAME, but it isn't being set to the correct value of "cxxrt" on FreeBSD...

...;cbergstrom at pathscale.com>wrote: > On 10/29/13 07:01 AM, Richard Smith wrote: > >> >> [As an aside: I use libc++ for my Clang development (on Ubuntu Linux), >> and it works for me (tm). This is with libstdc++ providing the ABI pieces, >> rather than libc++abi or libcxxrt, though.] >> > libc++ "works" for us as well, but it can't self host. I don't know if > your "works" and my definition of works is 1:1. Can your clang+libc++ build > itself multiple levels deep? > Yes. I use my system g++ for my stage1, I use that comp...

...> Having a sunrise period would allow us to investigate this as well as > report any potentially blocking problems. > [As an aside: I use libc++ for my Clang development (on Ubuntu Linux), and it works for me (tm). This is with libstdc++ providing the ABI pieces, rather than libc++abi or libcxxrt, though.] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131028/e616bba4/attachment.html>

...g symbols from /usr/local/lib/libclucene-shared.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libclucene-shared.so.1 Reading symbols from /usr/lib/libc++.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libc++.so.1 Reading symbols from /lib/libcxxrt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libcxxrt.so.1 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/...

On Tue, Apr 1, 2014 at 1:23 PM, Ivan A. Kosarev <ivan at ivan-labs.com> wrote: > Hi Alexey, > > > On 03/31/2014 09:58 PM, Alexey Samsonov wrote: > > On FreeBSD 9.2 I add a couple custom options to CMAKE_CXX_FLAGS in order > to let clang know which header set it should use, like that: > >> >>> CC=clang CXX=clang++ cmake \ >>>

Since the original buildit script doesn't cover my needs I switched to a custom but really similar script, in the meantime I also got the habit to dig for new flags and support and the __GLIBCXX__ define was hiding some of this errors. I see that other linux-based operating system offer this kind of support and they even use the same core components of my GNU/Linux distribution. You are

15.08.2012, 19:25, "Villmow, Micah" <Micah.Villmow at amd.com>: > Three reasons. > 1) I need to modify the code to support extensions to the standard demangler. > 2) GCC's version is GPL v3. And? BTW, there is BSD-licensed implementation of __cxa_demangle in libcxxrt > 3) Need windows support. > > Micah -- Regards, Konstantin

PR16537 demonstrates a defect in Clang/LLVM conformance with the Itanium C++ ABI. I poked around a little in the Clang, LLVM, and test-suite tests but didn't see anything that obviously looked like an attempt at an ABI conformance test set. Is there a conformance test set that I missed? If not, does anybody think they are privately testing ABI conformance? Alternatively, does anybody know