similar to: LLVM build performance with LLVM

David, Yes, I was indeed trying to build LLVM with a Debug build. I'll stop doing that from now on. I am on JSC's JURON machine which has 251 GB of memory on the login node, that's more than sufficient to do a build, I suppose, and the linker is LLD as LLVM has a CMake variable to select the linker. On Fri, Jan 3, 2020 at 11:02 AM David Blaikie <dblaikie at gmail.com> wrote:

As I am facing the serious super slow down: https://bugs.llvm.org/show_bug.cgi?id=44407 , I'd like to learn more about how it can be minimized. When debugging an app, there are times building it with a Debug build LLVM can not be avoided, but a situation like 40 times time increase (40 minutes) is hard to work with. On Fri, Jan 3, 2020 at 11:14 AM David Blaikie <dblaikie at gmail.com>

At least, to obtain enough information from libomptarget while running my offloading app on GPU capable environment, I have to build it with an LLVM which was built in Debug mode. On Sat, Jan 4, 2020 at 4:34 David Blaikie <dblaikie at gmail.com> wrote: > > > On Thu, Jan 2, 2020 at 10:55 PM Itaru Kitayama <itaru.kitayama at gmail.com> > wrote: > >> As I am facing

I have just tried a Release build of LLVM but with LIBOMPTARGET_ENABLE_DEBUG enabled. The app build became super fast, but I can not obtain debugging information that I need at runtime. On Sat, Jan 4, 2020 at 5:03 David Blaikie <dblaikie at gmail.com> wrote: > I'm still confused by that - whether or not the LLVM you built has debug > info in it shouldn't at all change what

Yes, exactly. On Sun, Jan 5, 2020 at 23:43 Mehdi AMINI <joker.eph at gmail.com> wrote: > > > On Fri, Jan 3, 2020 at 8:58 PM Itaru Kitayama via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> I have just tried a Release build of LLVM but >> with >> LIBOMPTARGET_ENABLE_DEBUG enabled. The app build became super fast, but I >> can not obtain

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

On another login node which is 256 (GB)/48 (nodes) JURECA at JSC, I never had an LLD issue without setting -j when executing ninja in the past few weeks. On Thu, Apr 2, 2020 at 7:17 AM Itaru Kitayama <itaru.kitayama at gmail.com> wrote: > Tom, > Then what ratio do you think it’s minimal? > > On Thu, Apr 2, 2020 at 6:11 Tom Stellard <tstellar at redhat.com> wrote: >

On 04/01/2020 01:47 PM, Itaru Kitayama via llvm-dev wrote: > Thanks for the heads up the supercomputer > Is down for maintenance this week. > I’ll give it a try when it gets back. > This doesn't look to me like it's necessarily an lld issue. Trying to build all the sub-projects without limiting the number of ninja jobs is almost guaranteed to run out of memory on a machine

Without seeing more details it's impossible to tell, but it might have been me. https://github.com/llvm/llvm-project/commit/6102310d814ad73eab60a88b21dd70874f7a056f#diff-0f9a49c4e31c311a0010e126cd785f08 changed PHI node equality check, but there were some users that implicitly depended on the old definition of the PHI equality, and didn't verify their implicit assumptions with reality,

On 2020-03-29, Nemanja Ivanovic via llvm-dev wrote: >Glad you got it working. >My suggestion about LLVM_ENABLE_THREADS didn't work because you didn't >apply it when building the build linker. > >When you don't have the ability to rebuild the build compiler, this doesn't >apply. In those cases, I end up doing a dirty hack where I use a wrapper >script with

Renato et al. In the meantime, is there an out of tree branch I mean, other than LLVM trunk so I can test how much I can SVE vectorize my code with it? Arm seemed to gave taken down the GitHub branch for sometime. On Wed, Sep 11, 2019 at 20:41 Renato Golin <rengolin at gmail.com> wrote: > On Wed, 11 Sep 2019 at 06:13, Itaru Kitayama via llvm-dev > <llvm-dev at lists.llvm.org>

Good news, I was able to use up to 37 cores for LLVM build with LLD. The build speed, did not measure precisely though, is comparable to the build with GNU ld case. Thank you all for your help! On Sun, Mar 29, 2020 at 5:04 AM Alex Brachet-Mialot < alexbrachetmialot at gmail.com> wrote: > Yes unfortunately that would limit you to 4 cores. > > There’s no easy way to use lld with

That is slowing down the build visibly, for the speed I should stick with ld at the moment. On Sun, Mar 29, 2020 at 4:42 AM Alexandre Ganea <alexandre.ganea at ubisoft.com> wrote: > Would `taskset -c 0-3 ninja check-all -j4` work? > > > > *De :* Itaru Kitayama <itaru.kitayama at gmail.com> > *Envoyé :* March 28, 2020 3:37 PM > *À :* Alex Brachet-Mialot

$ free -g total used free shared buff/cache available Mem: 376 149 20 1 207 225 Swap: 3 0 3 Too small swap size for a 72-core login machine? On Sun, Mar 29, 2020 at 4:28 AM Alex Brachet-Mialot < alexbrachetmialot at gmail.com> wrote: > Enable threads is for building llvm with

Hi, I am observing the libcxx project can not be built without libcxxabi, but I thought libcxx should not depend upon other projects. Observed on x86. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200102/023ca21b/attachment.html>

Hi, I'm still seeing the same ie trying to produce SVE instructions but resulted in NEONs with Clang as of Sep. 10th. http://lists.llvm.org/pipermail/llvm-dev/2019-March/130788.html -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190910/100290f6/attachment.html>

Hi, On AArch64, I see a lot of warnings like: warning: failed to compute relocation: R_AARCH64_PREL32, Invalid data was encountered while parsing the file when opening object file with llvm-objdump. The llvm-objdump is from trunk at this moment. Is this easy to fix?

I am seeing in the last couples of days llvm plus other projects builds are failing, is this being worked on?

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