> On Wed, 8 Dec 2010, Jack Howarth wrote: >> On Wed, Dec 08, 2010 at 01:44:38PM -0500, Dennis Clarke wrote: >> > > On Wed, Dec 08, 2010 at 02:42:56PM +0100, Richard Guenther wrote: >> > >> <snip wonderful work> >> > > This was built against ppl 0.10.2 and cloog 0.15.10. >> > >> > Have you tried a bootstrap with neither ppl nor cloog ? I have yet to >> see >> > their value and I generally exclude them. This results ( thus far ) in >> > nice clean bootstrap builds. >> Dennis, >> Considering that distros like Fedora ship their gcc's with graphite >> support built-in, allowing graphite to regress like this between gcc maintenance releases doesn't seem like a very good idea. > > The SUSE builds look fine. You have to investigate why it doesn't work for you, but it won't hold the 4.5.2 release. Are your > ppl and cloog testsuite runs clean? Did you by chance build them with a different GCC release (and thus libstdc++)? > > Thanks, > Richard.
Good question ! I generally do a double bootstrap in which my first build is done with a previous version of GCC. Once I see reasonable testsuite results I then use the resultant compiler from the first bootstrap to build the "release" version. This then explains why the compiler that build GCC 4.5.1 on Solaris 8 is in fact, GCC 4.5.1 : http://gcc.gnu.org/ml/gcc-testresults/2010-09/msg02183.html However, having said all this I have yet to see either the ppl or cloog software components build once on the legacy Solaris platform I must support baseline legacy Solaris 8 which in turn assures functionality upwards to Solaris 10 and possibly 11. http://www.blastwave.org/jir/pkgcontents.ftd?software=gcc4&style=brief&state=5&arch=sparc -- Dennis Clarke dcla...@opensolaris.ca <- Email related to the open source Solaris dcla...@blastwave.org <- Email related to open source for Solaris
