From: Eli Zaretskii <eliz@is.elta.co.il>
To: Jim Blandy <jimb@zwingli.cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Revised C++ ABI abstraction patches
Date: Thu, 15 Mar 2001 03:15:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010315130900.7550A-100000@is> (raw)
In-Reply-To: <200103150951.EAA25684@zwingli.cygnus.com>
On Thu, 15 Mar 2001, Jim Blandy wrote:
> They're not fit to be applied yet, since we don't yet automatically
> detect whether the executable uses the V3 or V2 ABI.
If it's important for users to be able to support the new ABI, you could
add a command which tells GDB which ABI to expect, no?
> * cp-abi-gnu-v2.c (gnu_v2_destructor_prefix_p,
[...]
> (gnu-v3-abi.o): Add.
> (gnu-v2-abi.o): Add.
So what is it: cp-abi-gnu-v2 or gnu-v2-abi? I prefer the latter, and I
thought that was the conclusion of the earlier discussions about that.
next prev parent reply other threads:[~2001-03-15 3:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 1:50 Jim Blandy
2001-03-15 3:15 ` Eli Zaretskii [this message]
2001-03-15 6:21 ` Fernando Nasser
2001-03-15 6:46 ` Daniel Berlin
2001-03-15 10:40 ` Jim Blandy
2001-03-15 13:38 ` Andrew Cagney
2001-03-15 14:05 ` Jim Blandy
2001-03-16 23:28 ` Eli Zaretskii
2001-03-19 9:38 ` Jim Blandy
2001-03-19 11:58 ` Eli Zaretskii
2001-03-15 14:57 ` Andrew Cagney
2001-03-15 17:57 ` Jim Blandy
2001-03-15 18:10 ` Andrew Cagney
2001-03-15 19:12 ` Daniel Berlin
2001-03-15 19:56 ` Jim Blandy
2001-03-15 18:58 ` Daniel Berlin
2001-03-15 10:50 Michael Elizabeth Chastain
2001-03-15 11:04 ` Jim Blandy
2001-03-15 11:32 ` Michael Snyder
2001-03-15 11:35 ` J.T. Conklin
2001-03-15 12:36 ` Jim Blandy
2001-03-15 15:21 ` Stan Shebs
2001-03-15 17:54 ` Jim Blandy
2001-03-15 20:11 ` Andrew Cagney
2001-03-15 13:46 ` Andrew Cagney
2001-03-15 15:01 ` Daniel Berlin
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=Pine.SUN.3.91.1010315130900.7550A-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@zwingli.cygnus.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