public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6601] testsuite: gcc.dg/pr108117.c: Require effective-target scheduling Date: Fri, 10 Mar 2023 22:48:55 +0000 (GMT) [thread overview] Message-ID: <20230310224855.AA8C138582AB@sourceware.org> (raw) https://gcc.gnu.org/g:88bcd4e5678260bfd60c6cbc7ecb63b8aeafd20e commit r13-6601-g88bcd4e5678260bfd60c6cbc7ecb63b8aeafd20e Author: Hans-Peter Nilsson <hp@axis.com> Date: Fri Mar 10 17:38:42 2023 +0100 testsuite: gcc.dg/pr108117.c: Require effective-target scheduling Targets that don't support scheduling get a warning: cc1: warning: instruction scheduling not supported on this target machine Do like other target-generic tests unconditionally passing -fschedule-insns: require effective target scheduling. * gcc.dg/pr108117.c: Require effective-target scheduling. Diff: --- gcc/testsuite/gcc.dg/pr108117.c | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/testsuite/gcc.dg/pr108117.c b/gcc/testsuite/gcc.dg/pr108117.c index ae151693e2f..4b3bebe229e 100644 --- a/gcc/testsuite/gcc.dg/pr108117.c +++ b/gcc/testsuite/gcc.dg/pr108117.c @@ -1,5 +1,6 @@ /* { dg-do run } */ /* { dg-require-effective-target nonlocal_goto } */ +/* { dg-require-effective-target scheduling } */ /* { dg-options "-O2 -fschedule-insns" } */ #include <stdio.h>
reply other threads:[~2023-03-10 22:48 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=20230310224855.AA8C138582AB@sourceware.org \ --to=hp@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: linkBe 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).