public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 0/7] Small cleanups in array_operation::evaluate
Date: Tue, 29 Aug 2023 08:58:10 -0700	[thread overview]
Message-ID: <5ccfdd16-b01a-cb46-76ff-2995823c2520@FreeBSD.org> (raw)
In-Reply-To: <20230829-cleanup-array-op-v2-0-3035458b0443@adacore.com>

On 8/29/23 8:34 AM, Tom Tromey wrote:
> While working on another, larger, series, I found a few small cleanups
> to do in array_operation::evaluate.  I've made each one a separate
> patch to try to keep each one reasonably obvious.
> 
> Regression tested on x86-64 Fedora 36.
> 
> ---
> Changes in v2:
> - Added two more cleanup patches
> - Link to v1: https://inbox.sourceware.org/gdb-patches/20230828-cleanup-array-op-v1-0-12ca00f20917@adacore.com
> 
> ---
> Tom Tromey (7):
>        Use gdb::array_view for value_array
>        Declare 'tem' in loop header in array_operation::evaluate
>        Hoist array bounds check in array_operation::evaluate
>        Remove redundant variable from array_operation::evaluate
>        Remove another redundant variable from array_operation::evaluate
>        Remove "highbound" parameter from value_array
>        More renames in array_operation::evaluate
> 
>   gdb/eval.c      | 34 +++++++++++++---------------------
>   gdb/rust-lang.c |  2 +-
>   gdb/valops.c    | 21 ++++++++-------------
>   gdb/value.h     |  4 ++--
>   4 files changed, 24 insertions(+), 37 deletions(-)
> ---
> base-commit: aa7b36b832a1475fad2f184e0b4b58fb2f12241f
> change-id: 20230828-cleanup-array-op-49e3af3bd743
> 
> Best regards,

The new patches (6 and 7) look good to me.

Reviewed-by: John Baldwin <jhb@FreeBSD.org>

-- 
John Baldwin


      parent reply	other threads:[~2023-08-29 15:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 15:34 Tom Tromey
2023-08-29 15:34 ` [PATCH v2 1/7] Use gdb::array_view for value_array Tom Tromey
2023-08-29 15:34 ` [PATCH v2 2/7] Declare 'tem' in loop header in array_operation::evaluate Tom Tromey
2023-08-29 15:34 ` [PATCH v2 3/7] Hoist array bounds check " Tom Tromey
2023-08-29 15:34 ` [PATCH v2 4/7] Remove redundant variable from array_operation::evaluate Tom Tromey
2023-08-29 15:34 ` [PATCH v2 5/7] Remove another " Tom Tromey
2023-08-29 15:34 ` [PATCH v2 6/7] Remove "highbound" parameter from value_array Tom Tromey
2023-08-29 17:53   ` Simon Marchi
2023-08-29 18:01     ` Tom Tromey
2023-08-29 15:34 ` [PATCH v2 7/7] More renames in array_operation::evaluate Tom Tromey
2023-08-29 15:58 ` John Baldwin [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=5ccfdd16-b01a-cb46-76ff-2995823c2520@FreeBSD.org \
    --to=jhb@freebsd.org \
    --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).