Date: Fri, 22 Nov 2002 03:37:53 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: Marc Recht <marc@informatik.uni-bremen.de>, Harald Arnesen <harald@skogtun.org>, David Schultz <dschultz@uclink.Berkeley.EDU>, David O'Brien <obrien@FreeBSD.ORG>, freebsd-current@FreeBSD.ORG Subject: Re: gcc 3.2.1 release import? Message-ID: <3DDE1711.6B9606B4@mindspring.com> References: <55350000.1037811461@leeloo.intern.geht.de> <20021121041449.GA17530@dragon.nuxi.com> <20021121214614.GA6062@HAL9000.homeunix.com> <87bs4iczjd.fsf@basilikum.skogtun.org> <87590000.1037924015@leeloo.intern.geht.de> <3DDD7F10.BFED05F7@mindspring.com> <120820000.1037929067@leeloo.intern.geht.de> <3DDDCD32.6D74D775@mindspring.com> <20021122064625.GA12620@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Kargl wrote:
> > Don't worry about it; it's being totally blown out of proportion;
> > there's no way anyone will commit to importing a 2 day old 3.2.1,
> > which is why I put the smiley's there.
>
> Well, the 2-day old 3.2.1 fixes numerous problems
> with our 3.2.1 [FreeBSD] 20021009 (prerelease).
>
> Compiling this
>
> void ice(int m, int n, double *f) {
> int i, j;
> for (j = 0; j < n; j++) {
> for (i = 1; i < m; i++) {
> f[i] = (double) (i * j);
> f[i + j] = (double) ((i + 1) * j);
> }
> }
> }
>
> with "gcc -O2 -c" yields an ICE in FreeBSD-current.
> The 2-day old gcc 3.2.1 does not blow chucks on the
> above code.
What does it do for all the other code in -ports, and in the
comp.source.* archives, and that anyone else has ever written,
such that you know it doesn't cause more problems than it
solves?
Supposedly, bringing in 3.2 was going to solve more problems
than it caused. It turns out the 4.x compiler, GCC 2.95.3,
also does not have an ICE as a result of compiling that code.
What is food to one, is to others bitter poison.
-- Titus Lucretius Carus
When you are updating tools, it's actually about risk/reward;
the risk of not supporting IA64, and the risk of the object
file compatability has (supposedly) be addressed.
The only other reasonable path would be to tie FreeBSD releases
to GCC releases, plus some period of time for burn-in, and that
really isn't reasonable: 3.3 was supposed to be out already;
should FreeBSD's release schedule slip every time GGC's slips?
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DDE1711.6B9606B4>