Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Aug 2002 16:49:45 -0700
From:      Terry Lambert <tlambert2@mindspring.com>
To:        Alexander Kabaev <ak03@gte.com>
Cc:        Scott_Long@adaptec.com, jesse_gross@yahoo.com, current@freebsd.org
Subject:   Re: GCC 3.2
Message-ID:  <3D5C3E19.D4EE4ED5@mindspring.com>
References:  <2C7CBDC6EA58D6119E4A00065B3A24CB046493@btcexc01.btc.adaptec.com> <20020815152703.2f0f23e1.ak03@gte.com> <3D5C21C3.7A848926@mindspring.com> <20020815180723.00a5a83d.ak03@gte.com> <3D5C2F93.BE3BE8B0@mindspring.com> <20020815192849.762e4182.ak03@gte.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Alexander Kabaev wrote:
> > Can *you* absolutely *guarantee* no binary incompatabilities
> > between 3.3, as it sits now, in experimental form, and the final
> > release of 3.3?  If not, then I don't see why are exploding at
> > me.
> 
> 3.1-pre to 3.2 upgrade breaks compatibility already. Can you guarantee
> that 3.3 will be backwards compatible with 3.2? This is yet another
> potential ABI breakage at the time when we'll be _forced_ to upgrade.
> How often do you expect GCC developers to break ABI with release
> scheduled to happed and the end of the year?

Once for every time the code is imported into FreeBSD, plus one.

I think Murphy is a GCC committer... 8-).

-- 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?3D5C3E19.D4EE4ED5>