From: Hans-Peter Nilsson <hp@axis.com>
Date: Mon, 10 Feb 2020 16:25:56 +0000 (+0100)
Subject: gcc.target/cris/cris.exp (check_effective_target_cc0): New.
X-Git-Tag: upstream/12.2.0~18478
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=dcdd0aa872b16e99c39395358344b59f517c2558;p=platform%2Fupstream%2Fgcc.git

gcc.target/cris/cris.exp (check_effective_target_cc0): New.

To simplify separating the cc0-specific xfails, let's have an
effective-target.

This likely fits all targets.
---

diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 5441fb1..1b48abd 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2020-02-10  Hans-Peter Nilsson  <hp@axis.com>
+
+	* gcc.target/cris/cris.exp (check_effective_target_cc0): New.
+
 2020-02-10  Jakub Jelinek  <jakub@redhat.com>
 
 	PR target/91913
diff --git a/gcc/testsuite/gcc.target/cris/cris.exp b/gcc/testsuite/gcc.target/cris/cris.exp
index c85c849..5216451 100644
--- a/gcc/testsuite/gcc.target/cris/cris.exp
+++ b/gcc/testsuite/gcc.target/cris/cris.exp
@@ -25,6 +25,17 @@ if { ![istarget cris-*-*] && ![istarget crisv32-*-*] } then {
 # Load support procs.
 load_lib gcc-dg.exp
 
+# For the time being, provide a means to tell whether the target is "cc0".
+# Some targets may split cbranch and cstore late, but for a cc0-target,
+# all the fun happens at "final" time, so this should be a safe time for
+# a scan.
+proc check_effective_target_cc0 { } {
+    return [check_no_messages_and_pattern cc0 "\\(cc0\\)" rtl-final {
+	extern void g (void);
+	void f (int *p, int *q) { *q = *p == 42; if (*p == 7) g (); }
+    }]
+}
+
 # If a testcase doesn't have special options, use these.
 global DEFAULT_CFLAGS
 if ![info exists DEFAULT_CFLAGS] then {