From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
gdb-patches@sources.redhat.com
Subject: Re: [patch/testsuite/cp] local.exp: accommodate gcc abi 2
Date: Mon, 05 Jan 2004 16:05:00 -0000 [thread overview]
Message-ID: <20040105160537.GA8576@nevyn.them.org> (raw)
In-Reply-To: <3FF98A6B.3000704@gnu.org>
On Mon, Jan 05, 2004 at 11:01:47AM -0500, Andrew Cagney wrote:
> >This expands local.exp to accommodate gcc HEAD -gstabs+ with the new abi.
> >As with several other files, I just cloned the pattern for
> >gcc 3.3.2 -gstabs+ abi-1 and re-ordered the fields.
> >
>
> Michael, humor me :-)
>
> Is this "The New ABI" or a yet to be named but for the moment would be
> best refered to as "The New New ABI"?
>
> Several years ago GCC added what they should add a new ABI and so called
> it "The New ABI" (...). I believe its motivation and specification both
> at least in part originated with the IA-64. I thought "The New ABI"
> became known as "ABI 2"?
It's not a new ABI in the sense that you mean. It's a new ABI version
- gcc now has a command line switch for incompatible bug-fixes to the
existing ABI. The only change between -fabi-version=1 and
-fabi-version=2 that will affect GDB is probably this one, which moves
virtual destructors to another location in the vtable.
This is still the "Itanium C++ ABI". It's just a little closer to the
published document than it used to be :) I don't remember it being
called ABI 2 - if anything, it was called the v3 ABI, for GCC 3.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-05 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 1:45 Michael Elizabeth Chastain
2004-01-05 16:01 ` Andrew Cagney
2004-01-05 16:05 ` Daniel Jacobowitz [this message]
2004-01-05 20:27 Michael Elizabeth Chastain
2004-01-05 21:34 ` Andrew Cagney
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=20040105160537.GA8576@nevyn.them.org \
--to=drow@mvista.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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