Help: want to build automatic .i-based tester for GCC

[James E Wilson]

Paolo Bonzini wrote:
> To do so, I need the .i files.  It is as easy as bootstrapping with 
> -save-temps and putting a tarball (gzipped or bzip2-ed) somewhere on the 
> web.  I'd be particularly interested in ia64, powerpc and sparc 
> preprocessed sources, but other targets cannot be bad of course.

I am not sure that static .i files like this will work.  Before long you 
will be testing different sources than we actually use in the compiler. 
  Also, you may run into cases where bug fixes require parts of gcc to 
be rewritten, and then your tester is unusable unless someone 
regenerates the .i files.

Incidentally, you can generate these .i files yourself by using Dan 
Kegel's crosstool scripts to build your own cross compilers complete 
with binutils/glibc/linux kernel headers.  You can then regenerate the 
.i files at will when you need them.  This will take a bit of disk space 
(cough), but shouldn't be too difficult to set up.  See
     http://kegel.com/crosstool/
You could built gcc-3.3.x based cross compilers for all of the targets 
of interest, and could then use these cross compilers to generate the .i 
files for mainline gcc.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com