public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-4719] testsuite: Add support for Rust and Modula-2 effective target tests
Date: Thu, 15 Dec 2022 12:58:27 +0000 (GMT)	[thread overview]
Message-ID: <20221215125827.0AC75388DD40@sourceware.org> (raw)

https://gcc.gnu.org/g:9cf9f3c7629d768d940d9f87cddcd616bb0449e0

commit r13-4719-g9cf9f3c7629d768d940d9f87cddcd616bb0449e0
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Dec 15 13:57:43 2022 +0100

    testsuite: Add support for Rust and Modula-2 effective target tests
    
    This patch allows magic comments also for Rust and Modula-2
    for effective target tests etc. and fixes up the Assembly entry
    - it is a glob, so /* Assembly can match /whatever Assembly and
    not just /* Assembly.
    
    Tested on x86_64-linux with
    make check-g++ RUNTESTFLAGS=i386.exp=pr35513*
    and verifying it still uses *.S extension for the property_1_needed
    effective target test.
    
    2022-12-15  Jakub Jelinek  <jakub@redhat.com>
    
            * lib/target-supports.exp (check_compile): Add support for
            Rust and Modula-2.  Use \* rather than * for /* comment for
            Assembly.

Diff:
---
 gcc/testsuite/lib/target-supports.exp | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index 2a058c67c53..e9867a4529c 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -36,7 +36,9 @@
 # "! Fortran" for Fortran code,
 # "/* ObjC", for ObjC
 # "// ObjC++" for ObjC++
-# and "// Go" for Go
+# "// Go" for Go
+# "// Rust" for Rust
+# and "(* Modula-2" for Modula-2
 # If the tool is ObjC/ObjC++ then we overide the extension to .m/.mm to 
 # allow for ObjC/ObjC++ specific flags.
 
@@ -58,13 +60,15 @@ proc check_compile {basename type contents args} {
 	set options ""
     }
     switch -glob -- $contents {
-	"*/* Assembly*" { set src ${basename}[pid].S }
+	"*/\* Assembly*" { set src ${basename}[pid].S }
 	"*! Fortran*" { set src ${basename}[pid].f90 }
 	"*// C++*" { set src ${basename}[pid].cc }
 	"*// D*" { set src ${basename}[pid].d }
 	"*// ObjC++*" { set src ${basename}[pid].mm }
 	"*/* ObjC*" { set src ${basename}[pid].m }
 	"*// Go*" { set src ${basename}[pid].go }
+	"*// Rust*" { set src ${basename}[pid].rs }
+	"*(\* Modula-2*" { set src ${basename}[pid].mod }
 	default {
 	    switch -- $tool {
 		"objc" { set src ${basename}[pid].m }

                 reply	other threads:[~2022-12-15 12:58 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=20221215125827.0AC75388DD40@sourceware.org \
    --to=jakub@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).