On Fri, 21 Jul 2006, Rainer Orth wrote: > * Try to get as many of those changes as possible into gcc mainline, either > for 4.2 or for 4.3 after 4.2 branches.
It cannot go into 4.2 apparently. I believe you're familiar with gcc policies. > * Create two solaris vendor branches (this isn't a csl-only thing, but > should be backed by the opensolaris community as a whole): one off gcc > 4.1 and another off gcc mainline. branch of the mainline ?! Such things are designed for new features and not for OS support. 'diff csl-sol210-3_4-branch gcc_343' should go into mainline, otherwise we'll end up with 'sol' branches for every major gcc release ON care to support. > * Continue testing with the 4.2/mainline based gcc to make sure it at least > compiles ON to be able to switch when/if it is released/stable enough. As you can see Linux _never_ switched to plain gcc release. New releases can be provided in distro, but kernel is alwasy based on some branch of some release branch. Currently they are 4.0s and 4.1s > The former certainly does not happen, the latter does, as you can see from > regular bug reports about issues detected when building and running Linux > with gcc mainline. Great ultimate goal. The prerequisite for that is to have 'diff csl-sol210-3_4-branch gcc_343' integrated into gcc trunk > should effectively target the Solaris 11 release, so baseing something on > GCC 4.0 for that release is a bad idea since that compiler will be > completely obsolete/unmaintained at that time. I completely disagree. gcc is still patching 3.4 branch. Alex. _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
