similar to: [LLVMdev] crtend

I am trying to disassemble some bytecode using llvm-dis: llvm-dis -f -o llvmtest/sliceme2.cbc.ll llvmtest/sliceme2.cbc However, I am getting the following error. llvm-dis: Invalid bytecode signature: 464C457F (Vers=0, Pos=4) How do I go about figuring out what the problem is? llvmtest/sliceme2.cbc is newly compiled using the same version of llvm-gcc as llvm-dis. -- Ryan M. Lefever

Hi Ryan, On Fri, 2006-12-01 at 18:06 -0600, Ryan M. Lefever wrote: > I am trying to disassemble some bytecode using llvm-dis: > llvm-dis -f -o llvmtest/sliceme2.cbc.ll llvmtest/sliceme2.cbc > > However, I am getting the following error. > > llvm-dis: Invalid bytecode signature: 464C457F (Vers=0, Pos=4) The problem is most likely that sliceme2.cbc is *not* bytecode. Open the

I ran the following command: llvm-gcc -Iinclude -Illvmtest -Wa,-disable-inlining -Wl,-disable-inlining -c -o llvmtest/sliceme2.bc llvmtest/sliceme2.c And it responded with the following: as: unrecognized option `-disable-inlining' Does -disable-inlining not work anymore? Thanks, Ryan

Ryan M. Lefever wrote: > I am trying to use LLVM as a source to source C compiler. I use > llvm-gcc to convert file.c->file.bc. Then I use opt to run my own > compiler passes to convert file.bc->file.opt.bc. Then I use llc to > convert file.opt.bc->file.opt.c. Now, I want to use normal gcc to > compile file.opt.c into an executable. However, I'm getting the

Thank you for the help. There seem to be several things in my makefiles that are messed up as a result of switching from the gcc3.4 front end to the gcc4 frontend. Is there any documentation listing the things that have changed? Thanks, Ryan Ryan M. Lefever [http://www.ews.uiuc.edu/~lefever] On Fri, 1 Dec 2006, Reid Spencer wrote: > Hi Ryan, > > On Fri, 2006-12-01 at 18:06

I am trying to use LLVM as a source to source C compiler. I use llvm-gcc to convert file.c->file.bc. Then I use opt to run my own compiler passes to convert file.bc->file.opt.bc. Then I use llc to convert file.opt.bc->file.opt.c. Now, I want to use normal gcc to compile file.opt.c into an executable. However, I'm getting the following errors: test.opt.c:89: warning:

Hi all, I started to write an LLVM backend for custom CPU. I created XXXInstrInfo but there are some problems. I searched for it but I couldn't find anything. Can anyone help me? include "XXXInstrFormats.td" def simm16 : Operand<i32> { let DecoderMethod = "DecodeSimm16"; } def mem : Operand<i32> { let PrintMethod = "printMemOperand"; let

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

On Mon, 2006-02-27 at 20:43 -0800, Wink Saville wrote: > > Try passing "-L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend" to llvm-ld. > This didn't work for me: > llvm-ld -o t1.app t1.bc t1.a -L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend.a > > I get two warning's about library 'crtend' missing > You didn't get the instructions quite right. The option is

Reid Spencer wrote: > On Mon, 2006-02-27 at 20:43 -0800, Wink Saville wrote: > >>> Try passing "-L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend" to llvm-ld. >>> >> This didn't work for me: >> llvm-ld -o t1.app t1.bc t1.a -L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend.a >> >> I get two warning's about library 'crtend' missing

On Mar 28, 2009, at 12:56 PM, Aaron Gray wrote: > How do I get the LLVM test-suite to work I have followed the /docs/ > TestingGuide.html but cannot seem to get it to work. I have tried > many variations, but get no joy. The docmunetation does not appear > very clear. Some things that are not so obvious: The testsuite has to be checked out as a subdirectory of llvm/ projects;

Chris Lattner wrote: > On Sun, 26 Feb 2006, Wink Saville wrote: >> I then do the following in my makefile: >> >> llvm-gcc -c t1.c -o t1.bc >> llvm-gcc -c t1sub1.c -o t1sub1.bc >> llvm-gcc -c t1sub2.c -o t1sub2.bc >> llvm-ar r t1.a t1sub1.bc t1sub2.bc >> llvm-ar: creating t1.a >> llvm-ld -o t1.app t1.bc t1.a /opt/llvm-1.6/llvm-gcc/lib/libcrtend.a

Thanks for the reply. Do I check it out under src or build directory ? I am sure I had all this working fine with no problems 2 years ago. Aaron ----- Original Message ----- From: Dale Johannesen To: LLVM Developers Mailing List Sent: Saturday, March 28, 2009 8:11 PM Subject: Re: [LLVMdev] LLVM test-suite On Mar 28, 2009, at 12:56 PM, Aaron Gray wrote: How do I get the

Thank you, Reid, I tried llvm-gcc -lcrtend ary3.c -o ary3, but I get gccld: warning: Cannot find library 'crtend' gccld: warning: Cannot find library 'c' I have the libraries in my llvm directory: llvm/runtime/GCCLibraries/crtend Well, how do I link this to the LLVM runtime stuff? Before building from the source, I had copied all the .h from my old gcc 4.0 to

Thanks for the quick responses, but unfortunately still no luck: > llvm-g++ -g -O0 -c -emit-llvm test.cpp > llc -O0 test.o > g++ test.o.s > ./a.out My return address is 0x400bb2 > addr2line 0x400bb2 ??:0 Also to further implicate llc, this works: > llvm-g++ -g -O0 -S test.cpp > g++ test.s > ./a.out My return address is 0x400bf9 > addr2line 0x400bf9

On Apr 25, 2006, at 8:56 AM, John Criswell wrote: > Ryan M. Lefever wrote: >> I am trying to use LLVM as a source to source C compiler. I use >> llvm-gcc to convert file.c->file.bc. Then I use opt to run my own >> compiler passes to convert file.bc->file.opt.bc. Then I use llc >> to convert file.opt.bc->file.opt.c. Now, I want to use normal gcc

Hi, I am using LLVM to compile vsftp to native x86 ELF code. One of it's object file (sysdeputil) contains inline asm so cannot be compiled by gcc-3.4 frontend. So I decided to firstly link together the llvm objects and libcrtend and compile it to native .o file and then link it with sysdeputil.o . The Makefile is sth like this: vsftpd: $(OBJS) gccld -r -native -o vsftpd.o $(OBJS)

Try adding -lcrtend to the gcc link line. You need to link in the LLVM runtime stuff. Reid. On Sun, 2006-08-20 at 14:30 -0700, Fernando Magno Quintao Pereira wrote: > > Rebuilding llvm-gcc4 from source should work fine. Please see the > > directions in the file README.LLVM at the top level src directory. You > > can check llvm-gcc4 out from Subversion with the command: >

On Sun, 26 Feb 2006, Wink Saville wrote: > I then do the following in my makefile: > > llvm-gcc -c t1.c -o t1.bc > llvm-gcc -c t1sub1.c -o t1sub1.bc > llvm-gcc -c t1sub2.c -o t1sub2.bc > llvm-ar r t1.a t1sub1.bc t1sub2.bc > llvm-ar: creating t1.a > llvm-ld -o t1.app t1.bc t1.a /opt/llvm-1.6/llvm-gcc/lib/libcrtend.a > llvm-ld: warning: Cannot find library 'crtend'

Misha Brukman wrote: > On Sun, Feb 26, 2006 at 10:00:18PM -0800, Wink Saville wrote: > > [snip] > If you're using -c, you're telling LLVM that there are other modules you > will link into the executable. Thus, LLVM does not know whether there > will be static ctors/dtors to run or not, so there's the call to > __main() from main. > > __main() gets