From: "David O'Brien" <obrien@FreeBSD.org>
To: Allan Sandfeld Jensen <snowwolf@one2one-networks.com>
Cc: gcc@gcc.gnu.org, Mark Mitchell <mark@codesourcery.com>
Subject: Re: C++ ABI Issues
Date: Sat, 07 Sep 2002 13:32:00 -0000 [thread overview]
Message-ID: <20020907203239.GB41373@dragon.nuxi.com> (raw)
In-Reply-To: <200208271457.58862.snowwolf@one2one-networks.com>
On Tue, Aug 27, 2002 at 02:57:58PM +0200, Allan Sandfeld Jensen wrote:
> Since 3.3 has to stay compatible with 3.2, the 3.2 ABI will most likely have
> to stay default.
WHY?? 3.2->3.3 is a major version release, so ABI changes are allowed.
For FreeBSD we would like to see all known C++ ABI bugs fixed in 3.3.0.
It is not too late for us to move from 3.2 -> 3.3. In fact we've had so
many problems with our update to 3.2 from 3.1-prerelease that we may have
to go to 3.3 anyway.
The proposals for a switch to choose the C++ ABI sound excellent to
FreeBSD. I don't care if the default ABI is the 3.2 one, or the "bug
free" one -- I can easily set what we want in config/freebsd-specs.h.
A -Wabi in 3.2.1 would also be well received by FreeBSD as we can use
that to help decided if we should move to 3.3 for our 5.0 release.
next prev parent reply other threads:[~2002-09-07 20:32 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 15:18 Mark Mitchell
2002-08-26 16:18 ` Mike Stump
2002-08-26 16:43 ` Zack Weinberg
2002-08-26 21:58 ` Geoff Keating
2002-08-26 16:46 ` Loren James Rittle
2002-08-26 17:10 ` Joe Buck
2002-08-26 18:32 ` David Edelsohn
2002-08-26 18:35 ` David S. Miller
2002-08-26 19:25 ` David Edelsohn
2002-08-26 20:40 ` Per Bothner
2002-08-27 10:08 ` Joe Buck
2002-08-27 11:51 ` Jeff Law
2002-08-28 4:32 ` Richard Earnshaw
2002-08-26 18:47 ` Joe Buck
2002-08-26 23:27 ` Jakub Jelinek
2002-08-26 23:57 ` Mark Mitchell
2002-08-27 7:40 ` Jeff Law
2002-08-27 11:28 ` Phil Edwards
2002-08-27 11:32 ` Joe Buck
2002-08-27 11:43 ` Jan Hubicka
2002-08-27 12:00 ` Gabriel Dos Reis
2002-08-27 15:10 ` Joe Buck
2002-08-27 15:18 ` Gabriel Dos Reis
2002-08-27 12:09 ` Joe Buck
2002-08-27 12:34 ` Gabriel Dos Reis
2002-08-27 11:58 ` Gabriel Dos Reis
2002-08-27 14:50 ` Joe Buck
2002-08-27 15:06 ` Gabriel Dos Reis
2002-08-27 15:21 ` Joe Buck
2002-08-27 15:32 ` Gabriel Dos Reis
2002-08-27 15:46 ` Joe Buck
2002-08-27 22:28 ` Gabriel Dos Reis
2002-08-28 10:04 ` Joe Buck
2002-08-26 19:18 ` Jamie Lokier
2002-08-26 23:44 ` Mark Mitchell
2002-08-27 5:33 ` Nathan Sidwell
2002-08-27 5:58 ` Allan Sandfeld Jensen
2002-08-27 7:32 ` Nathan Sidwell
2002-09-07 13:32 ` David O'Brien [this message]
2002-09-22 2:49 ` David O'Brien
2002-09-22 11:15 ` Mark Mitchell
2002-09-23 10:01 ` Joe Buck
2002-09-23 13:04 ` David O'Brien
-- strict thread matches above, loose matches on Subject: below --
2002-08-27 10:26 Benjamin Kosnik
2002-08-27 11:06 ` Ziemowit Laski
2002-08-27 11:15 ` Mike Stump
2002-08-27 11:27 ` Ziemowit Laski
2002-08-27 11:56 ` Mike Stump
2002-08-27 15:19 ` Toon Moene
2002-09-07 13:33 ` David O'Brien
2002-08-27 14:37 ` Joe Buck
2002-08-28 4:41 ` Richard Earnshaw
2002-08-26 20:40 Benjamin Kosnik
2002-08-26 23:55 ` Mark Mitchell
2002-08-27 6:03 ` Daniel Jacobowitz
2002-08-27 6:40 ` Andreas Jaeger
2002-08-27 7:27 ` Jeff Law
2002-08-27 7:49 ` Jeff Law
2002-08-27 7:30 ` Jeff Law
2002-08-27 8:45 ` Mark Mitchell
2002-08-27 9:33 ` Janis Johnson
2002-08-27 14:55 ` Mark Mitchell
2002-08-27 9:50 ` Mark Mitchell
2002-08-27 10:50 ` Devang Patel
2002-08-27 12:02 ` Per Bothner
2002-08-27 10:37 ` Mike Stump
2002-03-18 13:44 C++ ABI issues mike stump
2002-03-18 10:30 Benjamin Kosnik
2002-03-18 13:05 ` Jason Merrill
2002-03-18 13:46 ` Mark Mitchell
2002-03-18 14:13 ` Benjamin Kosnik
2002-03-18 15:19 ` Jason Merrill
2002-03-17 16:33 Jason Merrill
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=20020907203239.GB41373@dragon.nuxi.com \
--to=obrien@freebsd.org \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=snowwolf@one2one-networks.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).