public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-10358] testsuite, jit: Allow for target-specific assembler scans.
Date: Sat, 20 Apr 2024 14:43:35 +0000 (GMT)	[thread overview]
Message-ID: <20240420144335.345F83858D37@sourceware.org> (raw)

https://gcc.gnu.org/g:e73c4d7a236da0a1a9232861fe32bca0e5304870

commit r12-10358-ge73c4d7a236da0a1a9232861fe32bca0e5304870
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Sat Jan 13 13:30:08 2024 +0000

    testsuite, jit: Allow for target-specific assembler scans.
    
    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)

Diff:
---
 gcc/testsuite/jit.dg/jit.exp | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/gcc/testsuite/jit.dg/jit.exp b/gcc/testsuite/jit.dg/jit.exp
index 3568dbb9d63..35d38cec5bc 100644
--- a/gcc/testsuite/jit.dg/jit.exp
+++ b/gcc/testsuite/jit.dg/jit.exp
@@ -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"

                 reply	other threads:[~2024-04-20 14:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240420144335.345F83858D37@sourceware.org \
    --to=iains@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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).