Bob Palowoda <[EMAIL PROTECTED]> writes:

> As you all know the GCC team has released as of May 26 the GCC 4.1.1 compiler 
> suite. 
> With respect to build 37 of Nevada the gcc version is 3.4.3 which might be a 
> little dated
> from the 3.4.6 build from the gcc.gnu.org site.  Thank you all the engineers 
> that 

The version of GCC 3.4.3 delivered in /usr/sfw/bin is considerably
different from a stock FSF GCC 3.4.3: it includes lots of changes done by
CodeSourcery to support amd64 on Solaris/x86, among others.

>  Some basic questions:
> 
>  By the definition of support of /usr/sfw/bin/gcc does the version changes 
> stop at this version or where the changes from build 3.4.4/5/6 integrated
> into the current build?

I don't think this would be worth the effort unless it can be demonstrated
that those versions deliver important bug fixes compared to the
/usr/sfw/bin gcc 3.4.3.

>  What are the current gcc compiler problems of the 4.0, 4.1.1 and 4.2 
> compiler suites that are stopping them from being considered for
> any current build of OpenSolaris? 
> (by this I mean are there show stoppers that prevent the upgrade)

As I mentioned before on this thread

        http://www.opensolaris.org/jive/thread.jspa?threadID=6799&tstart=0
        http://www.opensolaris.org/jive/thread.jspa?threadID=6911&tstart=0

the /usr/sfw/bin gcc contains some changes that couldn't be integrated into
the upstream/FSF gcc for either political or technical reasons.  Before
those specific changes have been identified and made (e.g. in a branch in
the main GCC SVN repository), migrating to 4.1.x isn't an option since the
resulting gcc wouldn't work to build OpenSolaris.

Apart from that, testing of the full gcc 4.1 and mainline on Solaris/x86
almost isn't happening, and even less fixes being contributed from the
Solaris community.  I mentioned a couple of issues in the thread above.
Right now, you cannot bootstrap gcc 4.1 or mainline on Solaris/x86 since
boehm-gc doesn't build.  There need to be more contributors to GCC from the
OpenSolaris community.

>  Any issues with PSARC and upgrading gcc to 4.1.1?

I don't think this would make sense: by the time Solaris 11 (or whatever
it will be called then) is released, 4.1.x will be ancient history.  It
might be useful to provide an (unmodified) gcc 4.1.x via the companion
consolidation, though, since that version wouldn't be required to be able
to build OpenSolaris.

>  What are the considerations for gcc 4.2.2?

I had outlined a plan going forward with keeping either mainline GCC or a
constantly updated OpenSolaris branch thereoff working for OpenSolaris and
integrating the then-latest stable version into OpenSolaris in the thread
above.  So far, there hasn't been much response (and much less help), and
I've been both away and swamped with other issues to work much on GCC
lateley.

        Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to