search for: llvmlib

...out whether a certain gcc compiler will mis-compile? 2. I ran into exactly the problem you pointed out. (Thank you) The Makefile needs some update (after careful comparison between the tutorial Makefile and the makefile used for lib/Transformation/Hello), by commenting out the following line: #LLVMLIBS = LLVMCore.a LLVMSystem.a LLVMSupport.a I guess the tutorial needs some update, as with release 2.5 things might have changed a bit. Thanks for the reply Chuck Shuguang Feng wrote: > Hey Chuck, > > I'm afraid I can't reproduce your error but...a problem you may run > int...

...ke the shared library become a loadable module so the tools can # dlopen/dlsym on the resulting library. LOADABLE_MODULE = 1 # Tell the build system which LLVM libraries your pass needs. You'll probably # need at least LLVMSystem.a, LLVMSupport.a, LLVMCore.a but possibly several # others too. LLVMLIBS = LLVMCore.a LLVMSupport.a LLVMSystem.a # Include the makefile implementation stuff include $(LEVEL)/Makefile.common -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090717/28c1bd3c/attachment.html>

...llvm::cerr << "First: " << F.getName() << "\n"; return false; } }; char First::ID = 0; RegisterPass<First> X("first", "First world pass"); } and the Makefile: LEVEL = ../../.. LIBRARYNAME = First LOADABLE_MODULE = 1 LLVMLIBS = LLVMCore.a LLVMSupport.a LLVMSystem.a include $(LEVEL)/Makefile.common Thanks in advance. Lu

...y run into later is that opt will complain with opt: llvm/lib/VMCore/Pass.cpp:149: void<unnamed>::PassRegistrar::RegisterPass(const llvm::PassInfo&): Assertion `Inserted && "Pass registered multiple times!"' failed. Aborted I "fixed" this by replacing the LLVMLIBS line in the Makefile with LINK_COMPONENTS according to this tutorial http://llvm.org/docs/MakefileGuide.html#LoadableModules and was able to build/run my pass properly. -shu On Jul 17, 11:48 am, Chuck Zhao <cz... at eecg.toronto.edu> wrote: > While learning to write LLVM passes and foll...

...r file which include LLVM headers. --ldflags Linker flags. --libs <COMPONENT>... Libraries needed to link against LLVM components. Right now, the only useful component is the JIT: jit LLVM JIT compiler. I get this set of dependencies using: LLVMLIBS := JIT SUB_JITOBJS=$(LLVMUsedLibs) It's very easy to dump a Makefile variable to the llvm-config script, so the only obstacle to adding more configurations is modularizing the code which processes LLVMLIBS. > I would be quite happy to have a hard-coded list of library > depend...

...en't had any problems > 2. I ran into exactly the problem you pointed out. (Thank you) > The Makefile needs some update (after careful comparison between the > tutorial Makefile and the makefile used for lib/Transformation/Hello), by > commenting out the following line: > > #LLVMLIBS = LLVMCore.a LLVMSystem.a LLVMSupport.a > > I guess the tutorial needs some update, as with release 2.5 things might > have changed a bit. Yea, I commented out LLVMLIBS at first as well before I came across the documentation at http://llvm.org/docs/MakefileGuide.html#LoadableModules . I...

It turned out to be the problem of this line in Makefile LLVMLIBS = LLVMCore.a LLVMSupport.a LLVMSystem.a The error is gone when I remove the above line. However, the pass output only contains one line of the main function. First: main It does not have puts and __main as shown in this page: http://llvm.org/docs/WritingAnLLVMPass.html#running So I guess the...

...f "gmake", could it be the problem? Or maybe I just type (copy) something wrong? Could someone take a look of my files and point my errors out? Thanks in advance, Juan Carlos ***************** *** Makefile *** ***************** LEVEL = ../../.. LIBRARYNAME = MyPass LOADABLE_MODULE = 1 LLVMLIBS = LLVMCore.a LLVMSupport.a LLVMSystem.a include $(LEVEL)/Makefile.common ********************** *** MyPass.cpp *** ********************** #include "llvm/Pass.h" #include "llvm/Function.h" #include "llvm/Support/raw_ostream.h" using namespace llvm; namespace { struc...

...ms but I have a link problem and don't know how to solve it: The target machine uses 'FindUsedTypes' pass and when I try to use my target machine in the tool I got "Undefined symbols: "llvm::FindUsedTypes ... ld: symbol(s) not found" I tried following link options: LLVMLIBS = LLVMAnalysis.a LINK_COMPONENTS = analysis LINK_COMPONENTS = all But nothing solved my problem (in fact the last made some other problems with code I never touched). I would be very appreciated for any idea. Thanks a lot Nico PS: output from "make VERBOSE=1" llvm[2]: Linking Relea...

Dear Nico, I believe you need to add LLVMipa to the list of libraries to link into your tool. FindUsedTypes::ID is defined in lib/Analysis/IPA. I think it would be LLVMipa.a if you added it to LLVMLIBS and ipa if you added it to LINK_COMPONENTS. -- John T. Nico wrote: > Hi, > > I tried to implement an 'llc'-like tool in my project to manage > different passes and a target machine. > > I use given llvm project structure to avoid problems but I have a link > pro...

...ype (copy) something wrong? Could > someone take a look of my files and point my errors out? > > Thanks in advance, > > Juan Carlos > > ***************** > *** Makefile *** > ***************** > LEVEL = ../../.. > LIBRARYNAME = MyPass > LOADABLE_MODULE = 1 > LLVMLIBS = LLVMCore.a LLVMSupport.a LLVMSystem.a > include $(LEVEL)/Makefile.common > > ********************** > *** MyPass.cpp *** > ********************** > #include "llvm/Pass.h" > #include "llvm/Function.h" > #include "llvm/Support/raw_ostream.h" &g...

I am using llvm 1.8 and have patched ltdl.c and ltdl.h to the latest version. My Makefile has LLVMLIBS = LLVMCore.a LLVMSupport.a LLVMSystem.a included. > Try using 'nm -m' on the 'opt' executable itself. Using plain nm on my > local one yields: > 00121a4e T > __ZN4llvm12FunctionPass16addToPassManagerEPNS_20FunctionPassManagerTERNS_13AnalysisUsageE > > and nm -m...

.../lib/libLLVMHello.so': /opt/lib/libLLVMHello.so: Undefined symbol "_ZNK4llvm4Pass5printERNS_11raw_ostreamEPKNS_6ModuleE" -load request ignored. OVERVIEW: llvm .bc -> .bc modular optimizer and analysis printer [...] I edited the lib/Transforms/Hello/Makefile with various forms of LLVMLIBS, USEDLIBS, and LINK_COMPONENTS. Basically, I needed to include "LLVMCore.a LLVMSupport.a LLVMSystem.a" in order to get rid of all 3 unresolved symbols. However, when I tried to load that library with opt, I got the dreaded "pass loaded multiple times" assert. This is the Relea...

...ry become a loadable module so the tools can # dlopen/dlsym on the resulting library. # LOADABLE_MODULE = 1 # USEDLIBS=ga.a # Tell the build system which LLVM libraries your pass needs. You'll probably # need at least LLVMSystem.a, LLVMSupport.a, LLVMCore.a but possibly several # others too. # LLVMLIBS = LLVMCore.a LLVMSupport.a LLVMSystem.a SHARED_LIBRARY = 1 # ARCHIVE_LIBRARY = 1 DONT_BUILD_RELINKED = 1 # KEEP_SYMBOLS = 1 # LINK_LIBS_IN_SHARED = 1 # Include the makefile implementation stuff include $(LEVEL)/Makefile.common Thanks for your help!! I'm waiting for your answer. cheers, Ni...

...ystem compiler (which identifies itself as "Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)“. Would compiling the LLVM tree with another compiler, e.g., a recent GCC, make any difference? I tried various combinations of linking my passes with the related libraries via USEDLIBS, LLVMLIBS and LINK_COMPONENTS with no success. The outcome is either that opt does not load the module at all because of duplicated symbols, or that my custom passes don’t register properly at runtime (e.g., they’re not visible in „opt --help“) Cheers, Julian

On Wed, 15 Mar 2006, Eric Kidd wrote: > On Mar 14, 2006, at 2:22 PM, Chris Lattner wrote: >>> Gnome (and many other Unix projects with massively ugly dependencies) can >>> be linked trivially using a "foo-config" script. If LLVM had something >>> similar, it might save new LLVM developers several hours of digging >>> through manuals and

...MExmplDir:= $(LLVM_OBJ_ROOT)/$(BuildMode)/examples #-------------------------------------------------------------------- +# Locations of shared libraries +#-------------------------------------------------------------------- + +SharedPrefix := lib +SharedDir := $(LibDir) +LLVMSharedDir := $(LLVMLibDir) + +# Win32.DLL prefers to be located on the "PATH" of binaries. +ifeq ($(HOST_OS), $(filter $(HOST_OS), Cygwin MingW)) + SharedPrefix := + SharedDir := $(ToolDir) + LLVMSharedDir := $(LLVMToolDir) +endif + +ifeq ($(HOST_OS),Cygwin) + SharedPrefix := cyg +endif + +#----------...

...ind regards, Nico On Jan 4, 2009, at 4:07 PM, John Criswell wrote: > Dear Nico, > > I believe you need to add LLVMipa to the list of libraries to link > into > your tool. FindUsedTypes::ID is defined in lib/Analysis/IPA. > > I think it would be LLVMipa.a if you added it to LLVMLIBS and ipa if > you > added it to LINK_COMPONENTS. > > -- John T. > > Nico wrote: >> Hi, >> >> I tried to implement an 'llc'-like tool in my project to manage >> different passes and a target machine. >> >> I use given llvm project struc...

On Mar 14, 2006, at 2:22 PM, Chris Lattner wrote: >> Gnome (and many other Unix projects with massively ugly >> dependencies) can be linked trivially using a "foo-config" script. >> If LLVM had something similar, it might save new LLVM developers >> several hours of digging through manuals and Makefiles. > > This would be very very cool to have. OK!

I am just getting started with llvm. Here's code I am trying to compile: #include <stdio.h>#include "llvm/IR/LLVMContext.h"#include "llvm/IR/Module.h"#include "llvm/IR/IRBuilder.h" int main(){ llvm::LLVMContext& context = llvm::getGlobalContext(); llvm::Module* module = new llvm::Module("top", context); llvm::IRBuilder<>