From: Joe Buck <Joe.Buck@synopsys.com>
To: mark@codesourcery.com (Mark Mitchell)
Cc: obrien@freebsd.org (obrien@FreeBSD.org),
gcc@gcc.gnu.org (gcc@gcc.gnu.org),
pfeifer@dbai.tuwien.ac.at (Gerald Pfeifer)
Subject: Re: C++ ABI Issues
Date: Mon, 23 Sep 2002 10:01:00 -0000 [thread overview]
Message-ID: <200209231651.JAA20845@atrus.synopsys.com> (raw)
In-Reply-To: <22390000.1032717504@warlock.codesourcery.com> from "Mark Mitchell" at Sep 22, 2002 10:58:24 AM
> > We really need to know what the SC decided about this issue for 3.3?
> > FreeBSD would really like to see the C++ ABI bugs fixed in 3.3 (even if
> > selectable via a command line switch).
>
> The SC didn't decide anything, nor is it even debating the issue. We
> can raise it, if you like, but the consensus on the lists seemed to be
> to leave things alone for a while.
To be technical, a number of SC members discussed the issue, on this list,
so you can find the discussion in the archives. There hasn't been any
separate discussion on the private list.
The consensus, at least as I interpreted it, was to leave 3.2 compatible
with 3.3 by default, add warning code to detect cases that would be
handled differently, and have some option to generate "correct" code for
the known bad cases. The details were not completely fleshed out.
> Nor has anybody yet implemented the fixes. Until that happens, there's
> little that we can do.
>
> I plan to implement the fixes, soon, but probably not before 3.3 branches.
next prev parent reply other threads:[~2002-09-23 16:51 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
2002-09-22 2:49 ` David O'Brien
2002-09-22 11:15 ` Mark Mitchell
2002-09-23 10:01 ` Joe Buck [this message]
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=200209231651.JAA20845@atrus.synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=obrien@freebsd.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).