similar to: [LLVMdev] To Link *.bc with *.so

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, 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, 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

On Mon, Apr 25, 2005 at 04:34:07AM -0500, Zeyu Chen wrote: > I am asking this question to see if it is possible or desirable to > build a compilation/runtime system for C/C++ that can support the > following: > > 1. allow bc to call native (in dynamically loaded *.so) You can do this today, e.g., with lli -load=native.so file.bc > 2. allow native to call bc (through JIT or

Chandler/Domagoj, On Sun, 2006-12-10 at 10:53 -0500, Chandler Carruth wrote: > Unless I'm missing something, the problem lies directly with the fact > that you are trying to do a link-stage operation with the GCC > frontend. GCC, by default, probably runs "ld" or another system > linker, which grabs the executable from binutils. This linker hasn't > been modified

I am asking this question to see if it is possible or desirable to build a compilation/runtime system for C/C++ that can support the following: 1. allow bc to call native (in dynamically loaded *.so) 2. allow native to call bc (through JIT or interpreter) 3. can compile/interpret C/C++ sources _BASED_ on type info in precompiled bc Motivation: The class files produced by the java compiler

Hi I'm trying to compile the "bh" C program from the Olden benchmark to one bc file. # compile source files into an LLVM bitcode file llvm-gcc -emit-llvm -c args.c -o args.bc -w -DTORONTO llvm-gcc -emit-llvm -c newbh.c -o newbh.bc -w -DTORONTO llvm-gcc -emit-llvm -c util.c -o util.bc -w -DTORONTO llvm-gcc -emit-llvm -c walksub.c -o walksub.bc -w -DTORONTO # To link files together

Hello, If you have one or more bytecode files with debug info, how do you generate a native executable still with debug info? I tried, for instance, this: llvm-ld -native -disable-opt -o exec file1.bc file2.bc but it doesn't seem to work. Thanks, Luís

Reid Spencer wrote: > Chandler/Domagoj, > > On Sun, 2006-12-10 at 10:53 -0500, Chandler Carruth wrote: > >>Unless I'm missing something, the problem lies directly with the fact >>that you are trying to do a link-stage operation with the GCC >>frontend. GCC, by default, probably runs "ld" or another system >>linker, which grabs the executable from

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

I have a question with llvm-gcc and llvm-gfortran. Is it possible that llvm-ld can combine different bc files compiled from C programme and Fortran Programme together? For example: Compile a c program into llvm bc file by the task: # llvm-gcc -emit-llvm test.c -c -o test.bc and then compile a fortran program into llvm bc file by the task: # llvm-gfortran -emit-llvm testf.f -c -o testf.bc And

Unless I'm missing something, the problem lies directly with the fact that you are trying to do a link-stage operation with the GCC frontend. GCC, by default, probably runs "ld" or another system linker, which grabs the executable from binutils. This linker hasn't been modified (yet) to include support for .bc files, but you're compiler is emitting byte code to the *.o files.

According to the few tests I did, .ll.gz is more compact: 1.00 LLVM bitcode (.bc) 0.80 Gzipped LLVM bitcode (.bc.gz) 4.13 LLVM assembly (.ll) 0.68 Gzipped LLVM assembly (.ll.gz) However, there's not much in it, considering that a stripped native binary is about 0.40 on the same scale. So, seeing as projects such as PNaCl want to send LLVM bitcode over the network, are there any proposed

On Tue, 14 Dec 2010 10:55:09 -0000 "Edmund Grimley-Evans" <Edmund.Grimley-Evans at arm.com> wrote: > According to the few tests I did, .ll.gz is more compact: > > 1.00 LLVM bitcode (.bc) > 0.80 Gzipped LLVM bitcode (.bc.gz) > 4.13 LLVM assembly (.ll) > 0.68 Gzipped LLVM assembly (.ll.gz) > > However, there's not much in it, considering that a

I'm trying to test a bitcode file that I created using the LLVM API. Using llvm-g++, how can I compile.a C++ file and link it against my bc file ? I try to call a single function in the bc file from the c++ main function. Envoyé de mon iPhone

Hello Alexandre, > I'm trying to test a bitcode file that I created using the LLVM API. Using llvm-g++, how can I compile.a C++ file and link it against my bc file ? I try to call a single function in the bc file from the c++ main function. You need to have a linker which supports linking of LLVM bitcode. So far this is darwin linker and gold with extra plugin. This doc might be helpful:

Hi Eric, Thanks for the reply. I am very new to llvm so could you elaborate more about you meant by 'debugging lli'? Thanks a lot! Christine On Thu, Aug 18, 2011 at 4:47 PM, Eric Christopher <echristo at apple.com>wrote: > > On Aug 18, 2011, at 4:39 PM, Christine Cheng wrote: > > > Hi, > > > > I am working with a long llvm bc code in human readable

Sanjiv Gupta wrote: > Nick Lewycky wrote: >> Sanjiv.Gupta at microchip.com wrote: >>> >>> >>> A common followup question is "but how do I link native libraries into >>> my .bc file". You don't. A .bc file is llvm ir, you can't put a native >>> binary library into a .bc (barring sticking it in as a string, etc). >>>

Nick Lewycky wrote: > Sanjiv.Gupta at microchip.com wrote: >> >> >> A common followup question is "but how do I link native libraries into >> my .bc file". You don't. A .bc file is llvm ir, you can't put a native >> binary library into a .bc (barring sticking it in as a string, etc). >> >> The build then looks like: >> >>

* *Hello, I am using llvm-2.7 to run a native(executable) on a arm processor. I have built my wxGtk sample app with llvm-gcc as frontend . I am using llvm-2.7 and llvm-gcc-4.2. I built llvm-2.7 with: ../llvm-2.7/configure --prefix=/home/install-llvm --enable-optimized --enable-assertions and llvm gcc with: ../llvm-gcc-4.2-2.7.source/configure --prefix=/home//gcc-disable-shared