public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/94030] [8/9/10 Regression] ICE equivalence of an integer and an element of an array of size n
Date: Fri, 27 Mar 2020 15:42:07 +0000 [thread overview]
Message-ID: <bug-94030-4-Yyu0wN8rDW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94030-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94030
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #4 from kargl at gcc dot gnu.org ---
(In reply to markeggleston from comment #3)
> A patch from Steve Kargl was sent to the fortran mailing list, (see
> https://gcc.gnu.org/pipermail/fortran/2020-March/054130.html) without
> reference to any PR.
>
> It appeared to be related to this PR. I have verified the patch and also
> checked it with the test case in the original report.
Techinically, it is related to
https://stackoverflow.com/questions/60846187/fortran-equivalence-statement-with-array-length-from-subroutine-input
In the stackoverflow thread, someone mentioned this is a regression going back
to at least 6.5.
next prev parent reply other threads:[~2020-03-27 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-94030-4@http.gcc.gnu.org/bugzilla/>
2020-03-27 9:51 ` markeggleston at gcc dot gnu.org
2020-03-27 15:42 ` kargl at gcc dot gnu.org [this message]
2020-04-02 6:19 ` cvs-commit at gcc dot gnu.org
2020-04-02 7:27 ` cvs-commit at gcc dot gnu.org
2020-04-02 7:32 ` cvs-commit at gcc dot gnu.org
2020-04-02 7:46 ` markeggleston at gcc dot gnu.org
2020-04-16 13:06 ` tkoenig 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-94030-4-Yyu0wN8rDW@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).