public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Lancelot SIX <lsix@lancelotsix.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/7] Rewrite gdb_bfd_openr_iovec to be type-safe
Date: Mon, 18 Sep 2023 13:34:18 +0100	[thread overview]
Message-ID: <20230918123418.ddskjvzffqvfhisl@octopus> (raw)
In-Reply-To: <20230824-gdb-bfd-vec-v1-0-850e4e907ed1@adacore.com>

Hi Tom,

I have sent a couple of remarks on patch 1 & patch 6.  I quickly went
through the other patches of the series and did not notice any issue.

Best,
Lancelot.

On Thu, Aug 24, 2023 at 11:12:17AM -0600, Tom Tromey via Gdb-patches wrote:
> This series rewrites gdb_bfd_openr_iovec to be type-safe.
> 
> Note that I can't really test the solib-rocm.c changes, this was done
> as a best effort.
> 
> Regression tested on x86-64 Fedora 36.
> 
> ---
> Tom Tromey (7):
>       Introduce type-safe variant of gdb_bfd_openr_iovec
>       Small constructor change to target_buffer
>       Convert mem_bfd_iovec to new type-safe gdb_bfd_openr_iovec
>       Convert target fileio to new type-safe gdb_bfd_openr_iovec
>       Convert minidebug to new type-safe gdb_bfd_openr_iovec
>       Convert solib-rocm to new type-safe gdb_bfd_openr_iovec
>       Remove old gdb_bfd_openr_iovec
> 
>  gdb/gdb_bfd.c    | 211 +++++++++++++++++++++++++++----------------------------
>  gdb/gdb_bfd.h    |  43 ++++++++----
>  gdb/minidebug.c  |  98 +++++++++++---------------
>  gdb/solib-rocm.c |  39 +++-------
>  4 files changed, 182 insertions(+), 209 deletions(-)
> ---
> base-commit: 1f08d324601ef7fd4cce3cff8f8db4a774791828
> change-id: 20230824-gdb-bfd-vec-ba7f6c1139bb
> 
> Best regards,
> -- 
> Tom Tromey <tromey@adacore.com>
> 

      parent reply	other threads:[~2023-09-18 12:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 17:12 Tom Tromey
2023-08-24 17:12 ` [PATCH 1/7] Introduce type-safe variant of gdb_bfd_openr_iovec Tom Tromey
2023-09-18 10:29   ` Lancelot SIX
2023-09-18 14:44     ` Tom Tromey
2023-08-24 17:12 ` [PATCH 2/7] Small constructor change to target_buffer Tom Tromey
2023-08-24 17:12 ` [PATCH 3/7] Convert mem_bfd_iovec to new type-safe gdb_bfd_openr_iovec Tom Tromey
2023-08-24 17:12 ` [PATCH 4/7] Convert target fileio " Tom Tromey
2023-08-24 17:12 ` [PATCH 5/7] Convert minidebug " Tom Tromey
2023-08-24 17:12 ` [PATCH 6/7] Convert solib-rocm " Tom Tromey
2023-09-18  9:41   ` Lancelot SIX
2023-09-18 14:49     ` Tom Tromey
2023-08-24 17:12 ` [PATCH 7/7] Remove old gdb_bfd_openr_iovec Tom Tromey
2023-09-18 12:34 ` Lancelot SIX [this message]

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=20230918123418.ddskjvzffqvfhisl@octopus \
    --to=lsix@lancelotsix.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).