public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-4150] Adjust gfortran.dg/predict-2.f90 Date: Tue, 5 Oct 2021 06:37:51 +0000 (GMT) [thread overview] Message-ID: <20211005063751.EF923385701C@sourceware.org> (raw) https://gcc.gnu.org/g:1581aa38eba0ab47eaebe45e8dc6bef6832381c8 commit r12-4150-g1581aa38eba0ab47eaebe45e8dc6bef6832381c8 Author: Richard Biener <rguenther@suse.de> Date: Tue Oct 5 08:35:17 2021 +0200 Adjust gfortran.dg/predict-2.f90 After teaching VN to handle internal functions we now optimize the redundant inner loop preheader check of the testcase making the dump scanning fail because there's nothing to predict left. The following restores the inner preheader check by making it not redundant. 2021-10-05 Richard Biener <rguenther@suse.de> * gfortran.dg/predict-2.f90: Adjust to avoid redundant inner loop preheader checking code. Diff: --- gcc/testsuite/gfortran.dg/predict-2.f90 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/testsuite/gfortran.dg/predict-2.f90 b/gcc/testsuite/gfortran.dg/predict-2.f90 index 11a9ec5fd4b..93e3ad65c74 100644 --- a/gcc/testsuite/gfortran.dg/predict-2.f90 +++ b/gcc/testsuite/gfortran.dg/predict-2.f90 @@ -2,10 +2,10 @@ ! { dg-options "-O2 -fdump-tree-profile_estimate" } subroutine test(block, array) -integer :: i,j, block(9), array(2) +integer :: i,j, block(9), array(4) do i = array(1), array(2), 2 - do j = array(1), array(2), 3 + do j = array(3), array(4), 3 block(i) = j end do end do
reply other threads:[~2021-10-05 6:37 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=20211005063751.EF923385701C@sourceware.org \ --to=rguenth@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).