From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/5] Small cleanups in array_operation::evaluate
Date: Mon, 28 Aug 2023 13:59:30 -0600 [thread overview]
Message-ID: <20230828-cleanup-array-op-v1-0-12ca00f20917@adacore.com> (raw)
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.
---
Tom Tromey (5):
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
gdb/eval.c | 29 +++++++++++------------------
gdb/rust-lang.c | 2 +-
gdb/valops.c | 3 ++-
gdb/value.h | 2 +-
4 files changed, 15 insertions(+), 21 deletions(-)
---
base-commit: b8a175b415454df6a039ba0b5d2ff13c3c180275
change-id: 20230828-cleanup-array-op-49e3af3bd743
Best regards,
--
Tom Tromey <tromey@adacore.com>
next reply other threads:[~2023-08-28 19:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 19:59 Tom Tromey [this message]
2023-08-28 19:59 ` [PATCH 1/5] Use gdb::array_view for value_array Tom Tromey
2023-08-28 21:10 ` Simon Marchi
2023-08-29 15:13 ` Tom Tromey
2023-08-28 19:59 ` [PATCH 2/5] Declare 'tem' in loop header in array_operation::evaluate Tom Tromey
2023-08-28 19:59 ` [PATCH 3/5] Hoist array bounds check " Tom Tromey
2023-08-28 19:59 ` [PATCH 4/5] Remove redundant variable from array_operation::evaluate Tom Tromey
2023-08-28 19:59 ` [PATCH 5/5] Remove another " Tom Tromey
2023-08-28 21:12 ` [PATCH 0/5] Small cleanups in array_operation::evaluate John Baldwin
2023-08-29 15:35 ` 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=20230828-cleanup-array-op-v1-0-12ca00f20917@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).