From: "Machado, Luis" <Luis.Machado@amd.com>
To: Guinevere Larsen <guinevere@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [testsuite] Log gdb_do_cache misses only, not hits
Date: Fri, 19 Jun 2026 13:34:14 +0000 [thread overview]
Message-ID: <SJ5PPF816B8837532E03B56A7755AC112DC9DE22@SJ5PPF816B88375.namprd12.prod.outlook.com> (raw)
In-Reply-To: <6cbaf2d8-0d2e-45bd-b929-8570316ef755@redhat.com>
Thanks! I'll push this soon-ish.
________________________________________
From: Guinevere Larsen <guinevere@redhat.com>
Sent: Friday, 19 June 2026 14:16
To: Machado, Luis; gdb-patches@sourceware.org
Subject: Re: [PATCH] [testsuite] Log gdb_do_cache misses only, not hits
Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
On 6/19/26 5:16 AM, Luis Machado wrote:
> The verbose -log in gdb_do_cache fired unconditionally on every call,
> including cache hits. With many tests calling gdb_caching_procs like
> get_compiler_info_1 per compilation, this produced dozens of repeated
> identical lines per test file in the log, like so:
>
> gdb_do_cache: get_compiler_info_1 ( c )
> gdb_do_cache: get_compiler_info_1 ( c )
> gdb_do_cache: get_compiler_info_1 ( c )
> gdb_do_cache: get_compiler_info_1 ( c )
> gdb_do_cache: get_compiler_info_1 ( c )
> gdb_do_cache: get_compiler_info_1 ( c )
> gdb_do_cache: get_compiler_info_1 ( c )
> gdb_do_cache: get_compiler_info_1 ( c )
>
> Move the log to just before actual computation, after both the
> in-memory and on-disk cache checks. This helps keep the logs clean.
Yeah, this looks like a good idea, and would definitely reduce the noise
at the top of the log
Reviewed-By: Guinevere Larsen <guinevere@redhat.com>
> ---
> gdb/testsuite/lib/cache.exp | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/gdb/testsuite/lib/cache.exp b/gdb/testsuite/lib/cache.exp
> index 71688ee373e..1ba8c881716 100644
> --- a/gdb/testsuite/lib/cache.exp
> +++ b/gdb/testsuite/lib/cache.exp
> @@ -103,8 +103,6 @@ proc gdb_do_cache {name args} {
> global gdb_data_cache objdir
> global GDB_PARALLEL
>
> - verbose -log "gdb_do_cache: $name ( $args )"
> -
> # Normally, if we have a cached value, we skip computation and return
> # the cached value. If set to 1, instead don't skip computation and
> # verify against the cached value.
> @@ -195,6 +193,7 @@ proc gdb_do_cache {name args} {
> set old_gdb_nested_caching_proc_calls $::gdb_nested_caching_proc_calls
> set ::gdb_nested_caching_proc_calls {}
>
> + verbose -log "gdb_do_cache: $name ( $args )"
> set real_name gdb_real__$name
> set gdb_data_cache(${cache_name},value) [gdb_do_cache_wrap $real_name {*}$args]
> set gdb_data_cache(${cache_name},exit) $::gdb_exit_called
--
Cheers,
Guinevere Larsen
it/its
she/her (deprecated)
prev parent reply other threads:[~2026-06-19 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 8:16 Luis Machado
2026-06-19 13:16 ` Guinevere Larsen
2026-06-19 13:34 ` Machado, Luis [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=SJ5PPF816B8837532E03B56A7755AC112DC9DE22@SJ5PPF816B88375.namprd12.prod.outlook.com \
--to=luis.machado@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.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