On Fri, 21 Jul 2006, Rainer Orth wrote:

> I think it would be unwise to base this on a sort of isolated branch of GCC
> development.  As I've suggested before
> this should be done within the GCC community as much as possible, which is
> an important part of SFW as well: work with the upstream developers and
> minimize Solaris-local code changes.

what exactly do you propose from technical side:
create 3 gcc-csl branches and test ON on 4 compilers ?

I think it would unwise to try to support development branch which is 4.2
in ON. Do you see that Linux adopts it ?
The most recent shipped Ubuntu kernel for sparc 2.6.15 is built
with gcc 4.0.3-1

One thing is to make ON buildable with gcc 4.1 or 4.2, but to support
it is a bit different.

> While this does not apply to the ON changes necessary to build with GCC
> (either GCCfss or GCC 4), it applies to the GCC changes necessary to do so.

That's orthogonal discussion. It's certainly would be great to have
GCC developers test their new features on ON.

> On the other hand, I'd strongly argue against basing any development on GCC
> 4.0.x right now: there will most likely be no further release from that
> branch, so I'd suggest to concentrate on the latest stable GCC release
> (4.1.1 right now) or even on making sure everything still works with the
> upcoming GCC 4.2.0 instead.  Basing considerable amounts of work on an
> obsolete version is a loosing proposition IMO.

No SC sponsored releases doesn't mean that there will be no further releases
from 4.0 branch. It seems Linux doesn't see the extra value of gcc 4.1

Alex.

_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Reply via email to