diff options
author | Tom de Vries <tdevries@suse.de> | 2023-03-06 16:49:19 +0100 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2023-03-06 16:49:19 +0100 |
commit | 71f1ab80f1aabd70bce526635f84c7b849e8a0f4 (patch) | |
tree | be4ec728a4f9e2fc433a46fcc44310e8b9fb260c /binutils | |
parent | b50420fd058824ecc737709f49f87d622b0f3371 (diff) | |
download | binutils-71f1ab80f1aabd70bce526635f84c7b849e8a0f4.zip binutils-71f1ab80f1aabd70bce526635f84c7b849e8a0f4.tar.gz binutils-71f1ab80f1aabd70bce526635f84c7b849e8a0f4.tar.bz2 |
[gdb/testsuite] Allow args in gdb_caching_proc
Test-case gdb.base/morestack.exp contains:
...
require {have_compile_flag -fsplit-stack}
...
and I want to cache the result of have_compile_flag.
Currently gdb_caching_proc doesn't allow args, so I could add:
...
gdb_caching_proc have_compile_flag_fsplit_stack {
return [have_compile_flag -fsplit-stack]
}
...
and then use that proc instead, but I find this cumbersome and
maintenance-unfriendly.
Instead, allow args in a gdb_caching_proc, such that I can simply do:
...
-proc have_compile_flag { flag } {
+gdb_caching_proc have_compile_flag { flag } {
...
Note that gdb_caching_procs with args do not work with the
gdb.base/gdb-caching-procs.exp test-case, so those procs are skipped.
Tested on x86_64-linux.
Reviewed-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'binutils')
0 files changed, 0 insertions, 0 deletions