search for: llvm_use_split_dwarf

...15 Aug 2019 at 00:22, David Blaikie via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Nothing supported, though might not be too hard to do by hand. > > If you're having long link times, lots of disk usage, and slow gdb startup > time I'd recommend enabling split DWARF (LLVM_USE_SPLIT_DWARF=ON, > and CMAKE_EXE_LINKER_FLAGS_*=-Wl,-gdb-index in cmake) if you haven't > already. > > On Wed, Aug 14, 2019 at 11:40 AM Robert Henry via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> In order to minimize edit/compile/debug turn time, is there a way to &gt...

Hello, My system hangs every time during last stages of building LLVM ( starting at 95% in a CMake build ) using CMake or Ninja, sometime close to the linking of llvm-dysmutil. Could you please suggest tips that could speed up the compilation ? Thank You, Sanjay -------------- next part -------------- An HTML attachment was scrubbed... URL:

...< >> llvm-dev at lists.llvm.org> wrote: >> >>> Nothing supported, though might not be too hard to do by hand. >>> >>> If you're having long link times, lots of disk usage, and slow gdb >>> startup time I'd recommend enabling split DWARF (LLVM_USE_SPLIT_DWARF=ON, >>> and CMAKE_EXE_LINKER_FLAGS_*=-Wl,-gdb-index in cmake) if you haven't >>> already. >>> >>> On Wed, Aug 14, 2019 at 11:40 AM Robert Henry via llvm-dev < >>> llvm-dev at lists.llvm.org> wrote: >>> >>>> In order to mini...

On Tue, Nov 26, 2019 at 10:31 AM David Jones via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Throw hardware at it. > While I agree that this is good advice with the current state of affairs, I don't think we should consider the current situation acceptable. LLVM has a lot of knobs that Tim alluded to, but first time users shouldn't have to search for them to get a

In order to minimize edit/compile/debug turn time, is there a way to compile llvm tools so that the majority of the files are compiled as if for release (eg, no debug symbols), and only the handful of files that I have touched are compiled for debugging? This will reduce the load on the file system, linker and gdb tremendously. At present, AFAICT, it's all or nothing. -------------- next part

The linking state of a Debug build seems to require a humongous amount of memory. My poor little linux machine with 16G of ram swaps its brains out. Waiting for it to finish (if it ever does) is like the old days when you submitted your deck of cards and waited until the next day to see the results. To debug a new backend, is there a way to just get the debug info for the Target/Foo

Unfortunately, from personal experience, LLVM_PARALLEL_LINK_JOBS appears to have no effect for Visual Studio builds, AND some of the tools linked can take up several GB of RAM, so you'll end up with paging issues. I ended up getting a RAM upgrade in order to sensibly build it (note, I think builds with debug information take more memory than those that don't, and also the clang projects

The last time this came up, we agreed something should be done to fix the defaults, but nobody picked it up and ran with it. I think there was consensus, it just needs legwork now. On Thu, Jan 2, 2020 at 11:58 AM Aaron Smith via llvm-dev < llvm-dev at lists.llvm.org> wrote: > There was a recent thread on reducing memory: >

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:

...e(TM) Amplifier XE 2011 // about JIT code LLVM_USE_INTEL_JITEVENTS:BOOL=OFF //Use opagent JIT interface to inform OProfile about JIT code LLVM_USE_OPROFILE:BOOL=OFF //Define the sanitizer used to build binaries and tests. LLVM_USE_SANITIZER:STRING=Address //Use -gsplit-dwarf when compiling llvm. LLVM_USE_SPLIT_DWARF:BOOL=ON //Dependencies for target LLVMipo_LIB_DEPENDS:STATIC= //Dependencies for the target LTO_LIB_DEPENDS:STATIC=general;LLVMAArch64CodeGen;general;LLVMAArch64AsmPrinter;general;LLVMAArch64AsmParser;general;LLVMAArch64Desc;general;LLVMAArch64Info;general;LLVMAArch64Disassembler;general;LLVMAArc...