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.

gcc/testsuite/ChangeLog

+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

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 {