This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Solaris 8/SPARC bootstrap broken building 64-bit libgcc


> 3.3 went out the door with some amazing problems; I'm just now discovering
> them for myself.  I submit that, at present, the following statement is
> essentially true.
>
>     The sparc-sun-solaris2.* platform is not supported.

That's a bit unfair. You haven't cared about this platform for some time, 
suddendly you decide to give it a try and you run into some problems. This 
is to be expected on this platform, they are many nits to overcome. Instead 
of trying to understand them, you say that everything is broken.

You seem to be using a non-standard configuration (for example, I skimmed 
through dozen and dozen of bug reports for Solaris and never saw the 'sed' 
problem reported; you use bash to bootstrap, we explicitly recommend ksh).
Because of the shortage of resources, we are forced to support only a single 
procedure.

You reported that GCC 3.3 wasn't able to bootstrap itself and aborted with 
the exact same error as GCC 3.0.2. I answered that GCC 3.3 is able to 
bootstrap the current 3.3 branch and that you might not have properly 
reconfigured. Did you try another time?

You reported some installation problems with multilibs. I submitted a patch 
three weeks before the 3.3 release, but it was not reviewed quickly enough 
and missed the release.

Sure, sparc-sun-solaris2.* is not a first-class platform and the .0 releases
are very likely to have many regressions. But they will eventually be 
squashed in the subsequent .x releases. And take a look at the testsuite 
results on the 3.3 branch, they are on par with those of mainstream 
platforms.

> Proving this statement false would be wonderful.  A number of people
> have been tirelessly hunting down bugs (most recently, yourself and Eric
> Botcazou).  The expanding time required for a build-and-test cycle is
> what's defeating us.

Simply the lack of testing I'd say. The mainline is simply not tested on 
SPARC for development, period. So it is very likely that, during phase1, the 
platform will badly regress. So be it. In the meantime, we are fixing the 
most serious regressions on the branch.

-- 
Eric Botcazou


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]