search for: d__llvm__

.../gcc_install_sparc/bin/llvm-ld gcc version 3.1 20010410 (experimental) /usr/dcs/projects/cs426/Software/gcc_install/bin/../lib/gcc-lib/llvm/3.1/cc1 -lang-c -v -iprefix /usr/dcs/projects/cs426/Software/gcc_install/bin/../lib/gcc-lib/llvm/3.1/ -D__GNUC__=3 -D__GNUC_MINOR__=1 -D__GNUC_PATCHLEVEL__=0 -D__llvm__ -D__llvm__ -Asystem=unix -Asystem=bsd -D__STDC_HOSTED__=1 he.c -quiet -dumpbase he.c -version -o /var/tmp//ccobi9kx.s GNU CPP version 3.1 20010410 (experimental) (cpplib) (llvm) GNU C version 3.1 20010410 (experimental) (llvm) compiled by GNU C version 2.95.3 20010315 (release). ignoring no...

...> > /usr/dcs/projects/cs426/Software/gcc_install/bin/../lib/gcc-li > > b/llvm/3.1/cc1 > > -lang-c -v -iprefix > > /usr/dcs/projects/cs426/Software/gcc_install/bin/../lib/gcc-li > > b/llvm/3.1/ > > -D__GNUC__=3 -D__GNUC_MINOR__=1 -D__GNUC_PATCHLEVEL__=0 > > -D__llvm__ -D__llvm__ -Asystem=unix -Asystem=bsd > > -D__STDC_HOSTED__=1 he.c -quiet -dumpbase he.c -version -o > > /var/tmp//ccobi9kx.s GNU CPP version 3.1 20010410 > > (experimental) (cpplib) (llvm) GNU C version 3.1 20010410 > > (experimental) (llvm) > > compiled by GN...

....1 20010410 (experimental) > > /usr/dcs/projects/cs426/Software/gcc_install/bin/../lib/gcc-li > b/llvm/3.1/cc1 > -lang-c -v -iprefix > /usr/dcs/projects/cs426/Software/gcc_install/bin/../lib/gcc-li > b/llvm/3.1/ > -D__GNUC__=3 -D__GNUC_MINOR__=1 -D__GNUC_PATCHLEVEL__=0 > -D__llvm__ -D__llvm__ -Asystem=unix -Asystem=bsd > -D__STDC_HOSTED__=1 he.c -quiet -dumpbase he.c -version -o > /var/tmp//ccobi9kx.s GNU CPP version 3.1 20010410 > (experimental) (cpplib) (llvm) GNU C version 3.1 20010410 > (experimental) (llvm) > compiled by GNU C version 2.95.3 20...

Dear llvm, I just tried to compile a simple file hello.c. But each time I used llvmgcc hello.c, it gave me the following error: xli3|csil-suna33|~/cs426|[13]% llvmgcc hello.c as: error opening '/var/tmp//ccapglpE.o': file exists! Use -f command line argument to force output I really got confused. Could you please let me know what's wrong? thanks, Jerry

...ther related thing is that even when I defined -emit-llvm in what I thought would be a global CFLAGS for all of newlib, it did not get propagated to all subdirectories. I solved both of these issues by creating a shell script that is just a fall-through to llvm-gcc, but passes "-emit-llvm -D__LLVM__" to it. It might be worthwhile to have a similar thing in the LLVM distribution, that is, a compiler that would identify the target as LLVM and produce byte code by default. There was very little to do in terms of porting. Basically the only thing I needed to tweak in the source code was to d...

I have been browsing through the newlib documentation at <http://sources.redhat.com/newlib/> and pondering about how newlib relates to LLVM. Comments welcome, again. As I see it, there are basically two parts of libc that need to be considered. Much of libc is stuff like atoi(), isalpha(), etc. which are just convenience routines written in ANSI C. For these, it should be sufficient to

We are going to use LLVM in a compiler project for transport triggered processors. See Wikipedia for more on transport triggering: <http://en.wikipedia.org/wiki/Transport_Triggered_Architectures>. One thing we need is some sort of libc. We are targeting embedded systems, and I have been looking at things like newlib. Are there people out there doing something similar? Or any advice or

...thought would be a global CFLAGS for all of newlib, it did > not get propagated to all subdirectories. Oh? Which ones did it not get propagated to? > > I solved both of these issues by creating a shell script that is > just a fall-through to llvm-gcc, but passes "-emit-llvm -D__LLVM__" > to it. It might be worthwhile to have a similar thing in the LLVM > distribution, that is, a compiler that would identify the target as > LLVM and produce byte code by default. > > There was very little to do in terms of porting. Basically > the only thing I needed to twe...