search for: gcc_install_sparc

...of 'llvmgcc he.c -v' xli3|csil-suna27|~/cs426|[35]% llvmgcc he.c -v Reading specs from /usr/dcs/projects/cs426/Software/gcc_install/bin/../lib/gcc-lib/llvm/3.1/specs Configured with: /home/vadve/lattner/cvs/gcc/configure --srcdir=/home/vadve/lattner/cvs/gcc --prefix=/home/vadve/lattner/cvs/gcc_install_sparc --target=llvm --enable-languages=c --includedir=/home/vadve/lattner/cvs/gcc_install_sparc/llvm/include --with-as=/home/vadve/lattner/cvs/gcc_install_sparc/bin/llvm-as --with-ld=/home/vadve/lattner/cvs/gcc_install_sparc/bin/llvm-ld gcc version 3.1 20010410 (experimental) /usr/dcs/projects/cs426/Sof...

...llvmgcc he.c -v > > Reading specs from > > /usr/dcs/projects/cs426/Software/gcc_install/bin/../lib/gcc-li > > b/llvm/3.1/specs > > Configured with: /home/vadve/lattner/cvs/gcc/configure > > --srcdir=/home/vadve/lattner/cvs/gcc > > --prefix=/home/vadve/lattner/cvs/gcc_install_sparc > > --target=llvm --enable-languages=c > > --includedir=/home/vadve/lattner/cvs/gcc_install_sparc/llvm/include > > --with-as=/home/vadve/lattner/cvs/gcc_install_sparc/bin/llvm-as > > --with-ld=/home/vadve/lattner/cvs/gcc_install_sparc/bin/llvm-ld > > gcc version 3.1 20...

...i3|csil-suna27|~/cs426|[35]% llvmgcc he.c -v > Reading specs from > /usr/dcs/projects/cs426/Software/gcc_install/bin/../lib/gcc-li > b/llvm/3.1/specs > Configured with: /home/vadve/lattner/cvs/gcc/configure > --srcdir=/home/vadve/lattner/cvs/gcc > --prefix=/home/vadve/lattner/cvs/gcc_install_sparc > --target=llvm --enable-languages=c > --includedir=/home/vadve/lattner/cvs/gcc_install_sparc/llvm/include > --with-as=/home/vadve/lattner/cvs/gcc_install_sparc/bin/llvm-as > --with-ld=/home/vadve/lattner/cvs/gcc_install_sparc/bin/llvm-ld > gcc version 3.1 20010410 (experimental) &...

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

...ason, it is trying to use the 'as' in your path, which is the LLVM assembler. This is supposed to point to the 'gccas' program with an explicit path. I'm not sure why the sparc C frontend is misconfigured, here on the research machines I get this: ... /home/vadve/lattner/cvs/gcc_install_sparc/lib/gcc-lib/llvm/3.1/include /home/vadve/lattner/cvs/gcc_install_sparc/llvm/include End of search list. /home/vadve/lattner/cvs/gcc_install_sparc/bin/llvm-as -o test.o /var/tmp//ccUnJjqz.s which definately IS using the explicit path to llvm-as (aka gccas). I'll get in touch with Vikram to t...

...ernal' keyword instead of 'uninitialized' as appropriate (plus other changes). If you are seeing stuff break, make sure you update your LLVM tree, and make sure your llvmgcc alias is pointing to the right place (on the research machines, the right location is: /home/vadve/lattner/cvs/gcc_install_sparc/bin/llvm-gcc /home/vadve/lattner/cvs/gcc_install_x86/bin/llvm-gcc not /home/vadve/lattner/cvs/gcc_install/bin/* If you have problems after making these changes, please let me know. -Chris http://llvm.cs.uiuc.edu/ http://www.nondot.org/~sabre/Projects/

...cc_install alone for the time being. It is not correctly built, has problems, and is (among other things) huge (217M vs 21M for the x86 build). As soon as my LLVM tree is done building on solaris, I will make a new sparc version of the GCC frontend available in /home/vadve/lattner/cvs/gcc_install_sparc, with all of the nice characteristics of the x86 build. In a few weeks, or whenever I think about it, I will nuke the old /home/vadve/lattner/cvs/gcc_install directory, so you all should transition over sometime in the near future. As long as this tree is alive, gcc_install/bin/gcc...