From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>
Subject: Re: [RFC 1/2] [gdb/testsuite] Modernize gdb.base/huge.exp
Date: Thu, 14 Sep 2023 08:20:04 -0600 [thread overview]
Message-ID: <87v8cchm5n.fsf@tromey.com> (raw)
In-Reply-To: <20230904054148.24552-1-tdevries@suse.de> (Tom de Vries via Gdb-patches's message of "Mon, 4 Sep 2023 07:41:47 +0200")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> Rewrite test-case gdb.base/huge.exp:
Tom> - use build_executable rather than gdb_compile,
Tom> - use save_vars,
Tom> - factor out hardcoded loop limits min and max,
Tom> - handle compilation failure using require, and
Tom> - avoid using . in regexp to match $, {} and <>.
Seems fine to me.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
prev parent reply other threads:[~2023-09-14 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 5:41 Tom de Vries
2023-09-04 5:41 ` [RFC 2/2] [gdb/exp] Clean up asap in value_print_array_elements Tom de Vries
2023-09-14 14:51 ` Tom Tromey
2023-09-14 14:20 ` Tom Tromey [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=87v8cchm5n.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).