public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/111781] Fortran compiler complains about variable bound in array dummy argument
Date: Wed, 28 Feb 2024 19:38:18 +0000 [thread overview]
Message-ID: <bug-111781-4-bYtGHrWpFO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111781-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111781
--- Comment #6 from Mikael Morin <mikael at gcc dot gnu.org> ---
Created attachment 57571
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57571&action=edit
Tentative patch
(In reply to anlauf from comment #5)
> (In reply to anlauf from comment #4)
> > Thus I suggest to fix the testcase by one of the options suggested above.
>
> Testcase gfortran.dg/pr101026.f is corrected at r14-9220.
Ah, yes, thanks.
I attach above the tentative patch that I tried before.
I need to reevaluate it; there were other regressions if I remember correctly.
next prev parent reply other threads:[~2024-02-28 19:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 9:06 [Bug fortran/111781] New: Compiler error on valid code rasmus.vikhamar-sandberg at uit dot no
2023-10-12 10:16 ` [Bug fortran/111781] Fortran compiler complains about variable bound in array dummy argument mikael at gcc dot gnu.org
2023-10-21 14:01 ` mikael at gcc dot gnu.org
2023-10-21 16:37 ` mikael at gcc dot gnu.org
2024-02-06 18:19 ` anlauf at gcc dot gnu.org
2024-02-28 18:25 ` anlauf at gcc dot gnu.org
2024-02-28 19:38 ` mikael at gcc dot gnu.org [this message]
2024-03-15 19:37 ` mikael at gcc dot gnu.org
2024-03-15 19:57 ` anlauf at gcc dot gnu.org
2024-03-15 20:25 ` mikael at gcc dot gnu.org
2024-03-22 12:07 ` cvs-commit at gcc dot gnu.org
2024-03-28 10:40 ` cvs-commit at gcc dot gnu.org
2024-04-02 13:15 ` mikael at gcc dot gnu.org
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=bug-111781-4-bYtGHrWpFO@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).