similar to: [LLVMdev] What different?

hi, I try to build hello.cpp using both llvmg++ and GNU g++, the generate llvm bytecode's size is about 960K, and the size of binary code generated by g++ is only 13K. Could anyone explain the difference between the two result? BWT: I rebuild the cfrontend in RH linux9.0, but when I build the hello.cpp the llvmG++ reports warnings too, it shows: ----------------------------- [yue at RH9

hi, when i build hello.cpp, it show following conflict: ----------------------------------------------------------- [yue at RH9 Shootout-C++]$ llvmg++ hello.cpp -o hello WARNING: Type conflict between types named 'struct._Unwind_Exception'. Src='{ ulong, void (uint, \4 *) *, uint, uint }'. Dest='{ ulong, void (ubyte, \4 *) *, uint, uint }' gccld: error linking in

hi, I compile a pthread program using llvmgcc, but when i run pthread.ll, it show: ------------------ [yue at RH9 test]$ llvmgcc pthread.c -o pthread.ll [yue at RH9 test]$ ls pthread pthread.c pthread.ll pthread.ll.bc [yue at RH9 test]$ ./pthread.ll Creating thread 0 WARNING: Cannot resolve fn 'pthread_create' using a dummy noop function instead! ERROR; return code from

I try to run lli with "--load=/lib/libpthread.so", but it shows: --------------------------------------------------- [yue at RH9 test]$ ./pthread.ll Error opening '/lib/libpthread.so.0': /lib/libpthread.so.0: symbol _errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference -load request ignored. Creating thread 0 WARNING: Cannot resolve fn

Try llvmgcc pthread.c -o pthread.ll -pthread You have to link in the pthreads library, and I believe -pthread is all you need on a redhat 9 box. Kevin > -----Original Message----- > From: llvmdev-admin at cs.uiuc.edu [mailto:llvmdev-admin at cs.uiuc.edu] On > Behalf Of yue > Sent: Tuesday, December 23, 2003 11:43 PM > To: llvmdev at cs.uiuc.edu > Subject: [LLVMdev] pthread?

On Wed, 24 Dec 2003, yue wrote: > I try to run lli with "--load=/lib/libpthread.so", but it shows: > --------------------------------------------------- > [yue at RH9 test]$ ./pthread.ll > Error opening '/lib/libpthread.so.0': /lib/libpthread.so.0: symbol > _errno, version GLIBC_2.0 not defined in file libc.so.6 with link time > reference > -load request

Dear yueqiang, I tracked this down this morning, and it is a bug with our Python code that runs the tests. Essentially what is happening is that the code is finding the temporary directory it created the first time it ran the tests and believes that there are tests inside of it which it needs to run. It then gets confused and quits. This bug only shows up when the source tree and the

yue wrote: > hi, > about [LLVMdev] another question > > thanks > > yueqiang One other thing you might want to try is to put your object tree in a directory that is *not* inside of your source tree. Currently, we don't support using separate object trees that are subdirectories of the source tree. In other words: Will work: ========== SRC_ROOT=/home/yue/llvm

Hi devels, there are two issues concerning invoking optimizations: 1. this document: http://llvm.cs.uiuc.edu/docs/GettingStarted.html is very nice, it would be good though to add in a section An Example Using the LLVM Tool Chain examples on optimization step. 2. If i am not wrong there is no tool, which integrates all steps: llvmgcc->opt->llc into something like llcc (and

On Sat, 1 May 2004, [koi8-r] "Valery A.Khamenya[koi8-r] " wrote: > there are two issues concerning invoking optimizations: > > 1. > this document: > http://llvm.cs.uiuc.edu/docs/GettingStarted.html > is very nice, it would be good though to add in a section > > An Example Using the LLVM Tool Chain > > examples on optimization step. That's an

Hi Reid Spencer, > CC=/path/to/llvmgcc CXX=/path/to/llvmg++ configure > make > > and was able to reproduce the problem. Not sure what's up with that but > as Misha pointed out, llvmgcc isn't any "particular" version of 3.4, its > just 3.4ish. I also concur with him that you should file a bug and > attach the pre-processed source to it. You can get that with

hi, when i change the OBJ_ROOT and recompile the llvm, it's successful. but run following test, then the error occues: ----------------------------------------------------- [yue at RH9 obj]$ make -C ./test/Programs make: Entering directory `/home/yue/llvm/obj/test/Programs' make[1]: Entering directory `/home/yue/llvm/obj/test/Programs/SingleSource' make[2]: Entering directory

Does LLVM called the pthread directly? and what time do you plan to release Java front end? I'll try this. ----- Original Message ----- From: "Chris Lattner" <sabre at nondot.org> To: "yue" <qiangyue at ict.ac.cn> Cc: <llvmdev at cs.uiuc.edu> Sent: Wednesday, December 24, 2003 12:47 PM Subject: Re: [LLVMdev] GCC3.5 tree-ssa > On Wed, 24 Dec 2003,

Hi, New to LLVM and I want to try some sample programs and build on them. Any pointers to where I can find small projects ? Thanks.

hi, when I run "make -C ./llvm/test/Programs", it show following error: ------------------------------------------------------------------------------------------- [root at RH9 llvm]# make -C ./llvm/test/Programs make: Entering directory `/usr/local/llvm/llvm/test/Programs' make[1]: Entering directory `/usr/local/llvm/llvm/test/Programs/SingleSource' make[2]: Entering directory

Adam, I recant my previous message. I built FreeType with GCC not LLVMGCC by accident (I shoulda checked!). The thing is, FreeType's makefiles don't respect environment variables. So, I did this: CC=/path/to/llvmgcc CXX=/path/to/llvmg++ configure make and was able to reproduce the problem. Not sure what's up with that but as Misha pointed out, llvmgcc isn't any

I'm interested in getting LLVM running on OS X so I can play around with it and check it out. I downloaded the LLVM 1.2 package and compiled and installed with no errors (used config options --with-llvmgccidr and --enable-spec2000 pointing to the relevant directories). I want to look at performance of SPEC CPU2000 with LLVM vs gcc. I was able to successfully compile and run the hello

hi all, well, i have set up proper command line parameters for for C-Shootout tests to get reasonable running time for benchmarking. I have compared "gcc -O3" and "llvmgcc -Wl,-native-cbe" here goes output (which shows that llvm is already better for test with intensive function calls): time -p ./gcc_ackermann 11 user 2.36 time -p ./llvm_ackermann 11 user 1.07

On Sun, 2004-12-19 at 22:52, Adam Warner wrote: > Hi Reid Spencer, > > > CC=/path/to/llvmgcc CXX=/path/to/llvmg++ configure > > make > > > > and was able to reproduce the problem. Not sure what's up with that but > > as Misha pointed out, llvmgcc isn't any "particular" version of 3.4, its > > just 3.4ish. I also concur with him that you

why doesn't llvm transfer bytecode to RTL form? I mean the cross-platform compile in GCC. Could LLVM do that? maybe tree-ssa also create the representation with a testual format if needed. is it very difficalt? I want to know. BWT: if we port pthread library to llvm, what do we consider at first? yueqiang Chris Lattner wrote: >On Wed, 24 Dec 2003, yue wrote: > > >>what