From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 2/7] [gdbsupport] Add parameterless iterator_range constructor
Date: Thu, 23 Apr 2026 08:35:25 +0200 [thread overview]
Message-ID: <20260423063530.1074175-3-tdevries@suse.de> (raw)
In-Reply-To: <20260423063530.1074175-1-tdevries@suse.de>
I noticed that there's no convenient way to create an empty range in
iterator_range. Add this.
---
gdb/unittests/iterator-range-selftests.c | 2 +-
gdbsupport/iterator-range.h | 5 +++++
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/gdb/unittests/iterator-range-selftests.c b/gdb/unittests/iterator-range-selftests.c
index a05531d95e0..7c0f7f57484 100644
--- a/gdb/unittests/iterator-range-selftests.c
+++ b/gdb/unittests/iterator-range-selftests.c
@@ -67,7 +67,7 @@ test_iterator_range ()
{
/* Empty range. */
- auto r3 = int_array_iterator_range (end, end);
+ auto r3 = int_array_iterator_range ();
test_iterator_range_1 (r3, nullptr, 0, end, end);
}
diff --git a/gdbsupport/iterator-range.h b/gdbsupport/iterator-range.h
index 42185546f5a..98be1e67152 100644
--- a/gdbsupport/iterator-range.h
+++ b/gdbsupport/iterator-range.h
@@ -27,6 +27,11 @@ struct iterator_range
{
using iterator = IteratorType;
+ /* Create an empty range. */
+ explicit iterator_range ()
+ : iterator_range (IteratorType {}, IteratorType {})
+ {}
+
/* Create an iterator_range using BEGIN as the begin iterator.
Assume that the end iterator can be default-constructed. */
--
2.51.0
next prev parent reply other threads:[~2026-04-23 6:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 6:35 [PATCH 0/7] [gdb] Add superblocks range loops Tom de Vries
2026-04-23 6:35 ` [PATCH 1/7] [gdb] Use block::function_block Tom de Vries
2026-04-23 14:33 ` Tom Tromey
2026-04-24 12:19 ` Tom de Vries
2026-04-23 6:35 ` Tom de Vries [this message]
2026-04-23 14:34 ` [PATCH 2/7] [gdbsupport] Add parameterless iterator_range constructor Tom Tromey
2026-04-24 12:20 ` Tom de Vries
2026-04-23 6:35 ` [PATCH 3/7] [gdbsupport] Factor out base_next_iterator Tom de Vries
[not found] ` <87340kpbwx.fsf@tromey.com>
2026-04-30 4:49 ` Tom de Vries
2026-05-01 12:54 ` Tom de Vries
2026-05-01 13:00 ` Tom de Vries
2026-04-30 16:24 ` Simon Marchi
2026-04-30 19:09 ` Simon Marchi
2026-05-01 12:57 ` Tom Tromey
2026-05-01 13:20 ` Tom de Vries
2026-05-01 13:15 ` Tom de Vries
2026-04-23 6:35 ` [PATCH 4/7] [gdb] Add block::superblocks Tom de Vries
2026-04-27 11:11 ` Jan Vrany
2026-05-01 13:06 ` Tom de Vries
2026-04-30 16:24 ` Simon Marchi
2026-05-01 13:19 ` Tom de Vries
2026-04-23 6:35 ` [PATCH 5/7] [gdb] Use block::super_blocks Tom de Vries
2026-04-24 16:27 ` Tom Tromey
2026-04-24 21:24 ` Tom de Vries
2026-04-23 6:35 ` [PATCH 6/7] [gdb] Add block::function_blocks Tom de Vries
2026-04-23 6:35 ` [PATCH 7/7] [gdb] Use block::function_blocks Tom de Vries
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=20260423063530.1074175-3-tdevries@suse.de \
--to=tdevries@suse.de \
--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