Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/4] Cleanups for MIPS registers (mostly FreeBSD-specific)
Date: Wed, 12 Apr 2017 18:37:00 -0000	[thread overview]
Message-ID: <20170412183727.22483-1-jhb@FreeBSD.org> (raw)

Various small fixes to working with registers on FreeBSD/mips as well as
one OS-agnostic fix to handle unavailable registers more gracefully in
'info registers'.  Note that for the 32-bit info registers there isn't
room in the table layout for the full "<unavailable>" string, so a
truncated string "<unavail" is output instead.  I originally tried to
use "<unavail>" but it is one character too wide for 32-bit (8 hex
characters per register).

John Baldwin (4):
  Cleanups to FreeBSD/mips native register operations.
  Use mips_regnum instead of constants for FreeBSD/mips register
    operations.
  Consistently use fprintf_filtered when displaying MIPS registers.
  Don't throw an error in 'info registers' for unavailable MIPS GP
    registers.

 gdb/ChangeLog        | 28 ++++++++++++++++++++++++++++
 gdb/mips-fbsd-nat.c  | 26 ++++++++++++++------------
 gdb/mips-fbsd-tdep.c | 29 ++++++++++++++++-------------
 gdb/mips-tdep.c      | 12 +++++++++---
 4 files changed, 67 insertions(+), 28 deletions(-)

-- 
2.11.0


             reply	other threads:[~2017-04-12 18:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 18:37 John Baldwin [this message]
2017-04-12 18:37 ` [PATCH 1/4] Cleanups to FreeBSD/mips native register operations John Baldwin
2017-04-13 15:48   ` Luis Machado
2017-04-14 18:02     ` John Baldwin
2017-04-12 18:37 ` [PATCH 2/4] Use mips_regnum instead of constants for FreeBSD/mips " John Baldwin
2017-04-13 16:31   ` Luis Machado
2017-04-12 18:37 ` [PATCH 3/4] Consistently use fprintf_filtered when displaying MIPS registers John Baldwin
2017-04-13 16:29   ` Luis Machado
2017-04-27 16:05     ` Pedro Alves
2017-04-28 16:52       ` John Baldwin
2017-04-12 18:45 ` [PATCH 4/4] Don't throw an error in 'info registers' for unavailable MIPS GP registers John Baldwin
2017-04-13 16:37   ` Luis Machado
2017-04-14 18:02     ` John Baldwin
2017-04-15 16:02       ` Maciej W. Rozycki
2017-04-15 17:36         ` John Baldwin
2017-04-15 22:07           ` Maciej W. Rozycki
2017-04-17 18:27             ` John Baldwin
2017-04-18 21:33               ` Maciej W. Rozycki
2017-04-18 22:19                 ` John Baldwin
2017-04-25 21:02                   ` John Baldwin
2017-04-27  0:49                   ` Maciej W. Rozycki
2017-04-27 15:50                 ` Pedro Alves
2017-04-27 19:38                   ` Maciej W. Rozycki
2017-04-28 13:51                     ` Pedro Alves
2017-04-28 16:52                       ` John Baldwin
2017-05-05 19:51                         ` John Baldwin
2017-05-05 20:08                           ` Maciej W. Rozycki
2017-06-12 18:47                             ` John Baldwin
2017-06-15 23:50                               ` Maciej W. Rozycki
2017-06-16 16:17                                 ` John Baldwin

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=20170412183727.22483-1-jhb@FreeBSD.org \
    --to=jhb@freebsd.org \
    --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