From: Jerry D <jvdelisle2@gmail.com>
To: Harald Anlauf <anlauf@gmx.de>, fortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran testsuite: fix invalid Fortran in testcase
Date: Tue, 27 Feb 2024 19:53:05 -0800 [thread overview]
Message-ID: <33f79ccc-504b-4ec6-9056-3ac7bd5822e9@gmail.com> (raw)
In-Reply-To: <trinity-97b0f00a-c0ee-49fe-ad01-b4bd4fe74810-1709067614727@3c-app-gmx-bap21>
On 2/27/24 1:00 PM, Harald Anlauf wrote:
> 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
>
OK, simple.
prev parent reply other threads:[~2024-02-28 3:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 21:00 Harald Anlauf
2024-02-28 3:53 ` Jerry D [this message]
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=33f79ccc-504b-4ec6-9056-3ac7bd5822e9@gmail.com \
--to=jvdelisle2@gmail.com \
--cc=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).