Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/4] Remove many uses of field_fmt
Date: Tue, 02 Jul 2019 15:36:00 -0000	[thread overview]
Message-ID: <20190702153602.27637-1-tromey@adacore.com> (raw)

Here's v2 of the series to remove many uses of field_fmt.

Compared to v1, this:

* Fixes the phex bug pointed out by Simon,
* Converts more uses of 0x%s to use hex_string_custom,
* Changes how field_unsigned is implemented, and
* Removes a FIXME from mi-out.c

Regression tested on x86-64 Fedora 29.

Tom



             reply	other threads:[~2019-07-02 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-02 15:36 Tom Tromey [this message]
2019-07-02 15:36 ` [PATCH v2 1/4] Use field_core_addr in more places Tom Tromey
2019-07-02 15:36 ` [PATCH v2 3/4] Introduce field_unsigned Tom Tromey
2019-07-02 15:36 ` [PATCH v2 2/4] Use field_string in more places Tom Tromey
2019-07-02 15:53   ` Andrew Burgess
2019-07-09 15:21     ` Tom Tromey
2019-07-02 15:42 ` [PATCH v2 4/4] Fix a FIXME in mi-out.c Tom Tromey
2019-07-02 15:59 ` [PATCH v2 0/4] Remove many uses of field_fmt Simon Marchi
2019-07-02 16:12   ` 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=20190702153602.27637-1-tromey@adacore.com \
    --to=tromey@adacore.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