similar to: [LLVMdev] Compiler Driver Requrements & Design (Comments Solicited!)

On Wed, 28 Jul 2004, Reid Spencer wrote: > 2. MODE OF OPERATION > ==================== > The driver will simply read its command line arguments, read its > configuration data, and invoke the compilation, linking, and > optimization tools necessary to complete the user's request. Its basic I'm not sure that I agree with this. Compilers need to be extremely predictable and

On Wed, 2004-07-28 at 11:26, Chris Lattner wrote: > On Wed, 28 Jul 2004, Reid Spencer wrote: > > 2. MODE OF OPERATION > > ==================== > > The driver will simply read its command line arguments, read its > > configuration data, and invoke the compilation, linking, and > > optimization tools necessary to complete the user's request. Its basic > >

I just had a chance to read some of follow-up comments on Reid's initial document. I agree with Chris's discussion below of what is needed for users to get IPO/lifelong opt'n via LLVM without extensive changes to Makefiles, and about what .o files should contain. This is in perfect agreement with what I just said about how users should view LLVM. --Vikram

On Mon, 2 Aug 2004, Reid Spencer wrote: > I have a very simple XML document type that I use for configuring XPS > systems. There's only four elements and it follows much the same kind of > grouped name/value pairs that Chris is suggesting. Chris' example would > be like: > <configuration name="llvm"> > <group name=".c"> > <item

> For example: > $ llvmgcc ackerman.c -o ackerman -Wl,-native-cbe BTW, Chris, what should be then an analogy of "gcc -O3 -S foo.c" in LLVM framework? The invocation of $ llvmgcc -S ackerman.c -o ackerman -Wl,-native-cbe does not produce native assebler output as one might expect. -- Valery

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

Folks, As of the writing of this note, the llvmc tool is enabled for build on the CVS head. I'm encouraging you to try it out, provide some feedback, and help with the issues below. llvmc is now able to correctly link a pure bytecode version of any Stacker program. This includes translation with stkrc, optimization with opt and linking with llvm-link. It is also able to find Stacker's

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

Valery A.Khamenya wrote: >>For example: >>$ llvmgcc ackerman.c -o ackerman -Wl,-native-cbe > > > BTW, Chris, what should be then an analogy > of "gcc -O3 -S foo.c" in LLVM framework? > > The invocation of > > $ llvmgcc -S ackerman.c -o ackerman -Wl,-native-cbe > > does not produce native assebler output as one might expect.

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

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

gccld: Cannot find linker input file 'crtend.o I have set the LLVM_LIB_SEARCH_PATH ls -l $LLVM_LIB_SEARCH_PATH total 104 -rw-r--r-- 1 muj20 muj20 12788 Dec 7 17:05 crtend.o -rw-r--r-- 1 muj20 muj20 1984 Dec 7 17:05 libc.bc -rw-r--r-- 1 muj20 muj20 120 Dec 7 17:05 libcurses.bc

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

Hello, I've been able to get J3 working with the single and multimap garbage collectors but have hit several snags with Boehm and MMTk. For MMTk I get here: Buildfile: /cs/student/kyleklein/vmkit/mmtk/java/build.xml main: [mkdir] Created dir: /cs/student/kyleklein/vmkit/mmtk/java/classes [javac] Compiling 373 source files to /cs/student/kyleklein/vmkit/mmtk/java/classes

Some additional responses (this covers multiple previous messages): > As part of my work on bug 353: Create Front End Framework And Compiler > Driver (http://llvm.cs.uiuc.edu/PR353), I'm starting a discussion on > the > design and requirements of the compiler driver. Thanks very much for taking the lead on this, Reid. I think this will prove to be a valuable thing and, as you

Hi! I want to know if it is possible to link llvm object files with native static/shared libraries. I mean: without using the provided c/c++ frontend to compile first the sources of the libraries to llvm and then -everything being llvm- linking. For example, I would like to compile XLanguage to llvm and then link the resulting object against libXRuntime.so. If this can be done, could you give me a

hi, when build test echo.cpp using "llvmg++ echo.cpp -o echo" it create an echo file, contain: ------------------------------------- [yue at RH9 Shootout-C++]$ cat echo #!/bin/sh lli \ -load=/usr/lib/libm.so \ $0.bc $* --------------------------------------- and using "llvmgcc echo.cpp -o echo-c", it creates an echo-c file, contain:

> Yes, this is no problem. You can do something like > this: > > $ llvmgcc X.c -c -o X.bc > $ llc X.bc -o X.s > $ gcc Y.c -o Y.o -c > $ gcc X.s Y.o -o program > $ ./program Ok, fine, and what about the interpreter? It takes 100% llvm, doesn't it? Or is there some kind of import facility (perhaps as an specially interpreted call or as an extension to llvm which makes

Hi all LLVMor, I just tried to compile a simple code and analyze the number of the basic blocks. But after compile, what I got, the bytecode is seems to be optimized bytecode. So the information of basic blocks is not what I expected. I want ot use the code as example to see how some of code optimization methods work. However, after compiling file using llvm test.c -o test, bytecode file

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?