From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: gdb-patches@sourceware.org
Cc: Jovan Dmitrovic <jovan.dmitrovic@htecgroup.com>,
Djordje Todorovic <Djordje.Todorovic@htecgroup.com>,
Milica Matic <milica.matic@htecgroup.com>,
"Maciej W. Rozycki" <macro@globalfoundries.com>
Subject: [PATCH 2/7] PowerPC/testsuite: Reduce feature tests in terms of `allow_target_tests'
Date: Thu, 23 Jul 2026 19:52:51 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2607222358210.14485@angie.orcam.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.2607220148540.14485@angie.orcam.me.uk>
From: Maciej W. Rozycki <macro@globalfoundries.com>
Reimplement `allow_altivec_tests', `allow_power_isa_3_1_tests', and
`allow_vsx_tests' in terms of `allow_target_tests', removing duplicate
code. No functional change.
Eventually it may make sense to migrate the resulting wrappers to
testsuite/gdb.arch/ so as to declutter generic test framework from
target-specific stuff.
---
gdb/testsuite/lib/gdb.exp | 163 +++++++++-------------------------------------
1 file changed, 35 insertions(+), 128 deletions(-)
gdb-powerpc-test-target-allow.diff
Index: binutils-gdb/gdb/testsuite/lib/gdb.exp
===================================================================
--- binutils-gdb.orig/gdb/testsuite/lib/gdb.exp
+++ binutils-gdb/gdb/testsuite/lib/gdb.exp
@@ -4333,8 +4333,6 @@ proc allow_target_tests { me feature mes
# 0 if it does not. Based on 'check_vmx_hw_available' from the GCC testsuite.
gdb_caching_proc allow_altivec_tests {} {
- global srcdir subdir gdb_prompt inferior_exited_re
-
set me "allow_altivec_tests"
# Some simulators are known to not support VMX instructions.
@@ -4350,110 +4348,47 @@ gdb_caching_proc allow_altivec_tests {}
# Make sure we have a compiler that understands altivec.
if {[test_compiler_info gcc*]} {
- set compile_flags "additional_flags=-maltivec"
+ set flags "-maltivec"
} elseif {[test_compiler_info xlc*]} {
- set compile_flags "additional_flags=-qaltivec"
+ set flags "-qaltivec"
} else {
verbose "Could not compile with altivec support, returning 0" 2
return 0
}
# Compile a test program containing VMX instructions.
- set src {
- int main() {
- #ifdef __MACH__
- asm volatile ("vor v0,v0,v0");
- #else
- asm volatile ("vor 0,0,0");
- #endif
- return 0;
- }
- }
- if {![gdb_simple_compile $me $src executable $compile_flags]} {
- return 0
- }
-
- # Compilation succeeded so now run it via gdb.
-
- gdb_exit
- gdb_start
- gdb_reinitialize_dir $srcdir/$subdir
- gdb_load "$obj"
- gdb_run_cmd
- gdb_expect {
- -re ".*Illegal instruction.*${gdb_prompt} $" {
- verbose -log "\n$me altivec hardware not detected"
- set allow_vmx_tests 0
- }
- -re ".*$inferior_exited_re normally.*${gdb_prompt} $" {
- verbose -log "\n$me: altivec hardware detected"
- set allow_vmx_tests 1
- }
- default {
- warning "\n$me: default case taken"
- set allow_vmx_tests 0
- }
- }
- gdb_exit
- remote_file build delete $obj
-
- verbose "$me: returning $allow_vmx_tests" 2
- return $allow_vmx_tests
+ return [allow_target_tests $me "altivec hardware" "Illegal instruction" \
+ {
+ int main() {
+ #ifdef __MACH__
+ asm volatile ("vor v0,v0,v0");
+ #else
+ asm volatile ("vor 0,0,0");
+ #endif
+ return 0;
+ }
+ } \
+ $flags]
}
# Run a test on the power target to see if it supports ISA 3.1 instructions
gdb_caching_proc allow_power_isa_3_1_tests {} {
- global srcdir subdir gdb_prompt inferior_exited_re
-
- set me "allow_power_isa_3_1_tests"
-
# Compile a test program containing ISA 3.1 instructions.
- set src {
- int main() {
- asm volatile ("pnop"); // marker
+ return [allow_target_tests "allow_power_isa_3_1_tests" \
+ "Power ISA 3.1 hardware" "Illegal instruction" \
+ {
+ int main() {
+ asm volatile ("pnop"); // marker
asm volatile ("nop");
return 0;
}
- }
-
- if {![gdb_simple_compile $me $src executable ]} {
- return 0
- }
-
- # No error message, compilation succeeded so now run it via gdb.
-
- gdb_exit
- gdb_start
- gdb_reinitialize_dir $srcdir/$subdir
- gdb_load "$obj"
- gdb_run_cmd
- gdb_expect {
- -re ".*Illegal instruction.*${gdb_prompt} $" {
- verbose -log "\n$me Power ISA 3.1 hardware not detected"
- set allow_power_isa_3_1_tests 0
- }
- -re ".*$inferior_exited_re normally.*${gdb_prompt} $" {
- verbose -log "\n$me: Power ISA 3.1 hardware detected"
- set allow_power_isa_3_1_tests 1
- }
- default {
- warning "\n$me: default case taken"
- set allow_power_isa_3_1_tests 0
- }
- }
- gdb_exit
- remote_file build delete $obj
-
- verbose "$me: returning $allow_power_isa_3_1_tests" 2
- return $allow_power_isa_3_1_tests
+ }]
}
# Run a test on the target to see if it supports vmx hardware. Return 1 if so,
# 0 if it does not. Based on 'check_vmx_hw_available' from the GCC testsuite.
gdb_caching_proc allow_vsx_tests {} {
- global srcdir subdir gdb_prompt inferior_exited_re
-
set me "allow_vsx_tests"
# Some simulators are known to not support Altivec instructions, so
@@ -4465,56 +4400,28 @@ gdb_caching_proc allow_vsx_tests {} {
# Make sure we have a compiler that understands altivec.
if {[test_compiler_info gcc*]} {
- set compile_flags "additional_flags=-mvsx"
+ set flags "-mvsx"
} elseif {[test_compiler_info xlc*]} {
- set compile_flags "additional_flags=-qasm=gcc"
+ set flags "-qasm=gcc"
} else {
verbose "Could not compile with vsx support, returning 0" 2
return 0
}
# Compile a test program containing VSX instructions.
- set src {
- int main() {
- double a[2] = { 1.0, 2.0 };
- #ifdef __MACH__
- asm volatile ("lxvd2x v0,v0,%[addr]" : : [addr] "r" (a));
- #else
- asm volatile ("lxvd2x 0,0,%[addr]" : : [addr] "r" (a));
- #endif
- return 0;
- }
- }
- if {![gdb_simple_compile $me $src executable $compile_flags]} {
- return 0
- }
-
- # No error message, compilation succeeded so now run it via gdb.
-
- gdb_exit
- gdb_start
- gdb_reinitialize_dir $srcdir/$subdir
- gdb_load "$obj"
- gdb_run_cmd
- gdb_expect {
- -re ".*Illegal instruction.*${gdb_prompt} $" {
- verbose -log "\n$me VSX hardware not detected"
- set allow_vsx_tests 0
- }
- -re ".*$inferior_exited_re normally.*${gdb_prompt} $" {
- verbose -log "\n$me: VSX hardware detected"
- set allow_vsx_tests 1
- }
- default {
- warning "\n$me: default case taken"
- set allow_vsx_tests 0
- }
- }
- gdb_exit
- remote_file build delete $obj
-
- verbose "$me: returning $allow_vsx_tests" 2
- return $allow_vsx_tests
+ return [allow_target_tests $me "VSX hardware" "Illegal instruction" \
+ {
+ int main() {
+ double a[2] = { 1.0, 2.0 };
+ #ifdef __MACH__
+ asm volatile ("lxvd2x v0,v0,%[addr]" : : [addr] "r" (a));
+ #else
+ asm volatile ("lxvd2x 0,0,%[addr]" : : [addr] "r" (a));
+ #endif
+ return 0;
+ }
+ } \
+ $flags]
}
# Run a test on the target to see if it supports TSX hardware. Return 1 if so,
next prev parent reply other threads:[~2026-07-23 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 18:52 [PATCH 0/7] MIPS+testsuite: BLEZL stepping fix and associated test infrastructure Maciej W. Rozycki
2026-07-23 18:52 ` [PATCH 1/7] testsuite: Factor out target feature test template Maciej W. Rozycki
2026-07-23 18:52 ` Maciej W. Rozycki [this message]
2026-07-23 18:52 ` [PATCH 3/7] MIPS/testsuite: Verify MIPS I CPU branch stepping Maciej W. Rozycki
2026-07-23 18:53 ` [PATCH 4/7] MIPS: Correct BLEZL single-stepping Maciej W. Rozycki
2026-07-23 18:53 ` [PATCH 5/7] MIPS/testsuite: Verify MIPS II CPU branch stepping Maciej W. Rozycki
2026-07-23 18:53 ` [PATCH 6/7] MIPS/testsuite: Verify MIPS16 " Maciej W. Rozycki
2026-07-23 18:53 ` [PATCH 7/7] MIPS: Reorder a reference to "BGTZ, BGTZL" in `mips32_next_pc' Maciej W. Rozycki
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=alpine.DEB.2.21.2607222358210.14485@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=Djordje.Todorovic@htecgroup.com \
--cc=gdb-patches@sourceware.org \
--cc=jovan.dmitrovic@htecgroup.com \
--cc=macro@globalfoundries.com \
--cc=milica.matic@htecgroup.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