search for: loadable_modul

Hi everyone, I am wondering if there is any variable in LLVM's cmake configuration which is equivalent to LOADABLE_MODULE in LLVM's Makefile configuration. I would like to build some loadable modules for opt and I could successfully do that with Makefiles but not with CMakeLists.txt files. Thanks, Sean -- Sean Lee PhD Student Programming Language and Systems Research Group School of Computer Science and Engin...

Michael, I've implemented a LOADABLE_MODULE feature in the makefiles: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050110/023147.html The approach taken is almost what you described below. However, I want to retain the distinction between a "regular" shared library and one that can be dlopened. So, if you specify...

...; -load request ignored. Let me explain how I get to this point. To make simpler my explanation I took the "Hello World" pass provided in the directory llvm/lib/Transforms/Hello/Hello.cpp. I compiled Hello.cpp using the Makefile: > LEVEL=../../../.. > LIBRARYNAME=MyAnalysis > LOADABLE_MODULE=1 > SHARED_LIBRARY=1 > include $(LEVEL)/Makefile.common and then: clang test.c -c -emit-llvm -o test.bc opt -load /home/jorge/SvnReps/Systems/llvm/build/Debug+Asserts/lib/MyAnalysis.so -hello -stats test.bc > Hello: modulo > ===------------------------------------------------------...

...linux-gnu/libgcc_s.so.1 (0xb778d000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb7611000) /lib/ld-linux.so.2 (0xb78cf000) libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb75e7000) So I guess, my problem is in LD.Flags ? >> LEVEL=../../../.. >> LIBRARYNAME=MyAnalysis >> LOADABLE_MODULE=1 >> SHARED_LIBRARY=1 >> include $(LEVEL)/Makefile.common >> >> # These two lines are new: >> CXX.Flags += -I/home/jorge/include -fexceptions -Wno-variadic-macros >> LD.Flags += -L/home/jorge/lib -lppl -lgmp >> Ciao, Duncan. >> >> > &g...

...n how I get to this point. > > To make simpler my explanation I took the "Hello World" pass provided > in the directory llvm/lib/Transforms/Hello/Hello.cpp. > > I compiled Hello.cpp using the Makefile: > >> LEVEL=../../../.. >> LIBRARYNAME=MyAnalysis >> LOADABLE_MODULE=1 >> SHARED_LIBRARY=1 >> include $(LEVEL)/Makefile.common > > and then: > > clang test.c -c -emit-llvm -o test.bc > opt -load /home/jorge/SvnReps/Systems/llvm/build/Debug+Asserts/lib/MyAnalysis.so -hello -stats test.bc > >> Hello: modulo >> ===------------...

Yep, it sounds like a good solution, and it works for me - thanks! -mike On Mon, 10 Jan 2005 20:40:34 -0800, Reid Spencer <reid at x10sys.com> wrote: > Michael, > > I've implemented a LOADABLE_MODULE feature in the makefiles: > > http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050110/023147.html > > The approach taken is almost what you described below. However, I want > to retain the distinction between a "regular" shared library and one > that can b...

...b ├── basic.cpp ├── basic.h └── Makefile The problem is that basic.cpp will never be compiled into the loadable module which mypass.c symbols lies in. And LLVMLIBS USEDLIBS doesn't work either. Here is mypass/Makefile LEVEL = ../../.. DIRS = sub LIBRARYNAME = mypass LOADABLE_MODULE = 1 include $(LEVEL)/Makefile.common And mypass/sub/Makefile LEVEL = ../../../.. # LIBRARYNAME = test_sub # ARCHIVE_LIBRARY = 1 # LOADABLE_MODULE = 1 include $(LEVEL)/Makefile.common When mypss/sub/Makefile uses LOADABLE_MODULE = 1 with another library name(test_sub), and by add...

...in the method PopulateModulePassManager() so I can add my pass to standard passes. It all works if I add all my files in the lib/Transforms/IPO directory. But I want to keep them away in the lib/Transforms/Obfuscation directory. This is my Makefile: LEVEL = ../../.. LIBRARYNAME = LLVMobfuscation LOADABLE_MODULE = 1 BUILD_ARCHIVE = 1 include $(LEVEL)/Makefile.common My CMakeListes.txt add_llvm_library(LLVMobfuscation Cgf.cpp CgfFunction.cpp Flattening.cpp ) add_dependencies(LLVMobfuscation intrinsics_gen) and my LLVMBuild.txt [component_0] type = Library name = Obfuscation parent = Transform...

...pass because it so nice documented and speeds up the compilation and testing times dramaticly :-). Then i just registered this part as an analysis part which should be used in a modified cbackend. All seems to work fine, exept that llc fails to link. I tried removing the SHARED_LIBRARY = 1 and LOADABLE_MODULE= 1 options from the Makefile since it should be included by default in my build. Then i tried to add the .a file to the llc makefile. But it didn't help either... :-( Any hints what's missing? Btw. there was a way to make the makefile run more verbose. It was documented somewhere but...

...f endif endif endif @@ -960,6 +976,13 @@ LLVMUsedLibs := $(patsubst %.a.o, lib%.a, $(addsuffix .o, $(LLVMLIBS))) LLVMLibsPaths := $(addprefix $(LLVMLibDir)/,$(LLVMUsedLibs)) endif +# Win32.DLL may refer to other components. +ifeq ($(HOST_OS), $(filter $(HOST_OS), Cygwin MingW)) + ifdef LOADABLE_MODULE + LINK_COMPONENTS := all + endif +endif + ifndef IS_CLEANING_TARGET ifdef LINK_COMPONENTS @@ -972,8 +995,13 @@ $(LLVM_CONFIG): $(ToolDir)/$(strip $(TOOLNAME))$(EXEEXT): $(LLVM_CONFIG) ifeq ($(ENABLE_SHARED), 1) +# We can take the "auto-import" feature to get rid of using dlli...

When I tried this a while back, the .so file wasn't being built on Mac OS X. Now it looks like it is. I got dynamic loading to work following the instructions in http://llvm.cs.uiuc.edu/docs/ WritingAnLLVMPass.html. However, there was a typo in the instructions (it should say LOADABLE_MODULE = 1), and I fixed that and committed it. I also fixed the sample/lib/sample Makefile to conform to these instructions. So problem solved, thanks. Rob On Jan 6, 2006, at 3:29 PM, Reid Spencer wrote: > The answer lies in the lib/System/ltdl.c which is the dynamic loader > used by LLVM...

...t; command instead of "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; name...

...cygwin where I dont see the shared library being built. Do u think it could have been cygwin that is the problem? Aparna On Mon, Apr 13, 2009 at 5:16 PM, Milos Puzovic <milos.puzovic at gmail.com>wrote: > In order to generate shared libraries you need to have SHARED_LIBRARY > and LOADABLE_MODULE defined in the Makefile. See here for more > details: http://llvm.org/docs/MakefileGuide.html#libraries > > On 13 Apr 2009, at 20:46, aparna kotha wrote: > > > I am trying to run the LLVM hello world pass. I observe that in the > > OUPUT_DIR/lib the LLVMHello.a and LLVMHell...

...w what the exact problem is? It would be best to fix the > Makefile instead of moving it. And sense it is a transformation, the > build system is broken if you _have_ to move it. I am sorry, I don't understand what *the exact problem" is. I can describe facts; - Hello is the only LOADABLE_MODULE under lib/ - Other plugin, eg. tools/bugpoint-passes, can be built. ...Takumi

Hello all, Is it well known that building LLVM with --enable-optimized causes RegisterPass calls to be removed from dynamically loadable libraries (i.e., those built with LOADABLE_MODULE=1)? For example, here's what happens to the Hello pass (ToT on Darwin, both with and without --enable-optimized): $ pwd /Users/ransford/llvm/lib/Transforms/Hello $ nm -j Release+Asserts/Hello.o | c++filt -p | grep llvm::RegisterPass $ nm -j Debug+Asserts/Hello.o | c++filt -p | grep llvm::Reg...

...kefile its not working properly. My makefile is like this : # Makefile for hello pass # Path to top level of LLVM hierarchyLEVEL = ../../.. # Name of the library to buildLIBRARYNAME = Hello # Make the shared library become a loadable module so the tools can# dlopen/dlsym on the resulting library.LOADABLE_MODULE = 1 # Include the makefile implementation stuffinclude $(LEVEL)/Makefile.common Its giving an error like there is nothing to do with LOOPPASS.cpp or NO RULES DEFINED FOR ALL. then how should i proceed. or if u can provide me MAKEFILE for LOOPPASS so that i can crate .so file successfully. ---...

..._FD_LEAKS [ ] 5. LOW_MEMORY [*] 6. MALLOC_DEBUG [ ] 7. RADIO_RELAX [ ] 8. STATIC_BUILD [ ] 9. IAX_OLD_FIND [*] 10. LOADABLE_MODULES Do this options make asterisk consume much more CPU? My feeling is that asterisk is consuming an average of 30% more CPU than before. I'm doing this because the last upgrade to 1.4.23.1 was no good for me in terms of overall stability, so if this time it core dumps again or something I c...

hello... I have finish my backend. But I dont know how to install my backend... llc -load=???Load what?? Can anyone teach me? thanx.

...> thanx. There are two ways to do this. You can either link the backend directly into llc (like the X86 or PowerPC backends, see tools/llc/Makefile), or you can dynamically load the backend. To dynamically load the back end, add these two lines to your target makefile: SHARED_LIBRARY = 1 LOADABLE_MODULE = 1 This should build a DSO for your target (which will end with .so if you're on most unixy platforms). You can load this with: llc --load ~/llvm/Debug/lib/yourlibrary.so -march=yourarch in.bc -o out.s BTW, what architecture are you working with? -Chris -- http://nondot.org/sabre/...

In order to generate shared libraries you need to have SHARED_LIBRARY and LOADABLE_MODULE defined in the Makefile. See here for more details: http://llvm.org/docs/MakefileGuide.html#libraries On 13 Apr 2009, at 20:46, aparna kotha wrote: > I am trying to run the LLVM hello world pass. I observe that in the > OUPUT_DIR/lib the LLVMHello.a and LLVMHello.la libraries are &gt...