From: Benjamin Kosnik <bkoz@redhat.com>
To: gcc@gcc.gnu.org
Cc: jbuck@synopsys.com
Subject: Re: draft release notes for gcc 3.3
Date: Wed, 07 May 2003 17:50:00 -0000 [thread overview]
Message-ID: <20030507124939.0da846eb.bkoz@redhat.com> (raw)
Joe,
> (Need to say something about C++ binary compatibility, versioning of
> libstdc++ etc).
It's my thought that you should say that 3.3.x is C++ ABI compatible
with 3.2.x. I believe this is certainly the intention.
For instance, libstdc++.so will be versioned at 5.0.4, ie "next in the
series after 3.2.3's libstdc++.so.5.0.3". The current branch passes the
C++ library ABI checks (in the 'make check-abi' rule), so it is assumed
safe.
> 8463 std::ios_base has a non-virtual destructor
8463 is not fixed, nor fixable, for 3.3 due to ABI constraints, sadly.
It is fixed on mainline. Everything else looks ok though.
best,
benjamin
next reply other threads:[~2003-05-07 17:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 17:50 Benjamin Kosnik [this message]
2003-05-07 18:06 ` Joe Buck
2003-05-07 21:30 ` Benjamin Kosnik
2003-05-07 21:43 ` Phil Edwards
2003-05-08 23:59 ` Joe Buck
2003-05-09 2:59 ` Benjamin Kosnik
2003-05-09 4:28 ` Benjamin Kosnik
2003-05-09 16:20 ` Joe Buck
2003-05-09 16:34 ` Benjamin Kosnik
2003-05-09 7:24 ` Matthias Klose
2003-05-09 16:24 ` Benjamin Kosnik
-- strict thread matches above, loose matches on Subject: below --
2003-05-07 22:14 Benjamin Kosnik
2003-05-07 22:46 ` Joe Buck
2003-05-08 7:14 ` Gerald Pfeifer
2003-05-07 17:28 Joe Buck
2003-05-07 18:04 ` Phil Edwards
2003-05-07 21:35 ` Gerald Pfeifer
2003-05-07 21:42 ` Steven Bosscher
2003-05-07 21:45 ` Phil Edwards
2003-05-07 22:17 ` Joe Buck
2003-05-08 9:46 ` Gabriel Dos Reis
2003-05-07 18:45 ` Steven Bosscher
2003-05-07 19:32 ` Joe Buck
2003-05-08 2:10 ` Kaveh R. Ghazi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030507124939.0da846eb.bkoz@redhat.com \
--to=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).