Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Paul Gilliam <pgilliam@us.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]*3  Re: [RFC] "info powerpc"
Date: Fri, 16 Sep 2005 13:56:00 -0000	[thread overview]
Message-ID: <20050916135602.GA3473@nevyn.them.org> (raw)
In-Reply-To: <200509141710.39794.pgilliam@us.ibm.com>

On Wed, Sep 14, 2005 at 05:10:39PM -0700, Paul Gilliam wrote:
> My least favorite is the third one.  While it's a clean fix to the
> problem, it slams the door on any future 'info powerpc' sub-commands. 
> It also requires a fix so that prefix commands without any
> sub-commands can be depreciated.  Of course, we could just get rid of
> the "info powerpc" command without depreciating it for a while
> first....

If you just remove it, you don't slam the door on anything.  We can add
it back the moment we've got a use for it.

We have a common routine for printing vector registers; I would prefer
using "info vector" instead of extending "info powerpc".

How on earth did these tests get added to the FSF sources without the
command they're testing?  Ah-hah, they didn't.  This is why repository
history and ChangeLogs are so useful.

2002-08-20  Elena Zannoni  <ezannoni@redhat.com>

        * rs6000-tdep.c (altivec_register_p): Delete.
        (rs6000_do_altivec_registers): Delete.
        (rs6000_altivec_registers_info): Delete.
        (rs6000_do_registers_info): Delete.
        (_initialize_rs6000_tdep): Remove command 'info powerpc altivec'.
        (rs6000_gdbarch_init): Remove setting of do_registers_info.

Here:
    http://sourceware.org/ml/gdb-patches/2002-08/msg00597.html

It was Elena's goal to get rid of 'info powerpc altivec'; she just
didn't update the testsuite, apparently.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  parent reply	other threads:[~2005-09-16 13:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 23:32 Paul Gilliam
2005-09-15  0:11 ` [PATCH]*3 " Paul Gilliam
2005-09-15  3:34   ` Eli Zaretskii
2005-09-15 19:06     ` [DOC PATCH] " Paul Gilliam
2005-09-16 10:26       ` Eli Zaretskii
2005-09-15 19:18   ` Mark Kettenis
2005-09-16 13:56   ` Daniel Jacobowitz [this message]
2005-09-16 17:45     ` Kevin Buettner
2005-09-16 18:51     ` Paul Gilliam
2005-09-16 19:40       ` Mark Kettenis
2005-09-16 19:47       ` Kevin Buettner
2005-09-19 17:50         ` [commit] "get rid of info powerpc" Paul Gilliam
2005-09-19 18:09           ` Daniel Jacobowitz
2005-09-20 20:05             ` Paul Gilliam

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=20050916135602.GA3473@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=pgilliam@us.ibm.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