From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Ingham <jingham@apple.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: add set cp-abi command
Date: Tue, 09 Apr 2002 17:54:00 -0000 [thread overview]
Message-ID: <20020409205402.A18266@nevyn.them.org> (raw)
In-Reply-To: <B80D7663-4C19-11D6-B08E-000393540DDC@apple.com>
On Tue, Apr 09, 2002 at 05:27:19PM -0700, Jim Ingham wrote:
> I got distracted from this for a little while... Here is a final
> version with something in the texi file as well.
>
> ChangeLog:
>
> 2002-03-12 James Ingham <jingham@apple.com>
>
> * cp-abi.c (set_cp_abi_cmd, show_cp_abi_cmd,): New functions,
> allow you to set & show cplus abi's in case gdb gets it wrong.
> (set_cp_abi_as_auto_default): New function, set the "auto" abi
> to be this abi.
> (is_cp_abi_auto_p): New function, say whether the current abi
> is the default or not.
> (_initialize_cp_abi): Define the cp-abi switching commands.
> * cp-abi.h: declare the new functions.
> * minsyms.c (install_minimal_symbols): don't switch the cp_abi
> unless the current abi is auto.
> * gnu-v2-abi.c (_initialize_gnu_v2_abi): don't switch to gnu-v2,
> but set it as the auto_default instead.
>
> Okay to check in?
I think we may have misplaced a revision here...
! internal_error (__FILE__, __LINE__,
! "Too many CP ABIs, please increase CP_ABI_MAX in cp-abi.c");
C++ ABIs.
! char *longname; /* These two can't be const, because I need to */
! char *doc; /* change the name for the auto abi. */
GNU comment formatting. Something like:
/* These two are not constant because they are changed at runtime
for the auto ABI. */
char *longname;
char *doc;
More importantly:
! if (cp_abi_is_auto_p ())
! set_cp_abi_as_auto_default ("gnu-v3");
Shouldn't you lose the cp_abi_is_auto_p () check there?
If you agree with all three, feel free to update them and check it in.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-04-10 0:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 10:56 Jim Ingham
2002-03-13 12:11 ` Daniel Jacobowitz
2002-03-14 13:14 ` Jim Ingham
2002-03-14 13:26 ` Daniel Jacobowitz
2002-03-15 15:53 ` Jim Ingham
2002-03-15 19:41 ` Daniel Jacobowitz
2002-03-18 12:01 ` Jim Ingham
2002-03-20 15:19 ` Daniel Jacobowitz
2002-03-20 19:02 ` Jim Ingham
2002-03-22 10:34 ` Daniel Jacobowitz
2002-03-22 11:04 ` Andrew Cagney
2002-03-22 11:09 ` Daniel Jacobowitz
2002-03-22 11:29 ` Jim Ingham
2002-04-09 17:27 ` Jim Ingham
2002-04-09 17:54 ` Daniel Jacobowitz [this message]
2002-04-10 11:10 ` Jim Ingham
2002-04-10 11:58 ` Daniel Jacobowitz
2002-04-09 22:33 ` Eli Zaretskii
2002-04-10 11:14 ` Jim Ingham
2002-04-11 12:25 ` Eli Zaretskii
2002-03-15 17:11 ` Jim Ingham
2002-03-13 12:11 ` Eli Zaretskii
2002-03-14 15:29 ` Andrew Cagney
2002-03-15 10:33 ` Jim Ingham
2002-03-15 17:29 ` 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=20020409205402.A18266@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jingham@apple.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