similar to: [LLVMdev] API CHANGE: set_gcc_path removed from libLTO C binding

On Sat, Nov 29, 2008 at 9:17 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > I'm looking into the possibility of building the libLTO plugin on Linux, > and got tangled up in the build system. > > Currently, tools/Makefile only includes 'lto' when the OS equals Darwin, > while tools/lto/Makefile has an if-statement that builds libLTO as a > static library on

I'm looking into the possibility of building the libLTO plugin on Linux, and got tangled up in the build system. Currently, tools/Makefile only includes 'lto' when the OS equals Darwin, while tools/lto/Makefile has an if-statement that builds libLTO as a static library on non-Darwin systems. If I try to build libLTO as a dynamic library on Linux, it works fine, but I get an

On Nov 12, 2009, at 11:43 AM, John Criswell wrote: > Dear LLVMers, > > I'm currently working on creating an alternate libLTO.so that will run > some whole-program analysis and transforms of mine during the final > linking of an executable. The idea is for it to link all of the > bitcode > files together, run the regular LTO passes, and then run my passes. > For

Hello, Is there any CMake variable available to build LLVM libs as static libraries. I found one -DLIBCLANG_BUILD_STATIC=ON but what if I want libLTO.a instead of libLTO.dylib ? *Vivek Pandya* -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20151214/1e03efc9/attachment.html>

Hello all, I'm a research assistant at the University of Wisconsin and we're trying to come up with a general way to run our whole program analysis over programs that may use different methods to perform the build. I saw some discussion that liblto could be used for this (and safecode successfully did it) for llvm 2.6 - 3.0, but that doesn't seem to be working the same way with llvm

Dear LLVMers, I'm currently working on creating an alternate libLTO.so that will run some whole-program analysis and transforms of mine during the final linking of an executable. The idea is for it to link all of the bitcode files together, run the regular LTO passes, and then run my passes. For Linux, I should be able to get the Gold linker to load my libLTO.so instead of the standard

The path to libLTO.so in LLVMgold.so points to the build directory on my machine: % ldd /usr/local/lib/LLVMgold.so linux-vdso.so.1 (0x00007fff3d795000) /var/tmp/build_llvm_clang/Release+Asserts/lib/libLTO.so => not found libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f1703983000) ... I have configured clang with: ../llvm/configure --enable-optimized

Maurice Gittens wrote: > Hi all, > > I just svn-updated the 2.5 branch on my machine and I noticed this > warning during the build. > > *** Warning: Linking the shared library > /home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool > *** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o >

Is there a particular method one should used to build the libLTO.dylib from the llvm svn on darwin9? Unless I am confused, it seems that libLTO.dylib gets built when I do a configure and make directly in the llvm svn tree but not when I created separate llvm_objdir directory and execute configure and make within it. Thanks in advance for any clarifications. Jack

On 3/24/11 6:23 PM, Sangmin Park wrote: > Hi, > > I need advice in instrumenting programs using liblto and gold plugin. > Specifically, I added my pass in tools/lto/LTOCodeGenerator.cpp. > My pass inserts functions (myLoad and myStore) for some load and store > instructions. > The functions exist in a library file. > > I found that the approach works for the example in

Hi all, libLTO is exposing a very “stable” (in the sense of immutable) C API to be used by linkers (and binutils tools) that manipulate bitcode (like when performing LTO). I’m looking into relaxing the stability concern and design a policy for this API that would allow to deprecate and remove some the APIs exposed here. The MacOS linker (ld64) is one the users of libLTO, but there are others

Hi, Is there a way to avoid linking with the dynamic LTO library. I’m using llvm 5.0.0 on various platforms (linux, windows, macOS), this library is not required by my application and I keep having trouble with it. My project is cmake based and makes use of LLVMConfig.cmake or llvm-config output (depending on the platform - there is no LLVMConfig.cmake with the windows package). On windows the

Hi, I need advice in instrumenting programs using liblto and gold plugin. Specifically, I added my pass in tools/lto/LTOCodeGenerator.cpp. My pass inserts functions (myLoad and myStore) for some load and store instructions. The functions exist in a library file. I found that the approach works for the example in the link: http://llvm.org/docs/GoldPlugin.html $ llvm-gcc -flto a.c -c -o a.o $ ar q

2017-05-02 8:42 GMT-07:00 Duncan P. N. Exon Smith <dexonsmith at apple.com>: > +Teresa, Mehdi > > On May 2, 2017, at 08:31, James Henderson <jh7370.2008 at my.bristol.ac.uk> > wrote: > > Hi, > > We have been investigating an issue when running LTO with our proprietary > linker, which links against libLTO dynamically. The issue is that when we > pass

Hi, We have been investigating an issue when running LTO with our proprietary linker, which links against libLTO dynamically. The issue is that when we pass -time-passes via the lto_codegen_debug_options function in the LTO C API, no time information is produced during compilation. The reason for this is that time information is stored in state owned by a ManagedStatic instance, and is only

I puzzled out that the --with-pic option was required to cause the libLTO.dylib to be built. I must have done a make before directly in the lto tools subdirectory when I was building directly in the source tree. Jack

Hi John, Thank you for your advice. LIBS and LDFLAGS work for the configure script, but they gave errors in the make stage for apache and mysql. I used either of the following ones with other flags: - export LIBS="-L/home/sangmin/Dropbox/Falcon/bin/ -ldummy" - export LDFLAGS="-L/home/sangmin/Dropbox/Falcon/bin/ -ldummy" Here are the error messages: Compile error (apache):

Hi all, I just svn-updated the 2.5 branch on my machine and I noticed this warning during the build. *** Warning: Linking the shared library /home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool *** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o /home/maurice/installation/llvm/Debug/lib/LLVMMSIL.o /home/maurice/installation/llvm/Debug/lib/LLVMCBackend.o

Aaron Gray wrote: > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Aaron Gray wrote: > > Hi, > > > > I partly built LLVM on Cygwin yesterday and it was fine as far as it > > went. But after doing a svn update today I am getting the following > > warning

On Wed, Oct 21, 2009 at 10:31 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Óscar Fuentes wrote: >> >> Just received this: >> >> The Buildbot has detected a new failure of llvm-ppc-linux on llvm. >> Full details are available at: >>  http://google1.osuosl.org:8011/builders/llvm-ppc-linux/builds/3229 >> >> Buildbot URL: