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/109861] Optimization is marking uninitialized C_PTR being passed to a C function, causes segfault.
Date: Mon, 15 May 2023 21:25:28 +0000 [thread overview]
Message-ID: <bug-109861-4-ApIDcfdzhu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109861-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109861
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #5 from kargl at gcc dot gnu.org ---
(In reply to Scot Breitenfeld from comment #3)
> I see the same issue with NAG, regardless of the optimization level. Our CI
> testing had missed it because this was a parallel test, and we don't test
> parallel with NAG.
>
> I guess the issue is whether marking TYPE(C_PTR) as CLOBBER is correct. I
> looked through the 2018 standard and could not locate anything that
> addresses this use case. Are you interpreting the possibility that a
> TYPE(C_PTR) should not be declared INTENT(OUT)?
Fortran 2023, 8.5.10
The INTENT (OUT) attribute for a nonpointer dummy argument specifies
that the dummy argument becomes undefined on invocation of the procedure,
except for any subcomponents that are default-initialized (7.5.4.6).
next prev parent reply other threads:[~2023-05-15 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 14:00 [Bug fortran/109861] New: " brtnfld at hdfgroup dot org
2023-05-15 18:23 ` [Bug fortran/109861] " anlauf at gcc dot gnu.org
2023-05-15 18:49 ` anlauf at gcc dot gnu.org
2023-05-15 20:08 ` brtnfld at hdfgroup dot org
2023-05-15 21:22 ` anlauf at gcc dot gnu.org
2023-05-15 21:25 ` kargl at gcc dot gnu.org [this message]
2023-05-16 13:27 ` brtnfld at hdfgroup dot org
2023-05-16 13:29 ` brtnfld at hdfgroup dot 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-109861-4-ApIDcfdzhu@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).