From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Paul Richard Thomas via Fortran <fortran@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR107900 Select type with intrinsic type inside associate causes ICE / Segmenation fault
Date: Sat, 17 Jun 2023 08:33:29 -0700 [thread overview]
Message-ID: <ZI3SSbVMUmUPZkJb@troutmask.apl.washington.edu> (raw)
In-Reply-To: <CAGkQGiJyZDofE5VhYpCgKKyHg8YSQBLBZMYJspfJ40Kf6J+PcA@mail.gmail.com>
On Sat, Jun 17, 2023 at 10:14:43AM +0100, Paul Richard Thomas via Fortran wrote:
>
> PS This leaves 89645 and 99065 as the only real blockers to PR87477.
>
Hate to be the bearer of bad news, but Neil Carlson has added
a couple PRs about associate that may not be listed in 87447.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110224
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110033
For the second one, if I suppress the bogus error message,
the compiler runs into a new error message. The second
error message indicates the associate-name is not an
unexpected coarray. I haven't determined how to propagate
the information that the selector is a coarray to the
associate-name.
--
Steve
next prev parent reply other threads:[~2023-06-17 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 9:14 Paul Richard Thomas
2023-06-17 15:33 ` Steve Kargl [this message]
2023-06-17 18:01 ` Harald Anlauf
2023-06-18 7:54 ` Paul Richard Thomas
2023-06-20 10:54 ` Paul Richard Thomas
2023-06-20 21:57 ` Harald Anlauf
2023-06-21 16:12 ` Paul Richard Thomas
2023-06-21 16:46 ` Steve Kargl
2023-06-21 18:40 ` Harald Anlauf
2023-06-21 19:17 ` Bernhard Reutner-Fischer
2023-06-22 6:19 ` Paul Richard Thomas
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=ZI3SSbVMUmUPZkJb@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--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).