similar to: LLVM building problem

> -----Original Message----- > From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Tom Stellard > via llvm-dev > Sent: Wednesday, April 1, 2020 7:49 PM > To: Itaru Kitayama <itaru.kitayama at gmail.com> > Cc: Nemanja Ivanovic via llvm-dev <llvm-dev at lists.llvm.org> > Subject: Re: [llvm-dev] LLD issue on a massively parallel build machine >

On Thu, Apr 2, 2020 at 11:35 AM Itaru Kitayama via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Setting LLVM_PARALLEL_LINK_JOBS > did not help a week or two weeks ago’s lld. > > But recent commits to lld might reflect the variable correctly. > FYI: the variable has nothing to do with lld itself (not commits to lld would change the behavior of this flag), as far as I know

Dear all, I have a couple of questions of SPIR-V implementation for OpenCL. The first one is about the tool spirv-opt from the project SPIRV-TOOLS. When you use that tool like "spirv-opt test.spv -o test.spv", it changes something at the file or it does not do anything by not using any flag? I think it is like a "No action" flag but I am not 100% sure about that. The second

Hi Alexey, Your reply has been a great help to me,your way of explain the different types of compilation is very detailed and easy to understand. Even so, I have a couple of questions. 1) What do yourefer by OpenCL RT? 2) Could you give me some examples of an open-source OpenCL implementation and update optimization pipeline? Thank you in advance. Regards El vie., 20 sept. 2019 a las 12:34,

Dear all, I'm newbie in LLVM. I would like to know if it is available an optimizer for OpenCL in LLVM, in the same way as the 'opt' command in LLVM. Concretely, if it is possible to perform individual optimizations/transformations over OpenCL code (either at source or bitcode representation) as it can be done for C code using: - 'clang' to generate the .bc file(s) -

Hello, I am a computer engineering student and compression hobbyst and have recently developed a new entropy coding algorithm. It can be used to achieve compression proper of arithmetic coders at very high speeds -almost like Huffman codecs-. Since it could be of interest to you, I send it as an attachment -code and technical report-. Please, drop me a line in case you have any doubt or

On Thu, Feb 25, 2016 at 7:37 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> On Feb 24, 2016, at 9:55 PM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi, >> >> I switched from "configure and make" to "cmake" build-system and >> wanted to speedup my build. >> >> In my build-script I

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:

On Sun, Sep 18, 2016 at 12:32 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> On Sep 17, 2016, at 3:19 PM, Carsten Mattner <carstenmattner at gmail.com> wrote: >> >> So, when I embark on the next ThinLTO try build, probably this Sunday, >> should I append -Wl,-plugin-opt,jobs=NUM_PHYS_CORES to LDFLAGS >> and run ninja without -j or

You can set the LLVM_PARALLEL_LINK_JOBS CMake variable to restrict the number of link jobs. On Sat, Aug 8, 2020 at 3:00 PM Neil Nelson via llvm-dev < llvm-dev at lists.llvm.org> wrote: > https://ninja-build.org/manual.html > > ninja -h prints help output. Many of Ninja’s flags intentionally match > those of Make; e.g ninja -C build -j 20 changes into the build directory >

> On Aug 8, 2020, at 3:32 PM, Dmitry Mikushin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Cool, thanks! > > вс, 9 авг. 2020 г. в 00:27, Petr Hosek <phosek at chromium.org <mailto:phosek at chromium.org>>: > You can set the LLVM_PARALLEL_LINK_JOBS CMake variable to restrict the number of link jobs. IMO, a more thorough solution would be switching to

> On Mar 1, 2016, at 9:57 AM, Chris Bieneman <cbieneman at apple.com> wrote: > > There are a few notes I'd like to add to this thread. > > (1) we have a number of places throughout out CMake build where we use features from newer CMakes gated by version checks. Most of these features are performance or usability related. None of them are correctness. Using the latest

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

> Which combination of cmake/ninja versions are you using (latest are > v3.4.3 and v1.6.0)? > With this combination I could reduce build-time down from approx. 3h down to 01h20m. $ egrep -i 'jobs|ninja' llvm-build/CMakeCache.txt //Program used to build from build.ninja files. CMAKE_MAKE_PROGRAM:FILEPATH=/opt/cmake/bin/ninja //Define the maximum number of concurrent compilation

Hi, I am seeing an LLVM build failure with recent LLD on x86 like: [...] lib/libLLVMCodeGen.a lib/libLLVMBitWriter.a lib/libLLVMScalarOpts.a lib/libLLVMAgg ressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMDebugInfoDWARF.a lib/lib LLVMMCDisassembler.a lib/libLLVMExecutionEngine.a lib/libLLVMTarget.a lib/libLLVMAnalysis.a lib/libLLVMProfil eData.a

> On Feb 24, 2016, at 9:55 PM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi, > > I switched from "configure and make" to "cmake" build-system and > wanted to speedup my build. > > In my build-script I use... > > CMAKE_JOBS="1" > ##CMAKE_JOBS=$(($(getconf _NPROCESSORS_ONLN)+1)) >

How big is your project? LTO eats RAM even faster than chrome. For example linking clang with LTO could take 16GB of ram. Have you tried using LTO on your project on that machine, or is it your first time? Piotr On Sat, Jul 23, 2016 at 2:42 AM, Sedat Dilek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Thu, Jul 21, 2016 at 12:01 PM, Sedat Dilek <sedat.dilek at

For faster builds and rebuilds you should definitely read: https://blogs.s-osg.org/an-introduction-to-accelerating-your-build-with-clang/ https://blogs.s-osg.org/a-conclusion-to-accelerating-your-build-with-clang/ Hope this helps! On Tue, Mar 1, 2016 at 9:17 PM, ChrisBieneman via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > > On Mar 1, 2016, at 10:01 AM, Mehdi Amini

Hey Chris, Sedat was asking for a way to "to speedup my build" and those blog posts were really helpful to me. Anyway LLVM_DISTRIBUTION_COMPONENTS sounds very cool, hope you will push your code soon! On Tue, Mar 1, 2016 at 11:32 PM, Chris Bieneman <cbieneman at apple.com> wrote: > Fabio, the work I was mentioning here is an extension beyond those blog > posts. > >

On linux (not Windows) I doubt using Ninja vs make will make drastic differences.. (Others with actual numbers please chime in to correct me) /* I think the difference could be more beneficial if you're doing incremental builds, but I don't think that is what you're doing.. */ On Thu, Feb 25, 2016 at 1:51 PM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On