similar to: [LLVMdev] Pass linking problems

Hi, > I'm attempting to use Module::getTypeByName in my pass, but when I > run the pass with opt, I get this: > > opt: symbol lookup error: > /home/mmwu/Download/32/llvm/Release/lib/ParallelSort.so: undefined > symbol: _ZNK4llvm6Module13getTypeByNameENS_9StringRefE > > The pass worked before I added the call in. What do I need to link with > the pass to

Dear Michael, The symbols that are said undefined by the compiler live in libAllocator.a. That file should be in Release/lib/, do you have it? It is possible that the compiler has linking order problems. What is the version of your gcc? You can try changing the link order of the make command by editing tools/vmkit/Makefile. Also, you should know that the GC of vmkit does not work on a

Hi, I can't seem to get VMKit to compile correctly. I'm on a 64 bit Jaunty system. I compiled llvm and llvm-gcc from the subversion source no problem, but when I try to compile VMKit I get some issue with GCAllocator: /home/mmwu/Download/llvm$ ./configure /home/mmwu/Download/llvm$ make ENABLE_OPTIMIZED=1 /home/mmwu/Download/llvm$ make ENABLE_OPTIMIZED=1 install ...

Hi, I've managed to compile it the class down to a native executable. However, the executable runs for a while then spits out: terminate called without an active exception Aborted and dies. The program never gets to the normal output. Here is a stack trace from gdb: #0 0xf3f6baa6 in raise () from /lib/libc.so.6 #1 0xf3f6d3a8 in abort () from /lib/libc.so.6 #2 0xf41918f8 in

Hi Michael, On Tue, Dec 8, 2009 at 6:26 PM, Michael Wu <mmwu at princeton.edu> wrote: > Hi, > > Thanks a lot for the help! I am getting some errors though: > > I am on a 32 bit chroot on a x86_64 system. Thus llc guesses the wrong > architecture from the module bitcode and spits out x86_64 assembly. I fixed > this by adding "-march=x86" to the llc options

Hi, Thanks a lot for the help! I am getting some errors though: I am on a 32 bit chroot on a x86_64 system. Thus llc guesses the wrong architecture from the module bitcode and spits out x86_64 assembly. I fixed this by adding "-march=x86" to the llc options in llcj. gcc doesn't know what -lgc is. I'm guessing it is the garbage collection library. How can I get it or

Hi Michael, Currently, you can run vmjc created .bc files by statically linking them with all the .o needed files. For that, you can use the llcj tool, which works more or less like GCC's gcj tool. Note that you also need to create the libvmjc.so file, which contains the standard library in native form. Do a make in the tools/vmjc/libvmjc directory. Once this is done, update the

Hi: I'm building a small tool on top of LLVM Core Library. ``` LLVMContext context; SMDiagnostic diag; Module *M = parseIRFile(InputIR, diag, context).get(); if (M == nullptr) { diag.print("LLVM", errs()); exit(-1); } assert(M->isMaterialized() && "Module not materialized!"); PointerType *ArrayPtrTy =

Hi, What do I need to link with vmjc created .bc files to actually run the .bc file? I tried running with lli but only got: LLVM ERROR: Program used external function 'StartJnjvmWithoutJIT' which could not be resolved! Thanks, Michael

Several people on this list have reported issues with the linker regarding a named StructType instance with the same name in two different modules being resolved into two StructTypes with different names due to StructType:: setName(…) collision behavior. Looking at BitcodeReader::ParseTypeTableBody(…), I don't see use of LLVMContextImpl::NamedStructTypes or of Module::getTypeByName(…). Nor do

Hello Anton, While we have been discussing this, my partner discovered the source of where the sj/lj stuff is coming from. Does this mean that the LLVM libraries we're using are broken? Type.cpp ..\..\..\..\llvm\lib/libLLVMCore.a(Type.cpp.obj):Type.cpp.text+0x722): undefined reference to `__gxx_personality_sj0' ..\..\..\..\llvm\lib/libLLVMCore.a(Type.cpp.obj):Type.cpp.text+0x750):

On Mon, Jul 25, 2011 at 10:50 AM, Garrison Venn <gvenn.cfe.dev at gmail.com> wrote: > Several people on this list have reported issues with the linker regarding a > named StructType instance with the same name in two different modules > being resolved into two StructTypes with different names due to StructType:: > setName(…) collision behavior. Looking at

Hello Anton, We used the release tarball. Oh! I forgot to mention it's the version 2.5 stable release that we've been developing with. Thanks, --Sam ----- Original Message ---- > From: Anton Korobeynikov <anton at korobeynikov.info> > To: Samuel Crow <samuraileumas at yahoo.com> > Cc: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Sent: Fri,

Hello, Samuel > We used the release tarball.  Oh!  I forgot to mention it's the version 2.5 stable release that we've been developing with. Hrm, something is broken there.... Try to compile your code with -fno-exceptions then -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

On Jul 25, 2011, at 10:50 AM, Garrison Venn wrote: > Several people on this list have reported issues with the linker regarding a > named StructType instance with the same name in two different modules > being resolved into two StructTypes with different names due to StructType:: > setName(…) collision behavior. Looking at BitcodeReader::ParseTypeTableBody(…), > I don't see

Hello. I have an .bc, which defines @foo(%type* arg1, %type* arg2, %type* arg3). Firstly, i do this: runtimeModule = getLazyIRFileModule("runtime.bc", smd, llctx); then this: fooFunction = runtimeModule->getFunction("foo"); myType = runtimeModule->getTypeByName("type"); After that, i'm creating another module: myModule = new Module("My

On Thu, Sep 22, 2011 at 3:46 PM, sarath chandra <sarathcse19 at gmail.com>wrote: > Hi James, > > First i converted the void * to int* and then did FPToSI...then did SHL...( > because CreateShl only accepts integers... i pointer casted it to int64 type > first)... Below is the code snippet.... > > > lhs = mBuilder.CreateStructGEP(firstArg, 0); > lhs =

Hello all, Does anyone have any inside why I can't get the below simple C API test to link? This is on a 32-bit Gentoo Linux system and LLVM TOT which was compiled with enable-optimized, gcc is 4.3.2. 15:26|melis at juggle2:~/c/llvmpy> cat t.c #include "llvm-c/Core.h" int main() { LLVMContextRef ctx; ctx = LLVMContextCreate(); return 0; } 15:29|melis at

Hi Sarath, It would have really helped if you had removed the commented out code and inlined the calls to your homemade helper functions before sending it... You are doing this, in LLVM IR: %0 = getelementptr %Value* %firstArg, i32 0 ; i8** %1 = load i8** %0 ; i8* %2 = bitcast i8* %1 to i64* %3 = getelementptr %Value* %secondArg, i32 0 ; i8** %4 = load i8** %3; i8* %5 = bitcast i8* %4 to i64*

Hello all, I am trying to build the kaleidoscope sample code on Mac os (10.6). What I have done to get llvm libraries : 1) Downloaded llvm-2.6 source code 2) ./configure 3)make 4) make intall Then I tried to build kaleidoscope as described in the tutorial: g++ -g -O3 toy.cpp `llvm-config --cppflags --ldflags --libs core` -o toy I get typical link time errors (undefined symbols: ...) as if the