public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Mikael Morin <mikael@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-8243] testsuite: add additional option to force DSE execution [PR103662]
Date: Mon, 25 Apr 2022 11:32:06 +0000 (GMT)	[thread overview]
Message-ID: <20220425113206.302833858D28@sourceware.org> (raw)

https://gcc.gnu.org/g:6cc26f3037a18b9a958b4ac2a1363149a7fccd39

commit r12-8243-g6cc26f3037a18b9a958b4ac2a1363149a7fccd39
Author: Mikael Morin <mikael@gcc.gnu.org>
Date:   Mon Apr 25 13:14:20 2022 +0200

    testsuite: add additional option to force DSE execution [PR103662]
    
    This fixes a dump tree match check that is UNRESOLVED with the -O0
    optimization option, as the optimization pass corresponding to the
    dump file is not run at -O0, and the dump is not generated.
    
            PR fortran/103662
    
    gcc/testsuite/ChangeLog:
    
            * gfortran.dg/unlimited_polymorphic_3.f03: Force execution of
            the DSE optimization pass.

Diff:
---
 gcc/testsuite/gfortran.dg/unlimited_polymorphic_3.f03 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gfortran.dg/unlimited_polymorphic_3.f03 b/gcc/testsuite/gfortran.dg/unlimited_polymorphic_3.f03
index 780d68cdd87..4104de6ac68 100644
--- a/gcc/testsuite/gfortran.dg/unlimited_polymorphic_3.f03
+++ b/gcc/testsuite/gfortran.dg/unlimited_polymorphic_3.f03
@@ -1,5 +1,5 @@
 ! { dg-do run }
-! { dg-additional-options "-fdump-tree-dse-details" }
+! { dg-additional-options "-ftree-dse -fdump-tree-dse-details" }
 !
 ! Check that pointer assignments allowed by F2003:C717
 ! work and check null initialization of CLASS(*) pointers.


                 reply	other threads:[~2022-04-25 11:32 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=20220425113206.302833858D28@sourceware.org \
    --to=mikael@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: link
Be 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).