public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85510] [10/11/12/13/14 Regression][Coarray] Linking error when accessing a coindexed variable inside an associate block
Date: Fri, 02 Jun 2023 07:56:37 +0000 [thread overview]
Message-ID: <bug-85510-4-E7x4V89ZTH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-85510-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85510
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pault at gcc dot gnu.org
--- Comment #10 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Damian Rouson from comment #0)
> The code below compiles without error with -fcoarray=single; whereas
> compiling with -fcoarray=lib generates the link-time error message shown
> with the gfortran 7.2.0 and with the trunk dated 20180412. The gfortran
> command comes from the output of the OpenCoarrays command 'caf --show'. Some
> of the paths have been shortened manually for presentation purposes:
>
Hi Damian,
Could you check, please, whether or not this still fails?
Thanks
Paul
next prev parent reply other threads:[~2023-06-02 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-85510-4@http.gcc.gnu.org/bugzilla/>
2021-05-14 9:50 ` [Bug fortran/85510] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:11 ` rguenth at gcc dot gnu.org
2022-05-27 9:39 ` [Bug fortran/85510] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:35 ` jakub at gcc dot gnu.org
2023-06-02 7:56 ` pault at gcc dot gnu.org [this message]
2023-07-07 10:33 ` [Bug fortran/85510] [11/12/13/14 " rguenth 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-85510-4-E7x4V89ZTH@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).