Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-24 Thread Christoph Hellwig
On Mon, Jul 24, 2006 at 12:52:43PM -0700, Alexey Starovoytov wrote: > On Mon, 24 Jul 2006, Christoph Hellwig wrote: > > > That is of course utter bullshit. The Linux kernel doesn't require > > a specific gcc version. > > I didn't say it requires. I said shipped Linux kernel is always built with

Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-24 Thread Alexey Starovoytov
On Mon, 24 Jul 2006, Christoph Hellwig wrote: > That is of course utter bullshit. The Linux kernel doesn't require > a specific gcc version. I didn't say it requires. I said shipped Linux kernel is always built with patched gcc. Please prove otherwise. __

Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-24 Thread Christoph Hellwig
On Mon, Jul 24, 2006 at 09:11:23PM +0200, Rainer Orth wrote: > > 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 > > This may be for the same reasons as with Solaris: they may require specific > changes

Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-24 Thread Christoph Hellwig
On Fri, Jul 21, 2006 at 02:03:03PM -0700, Alexey Starovoytov wrote: > > * 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 rel

Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-24 Thread Rainer Orth
Alexey, > Glad to hear that this effort was made and that some x86 features went it. > I'm mostly concerned about sparc side. > > Let's see: > -fno-jump-tables for x86 - IN > -mno-integer-ldd-std for sparc - not in > -fno-constant-pools for x86- not in > -fno-dwarf2-indirect-strings

Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-24 Thread Rainer Orth
Michael, > Rainer Orth wrote: > > I don't see CodeSourcery being very active with GCC for Solaris > > work these days (maybe their contract has ended?) > > No, their contract has not ended. (I am the initiator/manager of the contact > for the 3.4.3 compiler). > > We just don't have a whole l

Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-24 Thread Rainer Orth
Alexey, > 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. I'm not sure: since the 4.2 branch

Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-21 Thread Alexey Starovoytov
On Fri, 21 Jul 2006, Michael Pogue wrote: > Alexey Starovoytov wrote: > > '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. > .. > > The prerequisite for that is to have 'diff csl-sol

Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-21 Thread Michael Pogue
Alexey Starovoytov wrote: > '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. .. > The prerequisite for that is to have 'diff csl-sol210-3_4-branch gcc_343' > integrated into gcc trunk O

Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-21 Thread Michael Pogue
Rainer Orth wrote: > I don't see CodeSourcery being very active with GCC for Solaris > work these days (maybe their contract has ended?) No, their contract has not ended. (I am the initiator/manager of the contact for the 3.4.3 compiler). We just don't have a whole lot of bugs that need fixin

Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-21 Thread Alexey Starovoytov
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

Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-21 Thread Rainer Orth
Alexey, > what exactly do you propose from technical side: > create 3 gcc-csl branches and test ON on 4 compilers ? no: I'd propose the following: * Identify the changes currently local to the csl-sol210-3_4-branch branch (which is the basis for the gcc 3.4.3 in sfw) necessary to build OpenS

Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-21 Thread Alexey Starovoytov
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 dev

Re: [osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-21 Thread Rainer Orth
Alexey Starovoytov <[EMAIL PROTECTED]> writes: > Since ON is buildable with /usr/sfw/bin/gcc 3.4, I'm proposing to make it > buildable with GCCfss (GCC for SPARC Systems) on sparc and with plain gcc > 4.0.x on x86. > > Because of the changes introduced in gcc version 4.0, ON didn't work with >

[osol-discuss] Project proposal: support GCCfss and gcc 4 in ON

2006-07-20 Thread Alexey Starovoytov
Hi, Since ON is buildable with /usr/sfw/bin/gcc 3.4, I'm proposing to make it buildable with GCCfss (GCC for SPARC Systems) on sparc and with plain gcc 4.0.x on x86. Because of the changes introduced in gcc version 4.0, ON didn't work with GCCfss (which is based on gcc 4.0.x) and/or plain gcc