Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [SH] regs command
Date: Fri, 10 Aug 2012 09:22:00 -0000	[thread overview]
Message-ID: <87lihnrtj2.fsf@schwinge.name> (raw)
In-Reply-To: <87wr3kl3b9.fsf@schwinge.name>

[-- Attachment #1: Type: text/plain, Size: 3428 bytes --]

Hi!

On Wed, 06 Jun 2012 20:10:02 +0200, I wrote:
> On Wed, 16 May 2012 18:31:30 +0200, I wrote:
> > On Wed, 16 May 2012 07:26:33 -0700, Joel Brobecker <brobecker@adacore.com> wrote:
> > > > I therefore propose to remove sh_show_regs_command et al. from sh-tdep.c.
> > > > If nobody objects, can it just go silently, or should invoking it then
> > > > cause an error message, like »Please use the »info all-registers« command
> > > > instead of »regs«.«?
> > > 
> > > Make it an alias of "info reg" or "info all-registers", and make
> > > the alias deprecated, so that users get a warning when they use it?
> 
> Below is the patch that I finally committed.
> 
> > > We can make that command deprecated for 7.5, and then remove it
> > > from HEAD after 7.5 is branched, in a few weeks.
> 
> I'll prepare a patch for that.

... and here it is.  OK to commit?

gdb/
	* NEWS: Document the removal of SH's 'regs' command.
	* sh-tdep.c (_initialize_sh_tdep): Remove the deprecated 'regs'
	command.

gdb/doc/
	* gdb.texinfo: Document the removal of SH's 'regs' command.

Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.538
diff -u -p -r1.538 NEWS
--- NEWS	6 Aug 2012 17:13:26 -0000	1.538
+++ NEWS	10 Aug 2012 09:15:04 -0000
@@ -20,6 +20,12 @@
 maint info bfds
   List the BFDs known to GDB.
 
+* Removed commands
+
+  ** For the Renesas Super-H architecture, the "regs" command has been removed
+     (has been deprecated in GDB 7.5), and "info all-registers" should be used
+     instead.
+
 *** Changes in GDB 7.5
 
 * GDB now supports x32 ABI.  Visit <http://sites.google.com/site/x32abi/>
Index: sh-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/sh-tdep.c,v
retrieving revision 1.246
diff -u -p -r1.246 sh-tdep.c
--- sh-tdep.c	22 Jul 2012 16:52:41 -0000	1.246
+++ sh-tdep.c	10 Aug 2012 09:15:04 -0000
@@ -2416,16 +2418,8 @@ extern initialize_file_ftype _initialize
 void
 _initialize_sh_tdep (void)
 {
-  struct cmd_list_element *c;
-
   gdbarch_register (bfd_arch_sh, sh_gdbarch_init, NULL);
 
-  /* We can't use an alias here because 'info registers' has not yet been
-     registered.  */
-  c = add_com ("regs", class_vars, all_registers_info,
-               _("Print all registers"));
-  deprecate_cmd (c, "info all-registers");
-
   add_prefix_cmd ("sh", no_class, set_sh_command, "SH specific commands.",
                   &setshcmdlist, "set sh ", 0, &setlist);
   add_prefix_cmd ("sh", no_class, show_sh_command, "SH specific commands.",
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.994
diff -u -p -r1.994 gdb.texinfo
--- doc/gdb.texinfo	2 Aug 2012 09:27:15 -0000	1.994
+++ doc/gdb.texinfo	10 Aug 2012 09:15:05 -0000
@@ -20471,13 +20471,6 @@ For the Renesas Super-H processor, @valu
 commands:
 
 @table @code
-@item regs
-@kindex regs@r{, Super-H}
-This command is deprecated, and @code{info all-registers} should be
-used instead.
-
-Show the values of all Super-H registers.
-
 @item set sh calling-convention @var{convention}
 @kindex set sh calling-convention
 Set the calling-convention used when calling functions from @value{GDBN}.


Grüße,
 Thomas

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2012-08-10  9:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 13:56 Thomas Schwinge
2012-05-16 14:26 ` Joel Brobecker
2012-05-16 16:32   ` Thomas Schwinge
2012-05-16 16:58     ` Joel Brobecker
2012-05-16 17:21       ` Thomas Schwinge
2012-05-16 18:47         ` Tom Tromey
2012-05-16 19:06           ` Joel Brobecker
2012-05-16 19:38             ` Maciej W. Rozycki
2012-05-17  0:59               ` Maciej W. Rozycki
2012-05-17 11:10                 ` Mark Kettenis
2012-05-17 11:23                   ` Maciej W. Rozycki
2012-05-17 12:38                     ` Joel Brobecker
2012-05-17 15:23                       ` Mark Kettenis
2012-05-17 15:45                         ` Joel Brobecker
2012-05-17 19:52                           ` Tom Tromey
2012-05-17 20:38                             ` Joel Brobecker
2012-05-18 12:23                               ` Maciej W. Rozycki
2012-05-18 12:39                                 ` Pedro Alves
2012-05-18 12:49                                   ` Joel Brobecker
2012-05-18 13:33                                     ` Pedro Alves
2012-05-18 13:47                                 ` Tom Tromey
2012-05-21 23:36                                   ` Maciej W. Rozycki
2012-05-24 18:05                                     ` Tom Tromey
2012-05-17 19:32         ` Kevin Buettner
2012-05-16 18:36       ` Tom Tromey
2012-05-16 18:36     ` Pedro Alves
2012-05-16 19:36     ` Eli Zaretskii
2012-06-06 18:10     ` Thomas Schwinge
2012-08-10  9:22       ` Thomas Schwinge [this message]
2012-08-10 16:20         ` Tom Tromey

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=87lihnrtj2.fsf@schwinge.name \
    --to=thomas@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    /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