From: Harald Anlauf <anlauf@gmx.de>
To: fortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH] Fortran testsuite: fix invalid Fortran in testcase
Date: Tue, 27 Feb 2024 22:00:14 +0100 [thread overview]
Message-ID: <trinity-97b0f00a-c0ee-49fe-ad01-b4bd4fe74810-1709067614727@3c-app-gmx-bap21> (raw)
[-- Attachment #1: Type: text/plain, Size: 308 bytes --]
Dear all,
the attached patch fixes invalid Fortran in testcase
gfortran.dg/pr101026.f, which might prohibit progress
in fixing pr111781. (Note that the testcase was for a
tree-optimizer issue, not the Fortran frontend.)
OK for mainline?
Will commit within 24h unless there are comments.
Thanks,
Harald
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: pr101026-fix.diff --]
[-- Type: text/x-patch, Size: 950 bytes --]
From 75724b6b42a1c46383d8e6deedbfb8d2ebd0fa12 Mon Sep 17 00:00:00 2001
From: Harald Anlauf <anlauf@gmx.de>
Date: Tue, 27 Feb 2024 21:51:53 +0100
Subject: [PATCH] Fortran testsuite: fix invalid Fortran in testcase
gcc/testsuite/ChangeLog:
* gfortran.dg/pr101026.f: Let variables used in specification
expression be passed as dummy arguments
---
gcc/testsuite/gfortran.dg/pr101026.f | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/testsuite/gfortran.dg/pr101026.f b/gcc/testsuite/gfortran.dg/pr101026.f
index 9576d8802ca..e05e21c898a 100644
--- a/gcc/testsuite/gfortran.dg/pr101026.f
+++ b/gcc/testsuite/gfortran.dg/pr101026.f
@@ -1,6 +1,6 @@
! { dg-do compile }
! { dg-options "-Ofast -frounding-math" }
- SUBROUTINE PASSB4 (CC,CH)
+ SUBROUTINE PASSB4 (CC,CH,IDO,L1)
DIMENSION CC(IDO,4,L1), CH(IDO,L1,*)
DO 103 I=2,IDO,2
TI4 = CC0-CC(I,4,K)
--
2.35.3
next reply other threads:[~2024-02-27 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 21:00 Harald Anlauf [this message]
2024-02-28 3:53 ` Jerry D
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=trinity-97b0f00a-c0ee-49fe-ad01-b4bd4fe74810-1709067614727@3c-app-gmx-bap21 \
--to=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).