Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Aug 2002 15:27:03 -0400
From:      Alexander Kabaev <ak03@gte.com>
To:        "Long, Scott" <Scott_Long@adaptec.com>
Cc:        Scott_Long@adaptec.com, jesse_gross@yahoo.com, current@freebsd.org
Subject:   Re: GCC 3.2
Message-ID:  <20020815152703.2f0f23e1.ak03@gte.com>
In-Reply-To: <2C7CBDC6EA58D6119E4A00065B3A24CB046493@btcexc01.btc.adaptec.com>
References:  <2C7CBDC6EA58D6119E4A00065B3A24CB046493@btcexc01.btc.adaptec.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> I agree that gcc32 is not an ideal target either, but by going to it,
> we can upgrade to gcc33 when it's available and not loose binary
> compatibility (at least, according to the gcc folks).  I'd rather
> move to gcc32 right now and get the binary compatibility pain out of
> the way, rather than wait for the last second to move to gcc33,
> then have to delay FreeBSD 5.0 because everything in c++ land is
> broken.

The idea is to move to gcc 3.3-pre _now_ If GCC 3.2 has C++ ABI
kinks worked out, GCC 3.3 surely has the same code in. GCC developers
are trying to keep C++ ABI compatible between 3.2 and 3.3, but they are
not giving any guaranrtees.

-- 
Alexander Kabaev

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?20020815152703.2f0f23e1.ak03>