search for: alexbrachetmialot

...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 <mailto:alexbrachetmialot at gmail.com>> >> wrote: >> > >> >> > >>> Yes unfortunately that would limit you to 4 cores. >> > >>> >> > >>> There’s no easy way to use lld with —no-threads w...

...>> 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 <mailto:alexbrachetmialot at gmail.com>> wrote: > >> > >>> Yes unfortunately that would limit you to 4 cores. > >>> > >>> There’s no easy way to use lld with —no-threads with our build system at > >>>...

Thanks for the reply. Typing in my username and clicking "Forgot password?" got me a link I could use to log in. It'd still be good if federated login worked again. Is there an upstream issue for this? On Thu, Nov 28, 2019 at 5:09 PM Alex Brachet-Mialot < alexbrachetmialot at gmail.com> wrote: > Yes this was broken for me too, there was another post on here about this > a few weeks ago too. I forget what I did to fix it. I think I just logged > in with my email and somehow got my account back, I think because I used > the email associated with that go...

...as 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 —no-threads with our build system at >>> the moment unfortunately. >>> >>> I also had just been using ld.gold, bu...

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 —no-threads with our build system at > the moment unfortunately. > > I also had just been using ld.gold, but will switch now that numactl works > for me. > &...

...gt; consistent across tools (either always read from stdin or no default at all >> /give error messages) >> >> >> >> *From:* James Henderson <jh7370.2008 at my.bristol.ac.uk> >> *Sent:* Wednesday, June 26, 2019 2:31 AM >> *To:* Alex Brachet-Mialot <alexbrachetmialot at gmail.com> >> *Cc:* Fāng-ruì Sòng <maskray at google.com>; LLVMDev < >> llvm-dev at lists.llvm.org>; Jordan Rupprecht <rupprecht at google.com>; Chen, >> Yuanfang <Yuanfang.Chen at sony.com> >> *Subject:* Re: [llvm-dev] [RFC] [tools] Changing Be...

...-O flag that created the problem. But it pointed me in the right direction, when I passed -fno-experimental-new-pass-manager it started to show the error. My guess is that the new pass manager is more aggressive in removing UB? Thanks, Tobias On Mon, Feb 3, 2020 at 5:29 PM Alex Brachet-Mialot <alexbrachetmialot at gmail.com> wrote: > > I haven’t looked at the code gen yet because I’m not on my computer right now but I suspect that at -Os the compiler is optimizing this away because it knows it to be undefined behavior. Try with -O0. > > On Mon, Feb 3, 2020 at 10:53 AM Tobias Hieta via llvm-...

...n 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 <alexbrachetmialot at gmail.com> > *Cc :* Alexandre Ganea <alexandre.ganea at ubisoft.com>; LLVM Dev < > llvm-dev at lists.llvm.org>; Nemanja Ivanovic <nemanja.i.ibm at gmail.com> > *Objet :* Re: [llvm-dev] LLD issue on a massively parallel build machine > > > > $ free -g &gt...

...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 or without thread support. To my > knowledge it has no effect on the build system. > > Like was discussed above you could try limiting the number of processes > created (assuming your lld was after that commit) with...

...rules to identifiers >> after `@parameter`. Since lld doesn't use doxygen comments, it is >> fine for now, but before moving forward, I'll address that. Thank >> you for pointing that out. >> >> On Wed, Jul 10, 2019 at 8:20 PM Alex Brachet-Mialot >> <alexbrachetmialot at gmail.com> wrote: >> >> Also, now that I think about it, I believe doxygen will fail to >> build if the @parameter comments aren't changed to match the new >> names, my guess is it case sensitive. So perhaps we will need to >> find a way to manually change t...

...with `@parameter` and apply the same name conversion rules to identifiers after `@parameter`. Since lld doesn't use doxygen comments, it is fine for now, but before moving forward, I'll address that. Thank you for pointing that out. On Wed, Jul 10, 2019 at 8:20 PM Alex Brachet-Mialot < alexbrachetmialot at gmail.com> wrote: > Also, now that I think about it, I believe doxygen will fail to build if > the @parameter comments aren't changed to match the new names, my guess is > it case sensitive. So perhaps we will need to find a way to manually change > these names for doxygen co...

My personal preference is that llvm-readelf only show the elf related options with -help and show all with -help-hidden. There is support for this in CommandLine.h, but I don't know how tricky it gets when we don't want them to be hidden for llvm-readobj. I haven't looked into this fully. For some reference, I have compiled how the other alias tools are handled. Many of these are

Like James, Michael suggested, I would prefer the default behavior be consistent across tools (either always read from stdin or no default at all /give error messages) From: James Henderson <jh7370.2008 at my.bristol.ac.uk> Sent: Wednesday, June 26, 2019 2:31 AM To: Alex Brachet-Mialot <alexbrachetmialot at gmail.com> Cc: Fāng-ruì Sòng <maskray at google.com>; LLVMDev <llvm-dev at lists.llvm.org>; Jordan Rupprecht <rupprecht at google.com>; Chen, Yuanfang <Yuanfang.Chen at sony.com> Subject: Re: [llvm-dev] [RFC] [tools] Changing Behavior of LLVM binutils When No File Is S...

Hi, I log in to Phab using my @chromium account with the "Log In or Register Google" button on https://reviews.llvm.org/auth/start/?next=%2F . That has worked fine for me, but now it fails with ``` Auth > Unhandled Exception ("Exception") Expected to retrieve an "account" email from Google Plus API call to identify account, but failed. ``` Is anyone else

Alex : Can you please try `numactl` or `taskset` after https://github.com/llvm/llvm-project/commit/09158252f777c2e2f06a86b154c44abcbcf9bb74 ? There was a tiny bug in how sched_getaffinity() was used, see: https://reviews.llvm.org/D75153#1942336 De : Alex Brachet-Mialot <alexbrachetmialot at gmail.com> Envoyé : March 28, 2020 12:11 PM À : Itaru Kitayama <itaru.kitayama at gmail.com> Cc : LLVM Dev <llvm-dev at lists.llvm.org>; Alexandre Ganea <alexandre.ganea at ubisoft.com>; Fāng-ruì Sòng <maskray at google.com> Objet : Re: [llvm-dev] LLD issue on a massiv...

Hi, I'm using clang ast for a while now to do meta compilation, and I just fell into a problem when trying to parse vulkan library which has extern "C" in it. Every symbol inside extern "C" seem to be striped from the TU and ast. I tried to #undef __cplusplus and this time I got the symbols into the AST. I first supposed it was a problem with missing includes or else, but

Rui, I have created D64474 to change comments explicitly stating the parameter names for constants ( /*parameterName=*/<constant> ). I did this by hand to match the new variable names. Do you know if there would be a way to update these comments with a tool similar to what you used to change these names? Perhaps it would be much more difficult, I'm guessing clang's AST doesn't

...b.com/llvm/llvm-project/commit/09158252f777c2e2f06a86b154c44abcbcf9bb74 >> ? >> >> >> >> There was a tiny bug in how *sched_getaffinity*() was used, see: >> https://reviews.llvm.org/D75153#1942336 >> >> >> >> *De :* Alex Brachet-Mialot <alexbrachetmialot at gmail.com> >> *Envoyé :* March 28, 2020 12:11 PM >> *À :* Itaru Kitayama <itaru.kitayama at gmail.com> >> *Cc :* LLVM Dev <llvm-dev at lists.llvm.org>; Alexandre Ganea < >> alexandre.ganea at ubisoft.com>; Fāng-ruì Sòng <maskray at google.com> &...

Hello, I am building sanitizers for our different platforms and trying to use it in an example program, but while it seems like ASAN is running it's init functions (see stdout below with ASAN_OPTIONS=verbosity=1) it never catches anything in the program. This is LLVM 8.0.1 btw. I was using this small test case: int main(int argc, char** argv) { int *array = new int[100]; delete []

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