similar to: [LLVMdev] llc -load....

Thank you... I am preparing to build a simple C compiler for our new architecture. According to your suggestion. I try to dynamically load my backend. But I got the error message : llc : target 'Your_Arch' does not support static compilation! could you tell me where is this problem? On Mon, 24 Jan 2005 22:53:15 -0600 (CST), Chris Lattner <sabre at nondot.org> wrote: > On

On Tue, 25 Jan 2005, s88 wrote: > hello... > I have finish my backend. But I dont know how to install my backend... > llc -load=???Load what?? > Can anyone teach me? > 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

On Tue, 25 Jan 2005, s88 wrote: > Thank you... > I am preparing to build a simple C compiler for our new architecture. > According to your suggestion. I try to dynamically load my backend. > But I got the error message : > llc : target 'Your_Arch' does not support static compilation! > could you tell me where is this problem? A useful tool in llvm is named

Hi I have just written an pass which does some simple ASAP scheduling. First i registered it as optimization 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

Hi all, I'm trying to use the PPL (Parma Polyhedra Library, bugseng.com/products/ppl) in one of my LLVM passes getting the error: > Error opening > '/home/jorge/SvnReps/Systems/llvm/build/Debug+Asserts/lib/MyAnalysis.so': > /home/jorge/SvnReps/Systems/llvm/build/Debug+Asserts/lib/MyAnalysis.so: > undefined symbol: _ZNK23Parma_Polyhedra_Library13PIP_Tree_Node2OKEv >

Hi Jorge, > I'm trying to use the PPL (Parma Polyhedra Library, > bugseng.com/products/ppl) in one of my LLVM passes getting the error: > >> Error opening >> '/home/jorge/SvnReps/Systems/llvm/build/Debug+Asserts/lib/MyAnalysis.so': >> /home/jorge/SvnReps/Systems/llvm/build/Debug+Asserts/lib/MyAnalysis.so: >> undefined symbol:

On Tuesday, November 15, 2011 at 10:11:25 (+0100), Duncan Sands wrote: >> Hi Jorge, >> >> > I'm trying to use the PPL (Parma Polyhedra Library, >> > bugseng.com/products/ppl) in one of my LLVM passes getting the error: >> > >> >> Error opening >> >> '/home/jorge/SvnReps/Systems/llvm/build/Debug+Asserts/lib/MyAnalysis.so':

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 SHARED_LIBRARY=1 you get a regular shared library

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 generated. But I am confused as to how to generate the .so library file from here. I am kinda new to compilers and hence the question I know is basic , but couldnt figure the answer out myself. Thanks a lot for your help. Regards -- -- Aparna Kotha Research

Thanks a lot. A see the shared library in linux version. I initially tried doing this in 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

Howdy everybody. I'm trying hard to load my backend. But I got problems. I took the target SparcV8 for lab. 1. mark all of the code in the bool SparcV8TargetMachine::addPassesToEmitAssembly(PassManager &PM,std::ostream &Out) and make it return false.( Of course I mark the // Output assembly language. PM.add(createSparcV8CodePrinterPass(Out, *this));) 2. generate the

Hi Takumi, > Any feedbacks are welcome. > Have fun! This seems to be pretty useful addition to LLVM on windows! And it seems the only painless way to make plugins working, yay! For me the patch looks pretty good. One minor thing: could you please rename SharedDir => SharedLibDir Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg

Good summer, all! This patch enables ENABLE_SHARED=1 to build DLL based LLVM toolchain. I have checked this on Cygwin-1.5, Cygwin-1.7, mingw(msysgit) and mingw-cross-fedora12. I can separate this patch into some parts; cleanups, adding definitions and adding rules. Any feedbacks are welcome. Have fun! ...Takumi * Pros - reduction of linking time of toolchain. - capability of -load

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 >

Hi!! It's me again. I guess that there is a problem in the Makefile of my source code. But I don't know where. Could you please verify it? The Makefile is written like this: # Makefile for Genetic Algorithm Pass CXXFLAGS = -Wall -I/iss/fpga3/nicole/galib247/ LDFLAGS= -L/iss/fpga3/nicole/galib247/ga/ -lga -Wl,-E # Path to top level of LLVM heirarchy LEVEL=../../../ # Name of the

I believe because cygwin behaves like windows (it is just a posix layer over window) it doesn't have dynamic linking hence only static libraries have been built. On 13 Apr 2009, at 23:16, aparna kotha wrote: > Thanks a lot. > > A see the shared library in linux version. I initially tried doing > this in cygwin where I dont see the shared library being built. Do > u

On May 8, 2009, at 11:49 AM, Chris Lattner wrote: > On May 7, 2009, at 6:24 PM, Mike Stump wrote: >> I'm toying with building with -mdynamic-no-pic, but for this to work, >> the shared library bits in llvm can't be built with that flag. > > Hi Mike, > > If you're doing this for Clang's benefit, No, not really, I'm doing it for the general benefit of

Hello, llvmers. Could someone explain me a little about the opt tool? I am having problems to load a MachineFunctionPass using opt. I have this pass: #include "llvm/Pass.h" #include "llvm/Function.h" #include "llvm/CodeGen/MachineFunctionPass.h" #include <iostream> using namespace llvm; namespace { struct MacFoo : public MachineFunctionPass { virtual

Hello! Is there any reason why after "./configure; make" all LLVM libraries are .a files, and not .so files? The problem with .a files is that if I make a plugin, say code generator, it should link in pretty large LLVM libraries. If libraries were shared, this would not be required. Alternatively, tools that load plugins can probably mark all symbols as dynamically exported, by using

On May 7, 2009, at 6:24 PM, Mike Stump wrote: > I'm toying with building with -mdynamic-no-pic, but for this to work, > the shared library bits in llvm can't be built with that flag. Hi Mike, If you're doing this for Clang's benefit, I think the best thing to do is to compile LLVM PIC (the default) and then build the clang front- end pieces with -mdynamic-no-pic. Does