Date: Sun, 20 Jan 2002 01:02:28 -0500 From: Mike Barcroft <mike@FreeBSD.ORG> To: Dan Nelson <dnelson@allantgroup.com> Cc: Terry Lambert <tlambert2@mindspring.com>, Alp Atici <aa878@columbia.edu>, freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD 5.x Message-ID: <20020120010228.C68881@espresso.q9media.com> In-Reply-To: <20020120053629.GE81627@dan.emsphone.com>; from dnelson@allantgroup.com on Sat, Jan 19, 2002 at 11:36:29PM -0600 References: <Pine.GSO.4.44.0201191709540.2959-100000@ciao.cc.columbia.edu> <3C4A53EE.B882356C@mindspring.com> <20020120053629.GE81627@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Nelson <dnelson@allantgroup.com> writes:
> In the last episode (Jan 19), Terry Lambert said:
> > Alp Atici wrote:
> > > Is gcc 3.x going to be the default compiler starting from FBSD 5.x
> > > series? Is the development on current branch compiled using gcc 3.0
> > > (or up)?
> >
> > I think that the cut over will happen after the compiler
> > no longer core dumps on:
> >
> > main()
> > {
> > int i;
> >
> > i = foo();
> >
> > switch( i) {
> > default:
> > printf( "hello, stupid compiler!\n");
> > break;
> > }
> > }
> >
> > int
> > foo()
> > {
> > return( 6);
> > }
>
> Doesn't core on me (gcc30+bounds-checking port, FreeBSD-current). In
> fact, I've got USE_GCC30 in my make.conf and build all my ports with it
> (at least the ports that aren't broken and hardcode cc or gcc).
Interesting. The sparc64 toolchain suffers from this problem, so a
number of files on the sparc64 p4 branch have custom versions.
Anyway, I'm told this problem has been fixed in 3.1, which is the
planned version of GCC for 5.0-RELEASE.
Best regards,
Mike Barcroft
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?20020120010228.C68881>