search for: have_cxxabi_h

..._PREFIX_PATH instead of defining custom variables like LLD_PATH_TO_LLVM_BUILD and LLD_PATH_TO_LLVM_SOURCE. Any objection to that? Also, two files ELFLinkingContext.cpp and MachOLinkingContext.cpp include a private header from the LLVM source tree, "llvm/Config/config.h" to get access to HAVE_CXXABI_H. Can the dependency on HAVE_CXXABI_H be removed? If no, mind if I add a config.h.cmake to LLD's "include/lld/Config"? Thanks, Greg

...ppears that the mangled name is surrounded by parentheses. I guess what could be done is to just write a version of the line stripper per platform. I'd start by only supporting the platforms I have access to, and letting other people contribute the parsing code for their platform. #if HAVE_CXXABI_H #include <cxxabi.h> #endif /// .... static void PrintStackTrace(int skipFrames) { #ifdef HAVE_BACKTRACE // Use backtrace() to output a backtrace on Linux systems with glibc. int depth = backtrace(stackTrace, static_cast<int>(arrayLengthOf(Stac...

I really want to start simple. So if adding a demangler the first objective is to add one that lets us drop the HAVE_CXXABI_H. After that it can be expanded. Cheers, Rafael On 5 May 2016 at 08:58, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 5 May 2016, at 13:47, Rafael Espíndola via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> * Is having an itanium demangler in lib/Sup...

...ables like LLD_PATH_TO_LLVM_BUILD and >> LLD_PATH_TO_LLVM_SOURCE. Any objection to that? >> >> Also, two files ELFLinkingContext.cpp and MachOLinkingContext.cpp >> include a private header from the LLVM source tree, >> "llvm/Config/config.h" to get access to HAVE_CXXABI_H. Can the >> dependency on HAVE_CXXABI_H be removed? If no, mind if I add a >> config.h.cmake to LLD's "include/lld/Config"? > > > I personally would be opposed to adding configure machinery to LLD's build. > It is just duplicating the machinery already in...

...object file generated by the source. > > > On 2016-May-05, at 06:37, Rafael Espíndola via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > I really want to start simple. So if adding a demangler the first > > objective is to add one that lets us drop the HAVE_CXXABI_H. > > > > After that it can be expanded. > > > > Cheers, > > Rafael > > > > > > On 5 May 2016 at 08:58, David Chisnall <David.Chisnall at cl.cam.ac.uk> > wrote: > >> On 5 May 2016, at 13:47, Rafael Espíndola via llvm-dev < > llv...

...a very few modern C++ conveniences. >>> On 2016-May-05, at 06:37, Rafael Espíndola via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> I really want to start simple. So if adding a demangler the first >>> objective is to add one that lets us drop the HAVE_CXXABI_H. >>> >>> After that it can be expanded. >>> >>> Cheers, >>> Rafael >>> >>> >>> On 5 May 2016 at 08:58, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: >>>> On 5 May 2016, at 13:47, Rafael Espíndola...

We are trying out lld ELF on windows. It works great, but a big difference from running it on linux is that it cannot demangle c++ names since there is no itanium demangler available on windows. We have an implementation in libcxxabi/src/cxa_demangle.cpp. I see that there was some discussion about having a version of that in lib/Support, but I don't think a patch was ever posted. So, some

...or FE_ALL_EXCEPT - found -- Looking for FE_INEXACT -- Looking for FE_INEXACT - found -- Looking for mach/mach.h -- Looking for mach/mach.h - not found -- Looking for mach-o/dyld.h -- Looking for mach-o/dyld.h - not found -- Looking for histedit.h -- Looking for histedit.h - found -- Performing Test HAVE_CXXABI_H -- Performing Test HAVE_CXXABI_H - Success -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Looking for pthread_getspecific in pthread -- Looking for pthread_getspecific in pthread - found -- Looking for pthread_rwlock_init in pthread -- Looking for pthre...

I had only a quick view on the blog-texts. It might be that a CLANG generated with LTO/PGO speeds up the build. Can you confirm this? Can you confirm binutils-gold speed up the build? Has LLVM an own linker? Can be used? Speedup the build? Yesterday night I loooked through available CMAKE/LLVM variables... ### GOLD # CMAKE_LINKER:FILEPATH=/usr/bin/ld #

Hello, Le 12/12/2016 à 18:29, Hans Wennborg a écrit : > +Sylvestre who knows about these things. > > On Thu, Dec 8, 2016 at 2:24 AM, Kris van Rens via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> L.S., >> >> I'm currently in the process of creating Debian packages for >> clang/llvm release 3.9.0. For this I'm using the steps as explained on

On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: [ brutal-snip ] ... > [ TODO#S: Before doing a 2nd build (and in a 3rd run using more > optimized binaries) ] > > How do I anable LTO via CMAKE? > > > LLVM_ENALBLE_LTO=On > [ v4 of my build-script attached ] Hi Chris, thanks for the response! That seems to work (see below). $ cd

Trying to run a self host "ninja check-clang" with ASan enabled I hit a /lot/ of errors like this (strangely I hit none of these in check-llvm, only in check-clang): Any ideas? ==10525==ERROR: AddressSanitizer failed to deallocate 0x10800 (67584) bytes at address 0x631000014800 ==10525==AddressSanitizer CHECK failed:

...RANDOM:INTERNAL= //Have symbol backtrace HAVE_BACKTRACE:INTERNAL=1 //Have symbol ceilf HAVE_CEILF:INTERNAL=1 //Is circo available ? HAVE_CIRCO:INTERNAL=1 //Have symbol closedir HAVE_CLOSEDIR:INTERNAL=1 //Have include CrashReporterClient.h HAVE_CRASHREPORTERCLIENT_H:INTERNAL= //Have include cxxabi.h HAVE_CXXABI_H:INTERNAL=1 //Test HAVE_CXX_ATOMICS64_WITHOUT_LIB HAVE_CXX_ATOMICS64_WITHOUT_LIB:INTERNAL=1 //Test HAVE_CXX_ATOMICS_WITHOUT_LIB HAVE_CXX_ATOMICS_WITHOUT_LIB:INTERNAL=1 //Have symbol arc4random HAVE_DECL_ARC4RANDOM:INTERNAL= //Have symbol FE_ALL_EXCEPT HAVE_DECL_FE_ALL_EXCEPT:INTERNAL=1 //Have symbol...