On Fri, 21 Jul 2006, Rainer Orth wrote: > I think I asked this before when you announced GCCfss on the main gcc list: > how much work would it be to turn GCCfss into a generic (i.e. both sparc > and x86) GCC with the Sun backend? It seems that the backend interface is > identical between sparc and x86, so it may be not much more than a > recompile of GCCfss on x86. We should strive for feature parity between > sparc and x86 as much as possible.
That's not what I meant. "For sparc and for x86 it can be made to be built from the same source tree. It will use Sun Studio backend on sparc and plain gcc backend on x86" > > gcc needs few extra features to build ON, so it can't be plain gcc4. Yet > > another gcc branch with Solaris required features may be too costly. > This should happen in a solaris vendor branch in the main GCC repository, > not an isolated development work. As far as possible, the solaris-specific > changes need to be identified and integrated upstream, with the few > remaining ones kept on a properly maintained solaris branch. Once this is > done, the result can be integrated into SFW practically unchanged. So what exactly do you suggest? have gcc-4.1-csl branch with Solaris related changes? 4.2 is out of the question as I mentioned in the other thread. I'd much prefer to have 4.0.3 based one, since I don't see the value of 4.1 for Solaris. > I consider it quite important for Sun/the OpenSolaris community to be seen > as an integral part of the GCC community: working there as much as possible > gives us much more credibility than doing things in our own private hole. > Besides, all efforts there would be for the benefits of both vanilla GCC > and it's users on Solaris as well as the OpenSolaris community. Agree. I guess first try to convince gcc developers to test new features on ON. As you can see ON is ready to test with gcc. Alex. _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
