Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Apr 2005 08:05:14 -0600
From:      Scott Long <scottl@samsco.org>
To:        Miguel Mendez <flynn@energyhq.es.eu.org>
Cc:        kris@obsecurity.org
Subject:   GCC 4.0 [Re: FreeBSD 6 is coming too fast]
Message-ID:  <426CF91A.8060907@samsco.org>
In-Reply-To: <20050425160146.4795fe1b.flynn@energyhq.es.eu.org>
References:  <20050424175543.71041.qmail@web51805.mail.yahoo.com> <20050424151517.O68772@lexi.siliconlandmark.com> <3822.216.177.243.38.1114385370.localmail@webmail.dnswatch.com> <20050425000459.GA28667@xor.obsecurity.org> <6.2.1.2.0.20050424204611.072105a0@64.7.153.2> <20050425010242.GA44110@xor.obsecurity.org> <6.2.1.2.0.20050424210422.03d22990@64.7.153.2> <20050425014453.GA59981@xor.obsecurity.org>	<426C6B1D.3040704@elischer.org> <20050425061459.GA33247@xor.obsecurity.org> <20050425062106.GB91852@voodoo.oberon.net>	<426CF3DE.4000409@samsco.org> <20050425160146.4795fe1b.flynn@energyhq.es.eu.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Miguel Mendez wrote:
> On Mon, 25 Apr 2005 07:42:54 -0600
> Scott Long <scottl@samsco.org> wrote:
> 
> 
>>>According to gcc-4.0 release notes, compilation speed for C++ was
>>>dramatically increased, up to 25% IIRC.  I think 4.0 is good
>>>candidate for merging into HEAD.
> 
> 
>>Is this work that you plan on doing for us?  
> 
> 
> Definitely not for 6.0, and I usually avoid .0 releases on critical
> software, but nonetheless it would interesting setting a tinderbox,
> launch a buildworld process with gcc40 and see where/if it breaks. I
> have a spare k6-2 box I could setup for that task.
> 
> 
>>What about the deprecated language constructs in 4.0?
> 
> 
> According to http://gcc.gnu.org/gcc-4.0/changes.html, some of the
> deprecated constructs are not even valid C, so I see this as an
> opportunity to fix buggy code. 
> 
> 
>>What about the lack of exposure that it's
>>had outside of the FSF and Apple development circles?
> 
> 
> Exactly the reason why testing will be beneficial. The more tested the
> product on FreeBSD the more robust it will be when it's time to get it
> into the tree.
> 
> Cheers,

Well, I'd caution against jumping into GCC 4.0 just because of the
claims of 25% speed improvement.  That's about the single worst reason
to do it.  But if you're interested in moving the technology forward,
I'd happily encourage you.  The changed language constructs are the big
problem (extern struct foo bar[]; is no longer valid) since you not only
need to sweep the FreeBSD tree for them, you also need to sweep the
ports tree.  I have mixed feeling on the value of GCC making sloppy
language extentions available for years and then suddenly revoking them,
and I know others that have been affected by 4.0 aren't terribly happy
either.

Scott



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?426CF91A.8060907>