From: David Edelsohn <dje@watson.ibm.com>
To: Matt Austern <austern@apple.com>
Cc: gcc@gcc.gnu.org
Subject: Re: 3.1/3.2 C++ ABI change
Date: Mon, 07 Oct 2002 16:37:00 -0000 [thread overview]
Message-ID: <200210072110.RAA26766@makai.watson.ibm.com> (raw)
In-Reply-To: Message from Matt Austern <austern@apple.com> of "Mon, 07 Oct 2002 14:07:45 PDT." <D34692B2-DA38-11D6-AC60-00039390D9E0@apple.com>
>>>>> Matt Austern writes:
Matt> (1) Was it the intention behind the ABI compatibility switch that it
Matt> should cover this vtable change?
The ABI compatibility switch is suppose to allow a choice among
multiple ABI changes. The current choices are 3.2 or current. GCC 3.1
was declared no longer supported. If you want to add another option to
the switch to handle GCC 3.1, it is up to the maintainer to decide whether
to accept and support that into the future.
Theoretically the "switch" can handle the vtable change, but the
current implementation does not have an option for GCC 3.1 compatibility.
David
next prev parent reply other threads:[~2002-10-07 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 16:11 Matt Austern
2002-10-07 16:37 ` David Edelsohn [this message]
2002-10-08 11:57 ` Mark Mitchell
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=200210072110.RAA26766@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=austern@apple.com \
--cc=gcc@gcc.gnu.org \
/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).