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] New: Wrong pointer associated status without initialization
Date: Wed, 17 Jun 2020 09:04:17 +0000	[thread overview]
Message-ID: <bug-95718-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95718

            Bug ID: 95718
           Summary: Wrong pointer associated status without initialization
           Product: gcc
           Version: 10.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: peng.wang@compiler-dev.com
  Target Milestone: ---

consider the code below:

****
program test
integer,pointer::ptr
integer,pointer::ptr1
integer,pointer::ptr2
integer,pointer::ptr3
integer,pointer::ptr4

print*,associated(ptr),'associated(ptr)'
print*,associated(ptr1),'associated(ptr1)'
print*,associated(ptr2),'associated(ptr2)'
print*,associated(ptr3),'associated(ptr3)'
print*,associated(ptr4),'associated(ptr4)'
end program test
****

#gfortran -std=f2008 test.f90 ; ./a.out
 T associated(ptr)
 F associated(ptr1)
 T associated(ptr2)
 F associated(ptr3)
 T associated(ptr4)

the associated status of the pointers is uncertain after the execution above.

according to F2008 draft 16.5.2.7, the associated status of the pointer should
be F in the case above.

this is the options given when GCC was configured:
# gfortran -v
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/usr/local/gcc/libexec/gcc/x86_64-pc-linux-gnu/10.1.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../configure --prefix=/usr/local/gcc -enable-checking=release
-enable-languages=c,fortran -disable-bootstrap -disable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.1.0 (GCC)

             reply	other threads:[~2020-06-17  9:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17  9:04 peng.wang@compiler-dev.com [this message]
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

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@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).