From: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: Lancelot SIX <lsix@lancelotsix.com>
Subject: [PATCH v3 0/2] Have ptype support hex display of offsets and sizes
Date: Fri, 23 Apr 2021 23:28:36 +0100 [thread overview]
Message-ID: <20210423222838.41119-1-lsix@lancelotsix.com> (raw)
Hi,
Here is a updated version of the series. The first patch is unchanged
from previous submission. Documentation and code style have been
updated in the second patch of the series according to reviews.
The second patch has also been updated to handle conflicts in
gdb/testsuite/gdb.base/ptype-offsets.exp after the following patch
landed in master: https://sourceware.org/pipermail/gdb-patches/2021-April/178016.html.
Lancelot.
Lancelot SIX (2):
typeprint.h: reorder struct declaration
[PR gdb/22640] ptype: add option to use hexadecimal notation
gdb/NEWS | 12 +
gdb/c-typeprint.c | 8 +-
gdb/doc/gdb.texinfo | 113 +++--
gdb/rust-lang.c | 2 +-
gdb/testsuite/gdb.base/ptype-offsets.exp | 562 ++++++++++++++---------
gdb/testsuite/gdb.rust/simple.exp | 10 +-
gdb/testsuite/gdb.rust/union.exp | 10 +-
gdb/typeprint.c | 83 +++-
gdb/typeprint.h | 69 +--
9 files changed, 544 insertions(+), 325 deletions(-)
--
2.31.1
next reply other threads:[~2021-04-23 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 22:28 Lancelot SIX via Gdb-patches [this message]
2021-04-23 22:28 ` [PATCH v3 1/2] typeprint.h: reorder struct declaration Lancelot SIX via Gdb-patches
2021-04-23 22:28 ` [PATCH v3 2/2] [PR gdb/22640] ptype: add option to use hexadecimal notation Lancelot SIX via Gdb-patches
2021-04-24 6:15 ` Eli Zaretskii via Gdb-patches
2021-04-24 15:32 ` [PATCH v3 0/2] Have ptype support hex display of offsets and sizes Tom Tromey
2021-04-25 17:12 ` Lancelot SIX via Gdb-patches
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=20210423222838.41119-1-lsix@lancelotsix.com \
--to=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.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