search for: belley

From: Philip Reames <listmail at philipreames.com<mailto:listmail at philipreames.com>> Date: mardi 8 septembre 2015 12:50 To: Benoit Belley <benoit.belley at autodesk.com<mailto:benoit.belley at autodesk.com>>, "llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>" <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> Subject: Re: [llvm-dev] LLVM struct, alloca, SROA and the en...

...nker::ImportIntrinsicGlobalVariables flag. The patch includes a unit test reproducing the problem. Hopefully, that will help getting more feedback. Note that it might take a while before I am allowed to upload the patch since I need approval from Autodesk Legal department. Cheers, Benoit Benoit Belley Sr Principal Developer M&E-Product Development Group MAIN +1 514 393 1616 DIRECT +1 438 448 6304 FAX +1 514 393 0110 Twitter <http://twitter.com/autodesk> Facebook <https://www.facebook.com/Autodesk> Autodesk, Inc. 10 Duke Street Montreal, Quebec, Canada H3C 2L7 www.autodesk.c...

...rantee that the linkonce will be availabe at link // time (by promoting it to weak for instance). Are these obsolete comments ? Should these be cleaned-up ? If so, how ? Thanks again, Benoit From: Peter Collingbourne <peter at pcc.me.uk> Date: mardi 20 juin 2017 à 13:51 To: Benoit Belley <benoit.belley at autodesk.com> Cc: David Blaikie <dblaikie at gmail.com>, llvm-dev <llvm-dev at lists.llvm.org>, Lang Hames <lhames at gmail.com>, Teresa Johnson <tejohnson at google.com> Subject: Re: [llvm-dev] JIT, LTO and @llvm.global_ctors: Looking for advise...

...hmark). Is there any guidelines for specifying the alignment of LLVM structs allocated by alloca instructions ? Is rounding down to the structure size to the next power of 2 a good strategy ? Will the MemCpy pass issue moves of up to 64-bytes on AVX-512 capable processors ? Cheers, Benoit Benoit Belley Sr Principal Developer M&E-Product Development Group MAIN +1 514 393 1616 DIRECT +1 438 448 6304 FAX +1 514 393 0110 Twitter<http://twitter.com/autodesk> Facebook<https://www.facebook.com/Autodesk> Autodesk, Inc. 10 Duke Street Montreal, Quebec, Canada H3C 2L7 www.autodesk.com&lt...

...remove the entry block) > > > So this needs to be fixed. > I marked it with a TODO. > If you want to do this, maybe refactor out the code for deleting dead > blocks from SCCP/DCE, and then submit the patch, it would be great. > > > On Wed, Mar 25, 2015 at 10:47 AM, Benoit Belley < > Benoit.Belley at autodesk.com> wrote: > >> Hi everyone, >> >> >> I am wondering what¹s stopping the LLVM optimizer (opt -O3) from >> eliminating the apparently useless « icmp sgt » instruction in the >> following piece of LLVM IR. >> >&gt...

..._MACOSX directives from being emitted into the LLVM generated object files. Any suggestions how to go about fixing LLVM to generate the correct LC_VERSION_MIN_MACOSX minimum SDK version number ? There seems to be no way to pass this information correctly through the Triple! Thanks, Benoit Benoit Belley Sr Principal Developer M&E-Product Development Group MAIN +1 514 393 1616 DIRECT +1 438 448 6304 FAX +1 514 393 0110 Twitter<http://twitter.com/autodesk> Facebook<https://www.facebook.com/Autodesk> Autodesk, Inc. 10 Duke Street Montreal, Quebec, Canada H3C 2L7 www.autodesk.com&lt...

...ate for our usage pattern ? Should we directly use llvm::IRMover instead ? 2. Or, is our patch to ModuleLinker::run() the way to go ? Should we submit back a patch along these lines ? 3. Other suggestions ? [Note] We are currently using LLVM 4.0.1-rc2. Cheers, Benoit Benoit Belley Sr Principal Developer M&E-Product Development Group MAIN +1 514 393 1616 DIRECT +1 438 448 6304 FAX +1 514 393 0110 Twitter <http://twitter.com/autodesk> Facebook <https://www.facebook.com/Autodesk> Autodesk, Inc. 10 Duke Street Montreal, Quebec, Canada H3C 2L7 www.autodesk.c...

...a !{metadata !1, metadata !2, metadata !3} > !2 = metadata !{metadata !"llvm.vectorizer.width", i32 1} > !3 = metadata !{metadata !"llvm.vectorizer.unroll", i32 1} > !4 = metadata !{metadata !4, metadata !2, metadata !3} Thanks for you help, Benoit Benoit Belley Sr Principal Developer M&E-Product Development Group MAIN +1 514 393 1616 DIRECT +1 438 448 6304 FAX +1 514 393 0110 Twitter <http://twitter.com/autodesk> Facebook <https://www.facebook.com/Autodesk> Autodesk, Inc. 10 Duke Street Montreal, Quebec, Canada H3C 2L7 www.autodesk.com &lt...

...ill leave dangling pointers to its own "writeout" and "flush" functions in the static writeout_fn and flush_fn lists of another shared library. These dangling pointers lead to crashes when the other shared library is unloaded or when the program exits. ‹‹‹‹‹‹‹‹‹‹‹‹‹‹ Benoit Belley Sr Principal Developer M&E-Product Development Group Autodesk, Inc. 10 Duke Street Montreal, Quebec, Canada H3C 2L7 www.autodesk.com <http://www.autodesk.com/>

Hi Lang, > MCJIT does not compile lazily (though it sounds like that's not an issue here?) That is not an issue here since the code JIT's once (a few secs) and then run the generated machine code for hours. > Morten - Can you share any test cases that demonstrate the slowdown. I'd love to take a look at this. The code is massive so not practical. However I will try and

Hi All, The general initializer support patch has landed (see 85fb997659b plus follow up fixes). Some quick background: Until now ORC, like MCJIT, has handled static initializer discovery by searching for llvm.global_ctors and llvm.global_dtors arrays in the IR added to the JIT. This approach suffers from several drawbacks: 1) It provides no built-in support for other program representations:

...ondents have seen similar issues, either in compilation time or in reduced code quality in the generated code. Some of the thread participants will be providing specific examples so they can be investigated. It's possible the issue is something as simple as a different default somewhere. Benoit Belley noted [they saw regressions due to their frontend's use of allocas in 3.7](http://lists.llvm.org/pipermail/llvm-dev/2016-February/094946.html). * Lang Hames kicked off a long discussion about [error handling in LLVM libraries](http://lists.llvm.org/pipermail/llvm-dev/2016-February/094804.html)...

Hi, Not sure whether this matches your use case, but the Orc-based JIT used in LLI appears to be using `llvm::orc::LocalCXXRuntimeOverrides` (http://llvm.org/doxygen/classllvm_1_1orc_1_1LocalCXXRuntimeOverrides.html) to override `__cxa_atexit`: https://github.com/llvm-mirror/llvm/blob/release_50/tools/lli/OrcLazyJIT.h#L74