public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "peng.wang@compiler-dev.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95718] [8/9/10/11 Regression] Wrong pointer associated status without initialization
Date: Thu, 23 Jul 2020 07:29:08 +0000 [thread overview]
Message-ID: <bug-95718-4-vnWq3OEwM2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95718-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95718
--- Comment #4 from PengWang <peng.wang@compiler-dev.com> ---
(In reply to kargl from comment #3)
> 16.5.2.2 Pointer association status
>
> A pointer may have a pointer association status of associated,
> disassociated, or undefined. Its association status may change
> during execution of a program. Unless a pointer is initialized
> (explicitly or by default), it has an initial association status
> of undefined. A pointer may be initialized to have an association
> status of disassociated or associated.
>
> 13.7.16 ASSOCIATED (POINTER [, TARGET])
>
> POINTER shall be a pointer. It may be of any type or may be a
> procedure pointer. Its pointer association status shall not
> be undefined.
>
> Your program is invalid.
thank you very much! The status of undefined has confused me for a long time,
now I understand it finally, thank you~
prev parent reply other threads:[~2020-07-23 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 9:04 [Bug fortran/95718] New: " peng.wang@compiler-dev.com
2020-06-17 10:12 ` [Bug fortran/95718] [8/9/10/11 Regression] " dominiq at lps dot ens.fr
2020-06-17 10:44 ` dominiq at lps dot ens.fr
2020-06-17 15:52 ` kargl at gcc dot gnu.org
2020-07-23 7:29 ` peng.wang@compiler-dev.com [this message]
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-95718-4-vnWq3OEwM2@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).