]> git.ipfire.org Git - thirdparty/gcc.git/commitdiff
testsuite, jit: Allow for target-specific assembler scans.
authorIain Sandoe <iain@sandoe.co.uk>
Sat, 13 Jan 2024 13:30:08 +0000 (13:30 +0000)
committerIain Sandoe <iain@sandoe.co.uk>
Sat, 20 Apr 2024 14:43:26 +0000 (15:43 +0100)
If we want to support multiple object formats and to allow for
scan-assembler tests, we need to make it possible to adjust the
tests on a per-target basis.

This adds similar mechamisms to jit-verify-assembler-output
to those used for the general scan-assembler dg directives.

As an aside; it would, perhaps, be possible to integrate this more
with scanasm.exp (which would also give access to function body
scanning) but I did not attempt that for this patch.

After this, we can accept things like:
... { jit-verify-assembler-output "......" { target *-*-darwin* } } }

gcc/testsuite/ChangeLog:

* jit.dg/jit.exp: Accept target clauses in jit-verify-assembler
handling.

Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
(cherry picked from commit e0e3ef18a047d54d63be91d82a55448851353260)

gcc/testsuite/jit.dg/jit.exp

index 3568dbb9d6334aed3c49d750d335e1034d899c72..35d38cec5bc1d3fa1fecdfa101e3c8abeff75b09 100644 (file)
@@ -871,9 +871,23 @@ proc jit-verify-assembler { args } {
 proc jit-verify-assembler-output { args } {
     verbose "jit-verify-assembler: $args"
 
+    if { [llength $args] > 3 } {
+       error "jit-verify-assembler-output: too many arguments"
+       return
+    }
+
     set dg-output-text [lindex $args 0]
     verbose "dg-output-text: ${dg-output-text}"
 
+    if { [llength $args] >= 2 } {
+       switch [dg-process-target [lindex $args 1]] {
+           "S" { }
+           "N" { return }
+           "F" { setup_xfail "*-*-*" }
+           "P" { }
+       }
+    }
+
     upvar 2 name name
     verbose "name: $name"