Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Wed, 20 Mar 2002 15:19:00 -0000	[thread overview]
Message-ID: <20020320181856.A17115@nevyn.them.org> (raw)
In-Reply-To: <B8BB8780.7EBD%jingham@apple.com>

On Mon, Mar 18, 2002 at 12:01:04PM -0800, Jim Ingham wrote:
> In fact, since the ABI's are all added in _initialize functions, it would be
> even simpler just to fix the size of the array.  When somebody adds the
> "last straw" ABI to gdb, we can just spit out a message saying increase this
> number, and that developer can do so and recompile.  This is safe since I
> don't think we really have the intention that we are adding these things
> dynamically at runtime...

Definitely not as GDB stands, and I don't see a point.  This bit is
fine.

> > 
> >>             const char *name = SYMBOL_NAME (&objfile->msymbols[i]);
> >>             if (name[0] == '_' && name[1] == 'Z')
> >>               {
> >> +               if (cp_abi_is_auto_p ())
> >>                   switch_to_cp_abi ("gnu-v3");
> >>                 break;
> >>               }
> > 
> > This bit, of course, is great :)
> 
> Way too much work to get there, however.  Another point that is unclear to
> me, should this instead be:
> 
>                if (cp_abi_is_auto_p ())
>                    set_cp_abi_as_auto_default ("gnu_v3");
>                  break;
> 
> I would have to change set_... to take the name rather than a structure, and
> look it up (and add a lookup_cp_abi to be nice).  But it fits with the set
> lang more.  OTOH, I have already spent more time on this that it deserves by
> a long shot, so...

I suppose that this would be best; if we set cp-abi to auto it should
remain v3.

> I am including a new patch, with just the cp-abi.c bits to keep it smaller,
> and I didn't edit this one to change the indentation goofs that the mailer
> added (I did with the last patch, oh fun...).

Mangled patches are a pain to read.  If you can't get a mailer that
won't mangle it inline, can you at least get them attached in some
vaguely sane MIME-ish way?

Other than set_cp_abi_as_auto_default, my only remaining nits are
grammatical again:
!       error ("Too many CP ABI's, please increase CP_ABI_MAX in cp-abi.c");

internal_error(), and "C++ ABIs".

+   if (!switch_to_cp_abi (args))
+     error ("Could not find ABI: \"%s\" in ABI list\n", args);

"Could not find \"%s\" in ABI list" (and no \n)

+   ui_out_text (uiout, "The currently selected C++ abi is: ");

"ABI", not "abi".

And show_cp_abis should probably mention "auto".

With the above changes it should be OK, although I would like to see
it.  Thanks for following this through.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-03-20 23:19 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 [this message]
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
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=20020320181856.A17115@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