public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/114141] ASSOCIATE and complex part ref when associate target is a function
Date: Wed, 28 Feb 2024 02:11:29 +0000 [thread overview]
Message-ID: <bug-114141-4-hmjUrB6ztL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114141-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114141
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle at gcc dot gnu.org
--- Comment #1 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
I see the fail here but I am not sure of the validity. I am going to read the
latest standard. I always thought of associate to refer associate complicated
data references to make code more readable. In this case it is referring to a
function which resolves to a constant.
Interestingly if I wrap the associate with parens one gets:
associate (x => (log(cmplx(-1,0))))
$ gfc pr114141.f90
pr114141.f90:6:14:
6 | y = x%im
| 1
Error: The RE or IM part_ref at (1) must be applied to a COMPLEX expression
next prev parent reply other threads:[~2024-02-28 2:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 22:11 [Bug fortran/114141] New: " kargl at gcc dot gnu.org
2024-02-28 2:11 ` jvdelisle at gcc dot gnu.org [this message]
2024-02-28 2:21 ` [Bug fortran/114141] " jvdelisle at gcc dot gnu.org
2024-02-28 15:43 ` kargl at gcc dot gnu.org
2024-02-28 17:30 ` mikael at gcc dot gnu.org
2024-02-28 18:13 ` kargl at gcc dot gnu.org
2024-02-28 19:27 ` mikael at gcc dot gnu.org
2024-02-28 20:24 ` sgk at troutmask dot apl.washington.edu
2024-02-28 20:42 ` sgk at troutmask dot apl.washington.edu
2024-02-28 22:32 ` jvdelisle at gcc dot gnu.org
2024-02-29 18:33 ` pault at gcc dot gnu.org
2024-02-29 20:25 ` sgk at troutmask dot apl.washington.edu
2024-03-01 9:15 ` pault at gcc dot gnu.org
2024-03-01 9:16 ` pault at gcc dot gnu.org
2024-03-02 17:32 ` pault at gcc dot gnu.org
2024-03-15 6:53 ` cvs-commit at gcc dot gnu.org
2024-03-15 7:09 ` pault 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-114141-4-hmjUrB6ztL@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).