Diego Novillo wrote:
The tuples branch is at the point now that it should bootstrap all
primary languages and targets. There are things that are still broken
and being worked on (http://gcc.gnu.org/wiki/tuples), but by and large
things should Just Work.
I expect things like code generation to be sub-par because some
optimizations are still not converted (notably, loop passes, PRE, and TER).
So, for folks with free cycles to spare, could you build the branch on
your favourite target and report bugs? Bugzilla and/or email reports
are OK. If you are creating a bugzilla report, please add my address to
the CC field.
Other than obvious brokenness, we are interested in compile time slow
downs and increased memory utilization. Both of which are possible
because we have spent no effort tuning the data structures yet.
To build the branch:
$ svn co svn://gcc.gnu.org/svn/gcc/branches/gimple-tuples-branch
$ mkdir bld && cd bld
$ ../gimple-tuples-branch/configure --disable-libgomp --disable-libmudflap
$ make && make -k check
For mipsel-linux:
http://gcc.gnu.org/ml/gcc-testresults/2008-05/msg01055.html
The complete bootstrap/test cycle seems to be about 10% faster than on
the trunk. I didn't try to figure out why, although I can speculate
that it is due to the fact that some optimization passes are still
disabled and that tests that ICE prevent the corresponding execution
test to be run.
Comparing the test results to a recent trunk build shows many FAILures
that are only on the branch.
Although I didn't investigate, the FAILure in libjava/Array_3, usually
indicate that exception handling is broken in some way.
David Daney
