similar to: [LLVMdev] Position Dependent Loading in LLVM Modules

Thanks James, Let me rephrase my question: How do I insert metadata into llvm modules (bit code files)? - Am

To compile an auto-tooled project to bitcode, I used to use plugin-opt=save-temps switch as explained in: http://gbalats.github.io/2015/12/10/compiling-autotooled-projects-to-LLVM-bitcode.html. This switch works with LLVM 3.8.0. However, it seems to have no effect with LLVM 5.0.0. I can see intermediate bitcode files on disk, but not the final one. Is the option removed altogether? Has the switch

As I've mentioned before[1] I've been regularly attempting to build the FreeBSD/amd64 base system with lld, in order to keep track of progress and identify issues on an ongoing basis. As of last November a 'buildword' (i.e., userland build) ran to completion, with several workarounds applied to the FreeBSD base system. However, the result did not actually work. I'm pleased to

Would you say that embedding the LLVM linker is a practical way to get the required dynamic linking capabilities on the bare-metal side? Orthogonal Devices Tokyo, Japan www.orthogonaldevices.com On 27/06/2019 19:06, Peter Smith wrote: > On Thu, 27 Jun 2019 at 10:36, Brian Clarkson via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi Tim. >> >> Thank you for

The ELF file header isn't always covered by a segment but still affects loading. I think everything else that effects loading/dynamic linking is always covered by a PT_LOAD segment. As evidence this is basically what --strip-sections in llvm-strip and eu-strip do and they produce perfectly runnable binaries. Having a hash of the actual memory map is interesting IMO. Build IDs can't really

Hello, While linking programs against static libraries built using llvm-ar and llvm-ranlib, I see an error message: could not read symbols: Archive has no index; run ranlib to add one collect2: ld returned 1 exit status Using either /usr/bin/nm or llvm-nm (depending on the use of --emit-llvm flag to llvm-gcc), one of them is able to list the symbols in the archive file. However, the link step

Hello all, I'm implementing a watermarking feature for lld that computes a hash of loadable segments and places the result in a note section. Ongoing work can be found here: https://reviews.llvm.org/D70316 https://reviews.llvm.org/D66426 The purpose of this watermark is to enable detection of post-link modifications to the loadable segments of the binary. Such modifications may produce a

On Thu, Jan 14, 2016 at 04:47:53PM -0800, Paul E. McKenney wrote: > So you need to build a different kernel for some types of MIPS systems? Yes. We can't really do without. Classic MIPS code is not relocatable without the complexity of PIC code as used by ELF DSOs - and their performanc penalty. Plus we have a number of architecture revisions ovr the decades, big and little endian, 32

On Thu, Jan 14, 2016 at 04:47:53PM -0800, Paul E. McKenney wrote: > So you need to build a different kernel for some types of MIPS systems? Yes. We can't really do without. Classic MIPS code is not relocatable without the complexity of PIC code as used by ELF DSOs - and their performanc penalty. Plus we have a number of architecture revisions ovr the decades, big and little endian, 32

Hello. I work at Apple on our linker. We are working to improve support for llvm in our tools. A while back Devang created <llvm/LinkTimeOptimizer.h> a C++ interface which allows the linker to process llvm bitcode files along with native mach-o object files. For the next step we'd like our other tools like nm, ar, and lipo to be able to transparently process bitcode files

Hi! Is it possible to implement a byte code cache for a llvm-jit? This way the compile time occurs only once and the next time the compiled machine code can simply be loaded from disk. Of course care has to be taken with function pointers that are used as constants since they may change on the next run. -Jochen

When I build LLVM, the message LLVMHello ignored -- Loadable modules not supported on this platform is shown and the LLVM Hello pass doesn't work. I am using Windows. Is this correct? LLVM Hello pass works only on Linux? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi llvmers, As you may know, work has been progressing on the experimental WebAssembly backend in llvm. However, there is currently not a good linking story. Most the of existing linking strategies (i.e. those in the emscripten toolchain) involve bitcode linking and whole program compilation at link time. To improve this situation I've been working on adding a wasm backend for lld. My

Thanks Mark! That'd be a useful starting point. For the rest of the people here: to be a bit more specific, I am having doubts about the following: - Can later optimization passes or code generation still create machine code that takes and stores (in a register perhaps) an address of something on the stack, even if not semantically visible to the programmer? Can this somehow be detected?

Hi, We have a research LLVM-based domain-specific code generator that we want to upgrade form LLVM 4.0 to 5.0. The code generator is written as an out-of-tree loadable module for opt. Till Clang 4.0 we were compiling the front-end code (annotated C++) using -O0. The generated bitcode was further processed using opt with our module loaded. In Clang 5.0 we see that using -O0 adds the optnone

Hi; I was wondering how can I get the name of the bitcode file on which I am running the pass. I am making my pass as a loadable module. And if I run my pass like this - opt -S -loops -load /home/arnie/llvm-clang/llvm/Release+Asserts/lib/XYZ.so -xyz <b.bc> b1.bc I want to get b.bc in the pass. Thank you; -- Arnamoy Bhattacharyya Athabasca Hall 143 Department of Computing Science -

Dear community, Recently I discovered that llvm gold linker plugin (LLVMgold.so) doesn't add llvm instrinsics symbols to the linker symbol table. I do not claim that something is necessary wrong, just want to share my observations with the community. Brief summary If I create a static library with a custom version of 'exp()' math function and link it as follows: $

Hi. IIRC some time ago there was some discussion about saving the executable code produced by the JIT to a file, for loading it at the next session. This would require to stream out the executable code before externals are resolved and resolve them when the code is loaded. AFAIK, LLVM does not support this at the moment. What's the difficulty of implementing this feature, on terms of

The direct cause of this issue is that, previously lld converted common symbols to defined symbols before passing input files to LTO, and after r360841 they are passed as common symbols to LTO. Making lld to work as before is easy, as we can convert common symbols to defined symbols as before. Here is a patch to do that, and I confirmed that that restores the original behavior for the reported

Hello Rui, Thanks for your reply. I tried with the keep-section argument and that made the shared library work. Should these sections be kept around by default maybe? -- Tobias On Thu, Oct 17, 2019 at 11:06 AM Rui Ueyama <ruiu at google.com> wrote: > > One thing I noticed is that llvm-strip seemed to remove a .ARM.attributes section. Can you try --keep-section=.ARM.attributes to