similar to: [LLVMdev] libc++ builds

On Fri, Feb 20, 2015 at 7:02 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > 2. We need to clarify how libstdc++ and libsupc++ can be used as > > libc++'s ABI library and explicitly define the level of support for > > these configurations. Are there any people using this functionality? > > These configurations have been broken for GCC >= 4.9.2 and I haven't

Hi All, Currently libc++ does not list linux as a supported platform. This should change. I think we should be able to list linux (with libc++abi) as a supported configuration. but there are some issues I would like to see resolved first. 1. We should add CMake support for building libc++ against a static libc++abi. If libc++ is linked to a shared libc++abi the resulting library can only be used

On 5 Jun 2017, at 15:17, Jonathan Roelofs via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 6/5/17 5:17 AM, Dmitry Golovin via llvm-dev wrote: >> I'm trying to build LLVM, Clang, LLD, compiler-rt, libc++, libc++abi and libunwind with musl-based toolchain. >> >> The configuration is the following: >> >> LIBCXX_HAS_MUSL_LIBC=ON >>

+glider The compiler hardly matters here, I would expect the same failures with clang. Alex, could you please take a look? --kcc On Thu, Nov 29, 2012 at 9:55 PM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > Nick, > Can you take a quick look at the asan_eh_bug.tar.bz testcase > I uploaded into the newly opened radr://12777299, "potential > pthread/eh bug exposed

Nick, Can you take a quick look at the asan_eh_bug.tar.bz testcase I uploaded into the newly opened radr://12777299, "potential pthread/eh bug exposed by libsanitizer". The FSF gcc developers have ported llvm.org's asan code into FSF gcc (and are keeping it synced to the upstream llvm.org code). I have been helping with the darwin build and testing -fsanitize=address against the

Hi There, I am trying to build a cross-compiler for an architecture with MIPS like ISA. To begin with, I built a toolchain for MIPSr2 which uses: Clang-3.1 for preprocessing, compiling, optimizing; Binutils-2.22 for assembling and linking; Newlib-1.20.0 as the standard C library implementation. I modified the Clang Driver to use the correct binutils tools and linker scripts. Compiling Newlib with

I'm trying to build LLVM, Clang, LLD, compiler-rt, libc++, libc++abi and libunwind with musl-based toolchain. The configuration is the following: LIBCXX_HAS_MUSL_LIBC=ON LIBCXX_HAS_GCC_S_LIB=OFF CLANG_DEFAULT_CXX_STDLIB=libc++ CLANG_DEFAULT_LINKER=lld CLANG_DEFAULT_RTLIB=compiler-rt LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl LLVM_TARGET_ARCH=x86_64

On 28 Jul 2016, at 08:59, Renato Golin <renato.golin at linaro.org> wrote: > > 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

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++

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

On Fri, Feb 14, 2014 at 1:29 PM, Howard Hinnant <hhinnant at apple.com> wrote: > On Feb 14, 2014, at 4:23 PM, Marshall Clow <mclow.lists at gmail.com> wrote: > >> On Feb 14, 2014, at 1:09 PM, Howard Hinnant <hhinnant at apple.com> wrote: >> >>> Author: hhinnant >>> Date: Fri Feb 14 15:09:01 2014 >>> New Revision: 201432 >>>

On Feb 14, 2014, at 1:09 PM, Howard Hinnant <hhinnant at apple.com> wrote: > Author: hhinnant > Date: Fri Feb 14 15:09:01 2014 > New Revision: 201432 > > URL: http://llvm.org/viewvc/llvm-project?rev=201432&view=rev > Log: Remove myself as owner of libc++ > > Modified: > llvm/trunk/CODE_OWNERS.TXT > > Modified: llvm/trunk/CODE_OWNERS.TXT > URL:

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, as well as using the

On Thu, Aug 29, 2013 at 07:40:46PM +0200, Duncan Sands wrote: > Hi Jack, > > On 29/08/13 18:35, Jack Howarth wrote: >> Duncan, >> Is there a long term plan for handling the conflicting c++ libraries in building >> dragonegg? In particular, as vendors switch their clang++ system compilers to default >> to -stdlib=libc++, the resulting builds of llvm against

On May 11, 2010, at 9:32 PM, David Leimbach wrote: > > libc++: > > 5 seconds > > libstdc++: > > 22 seconds > > (smaller is better) > > Is this libstdc++ with or without rvalue references? > > How about compile times? Having used Go a bit, I've been quite fond of how short the code, compile, test loop ends up being. Tonight compile times

On Fri, Nov 30, 2012 at 01:41:05PM +0400, Kostya Serebryany wrote: > Just want to remind everyone that we plan to stop using mach_override in > asanin favor of OSX's native function interposition. > So, we probably don't want to spend too much effort fixing mach_override. > > --kcc Kostya, Unless I am misunderstanding the code in asan/asan_intercepted_functions.h,

Duncan, Is there a long term plan for handling the conflicting c++ libraries in building dragonegg? In particular, as vendors switch their clang++ system compilers to default to -stdlib=libc++, the resulting builds of llvm against those compilers will be using the libc++ ABI but the dragonegg plugin will still need to be built against the libstdc++ ABI. For now, the only work-around appears to

On May 11, 2010, at 7:26 PM, David Greene wrote: > On Tuesday 11 May 2010 15:43:21 Chris Lattner wrote: >> Hi All, >> >> LLVM now includes a C++ standard library, written by Howard Hinnant. You >> can read about it here: >> http://blog.llvm.org/2010/05/new-libc-c-standard-library.html >> >> Or get the code here: >> svn co

+kremenek, ganna On Sat, Dec 1, 2012 at 4:33 AM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > On Fri, Nov 30, 2012 at 01:41:05PM +0400, Kostya Serebryany wrote: > > Just want to remind everyone that we plan to stop using mach_override in > > asanin favor of OSX's native function interposition. > > So, we probably don't want to spend too much effort fixing

On Tue, May 11, 2010 at 5:40 PM, Andrew Sutton <andrew.n.sutton at gmail.com>wrote: > > What's driving libc++? >> >> The possibility of being a superior solution. >> > > I thought "to support Apple applications" from the previous post was > sufficient motivation :) Either way, I'm excited about a new library. Plus, > it looks a little