similar to: [LLVMdev] C front-end news

The problem with llvmgcc invoking as instead of llvm-as has been fixed. 3 llvm-specific executables needed to be copied into a default location where gcc can find them if it does not find them as configured (gcc was configured for the paths on our research machines and copied over). Let us know if you have additional problems. --Vikram > -----Original Message----- > From: llvmdev-admin

As I have been threatening: (http://mail.cs.uiuc.edu/pipermail/llvmdev/2002-October/000141.html) to do (http://mail.cs.uiuc.edu/pipermail/llvmdev/2002-September/000092.html) for some time now, I have regenerated the X86 and Sparc C frontends. They are now in-sync again and both emit the 'external' keyword instead of 'uninitialized' as appropriate (plus other changes). If you are

Thanks, Chris, Below is the output 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

Dear Prof. Adve, Now I can use llvmgcc to compile a .c file into .bc file. But I still have trouble simply run the .bc code. Below is the sequence I got when I tried. I really don't know what's going on here. Please let me know how can I fix it. Thanks, xiaodong xli3|csil-suna48|~/cs426|[13]% llvmgcc scalarize.c -o scalarize xli3|csil-suna48|~/cs426|[14]% scalarize Cannot load value of

> ok, I finished recompiling llvm, and when trying to use llvmgcc I get > the following error message: > as -o /var/tmp//ccIuGwwQ.o /var/tmp//ccZvtWKU.s > as: error opening '/var/tmp//ccIuGwwQ.o': file exists! > Use -f command line argument to force output Okay, this is the problem. For some reason, it is trying to use the 'as' in your path, which is the LLVM

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

Just like we did for X86: http://mail.cs.uiuc.edu/pipermail/llvmdev/2003-May/000382.html We're now switching over to the new C frontend on solaris. If you are doing development on solaris, you *must* make the following changes to your setup: 1. Change your llvm-gcc symlink (or alias, or whatever you use) to point to ~lattner/local/sparc/llvm-gcc/bin/gcc 2. Add the following environment

This is a note to let everyone know that I just changed the LLVM build scripts to use the new C front-end for everything (on X86). If you are doing development on X86, you *must* make the following changes to your setup: 1. Change your llvm-gcc symlink (or alias, or whatever you use) to point to ~lattner/local/x86/llvm-gcc/bin/gcc 2. Add the following environment variable to your startup

On Tue, Aug 25, 2009 at 3:01 PM, Vikram S. Adve<vadve at cs.uiuc.edu> wrote: > For my introductory Compiler Construction class, I have been giving > the students a project to write a simple compiler for a toy, single- > inheritance object-oriented language.  We give them a set of classes > implementing an AST for the language and a type checker as well.  The > students write

For my introductory Compiler Construction class, I have been giving the students a project to write a simple compiler for a toy, single- inheritance object-oriented language. We give them a set of classes implementing an AST for the language and a type checker as well. The students write (1) a scanner and parser to build the AST; (2) a translator from AST to LLVM; and (3) a couple of

Hi, In the quest for better test cases for my MP, I thought of trying the Stepanov Abstraction Penalty benchmark. But apparently llvm-g++ is not ready for such terrible things. Let me know if you want me to send the source code (it is widely available). gaeke|csil-suna37|~/cs/426/MP1/step|[1177]% /usr/dcs/projects/cs426/Software/gcc_install/bin/g++ stepanov.cpp -o stepanov In file included from

Just for the archive or in case of anybody is interested in: The problem is the missing stddef.h which resides more than one time on the OS. I mistakenly thought, that there is an typo in the code, because one of this files is in /us/include/linux so I changed #include <stddef.h> to #include <linux/stddef.h> But this was wrong and it is the wrong file too. The right file to

I've created fink packaging for a building the llvm and llvm-gcc-4.2 svn pulls under fink on Mac OS X. Hopefully the fink info script and patch should be clear enough for some comments on my build approach. The llvm-gcc and llvm-g++ compilers seem okay so far. The llvm-gfortran compiler seems to always spew a warning.. WARNING: 128-bit integers not supported! ...even when just compiling a

Chris Lattner wrote: > On Thu, 16 Mar 2006, Vladimir Prus wrote: >> Ah, hell, as soon as I've send this email I've updated from CVS to find >> that the issue was fixed by Jim several hours after I reported the crash, >> by making MachineDebugInfo don't check for empty name of type. > > :) > >> Here's what I get now: >> >>

Chris Lattner wrote: > On Thu, 2 Mar 2006, Vladimir Prus wrote: >>>> The instructions seem to have one path wrong. It says to get: >>> >>> I'll put together a tarball today. That will be easier than dealing >>> with a patch, and it will include a bunch of bugfixes since the previous >>> email. >> Further into process, I get this error:

Chris Lattner wrote: > Here's a new snapshot of the front-end: > http://nondot.org/sabre/2006-03-14-llvm-gcc-4.tar.gz > > This: > > 1. Fixes the inline asm problem you have above. > 2. Includes patches to make it better on Alpha's (thanks to patches by > Andrew Lenharth). > 3. Sync's it up with debug info changes in LLVM CVS (by Jim Laskey). > 4.

Vladimir Prus wrote: > So, it looks either the snapshot is not in stable state, or there's > something seriously wrong with type name handling. At this point I gave up > on quickly fixing this, so I've applied the third attached patch to LLVM, > which "fixes" this issue completely. Ah, hell, as soon as I've send this email I've updated from CVS to find that

Sean Peisert wrote: > John, > > I may be missing something here, but if I the compilation docs, I need > to build LLVM first and the C frontend second. But doing this, I > get: > > **llvm-gcc/llvm-g++ was not found, > > (obviously -- it wasn't installed, right?) You do need to build LLVM first before building llvm-gcc. This may seem a bit weird, but

Chris Lattner wrote: > On Wed, 1 Mar 2006, Vladimir Prus wrote: >>> I just pushed out the latest version of my new GCC4-based llvm-gcc here: >>> http://gcc.gnu.org/ml/gcc/2006-01/msg00931.html >>> This email includes status and instructions for use. >> >> The instructions seem to have one path wrong. It says to get: > > I'll put together a

I just checked in an important change to the LLVM Verifier pass, and have compiled a new version of the GCC front-end. The big change is that we now match the LangRef.html much more closely: many operations on pointer operands are illegal. Essentially, the GCC front-end should never generate adds, subtracts, multiplies, divides, rem, or shr/shl instructions that take pointer operands now. In