public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Stefan Schulze Frielinghaus <stefansf@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-9931] testsuite: Fix loop-interchange-16.c Date: Fri, 12 Apr 2024 07:22:24 +0000 (GMT) [thread overview] Message-ID: <20240412072224.DBAD3384AB60@sourceware.org> (raw) https://gcc.gnu.org/g:b6c8259076a336e8082853ed6dda083c25a465d0 commit r14-9931-gb6c8259076a336e8082853ed6dda083c25a465d0 Author: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> Date: Fri Apr 12 09:20:53 2024 +0200 testsuite: Fix loop-interchange-16.c Prevent loop unrolling of the innermost loop because otherwise we are left with no loop interchange for targets like s390 which have a more aggressive loop unrolling strategy. gcc/testsuite/ChangeLog: * gcc.dg/tree-ssa/loop-interchange-16.c: Prevent loop unrolling of the innermost loop. Diff: --- gcc/testsuite/gcc.dg/tree-ssa/loop-interchange-16.c | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/testsuite/gcc.dg/tree-ssa/loop-interchange-16.c b/gcc/testsuite/gcc.dg/tree-ssa/loop-interchange-16.c index 781555e085d..bbcb14f9c6c 100644 --- a/gcc/testsuite/gcc.dg/tree-ssa/loop-interchange-16.c +++ b/gcc/testsuite/gcc.dg/tree-ssa/loop-interchange-16.c @@ -11,6 +11,7 @@ double s231(int iterations) // loop with data dependency for (int nl = 0; nl < 100*(iterations/LEN_2D); nl++) { for (int i = 0; i < LEN_2D; ++i) { +#pragma GCC unroll 0 for (int j = 1; j < LEN_2D; j++) { aa[j][i] = aa[j - 1][i] + bb[j][i]; }
reply other threads:[~2024-04-12 7:22 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=20240412072224.DBAD3384AB60@sourceware.org \ --to=stefansf@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).