public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nickpapior at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99765] New: Explicit dimension size declaration of pointer array allowed
Date: Thu, 25 Mar 2021 09:22:51 +0000	[thread overview]
Message-ID: <bug-99765-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99765
           Summary: Explicit dimension size declaration of pointer array
                    allowed
           Product: gcc
           Version: 4.8.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nickpapior at gmail dot com
  Target Milestone: ---

A mishandling of variable declarations

Consider this program:

program test
  real, dimension(10), pointer :: a(:) => null()

  print *, associated(a)
  allocate(a(2))
  print *, size(a)
  !print *, size(a(1)) ! obviously fails as a(1) is a scalar

end program test


It is ambiguous to determine the size of a. The programmer may think that after
allocation one has 2x10 elements a(1:2)(1:10) however what is happening is that
the dimension(10) attribute is completely ignored.

I can't find anywhere in the standard mentioning that this way of definition is
wrong, but I think it clearly shouldn't be allowed.

I.e. it is unclear whether the user wants a(1:2)(1:10) or a(1:10)(1:2), in any
case neither of the results are achieved.

I found this bug in 4.8.4 and also in 9.3.0, so I assume it exists in all in
between.

A few more cases that resemble this:

  real, dimension(10), allocatable :: a(:)

behaves exactly like with pointers. It is not well-defined and gets to the
a(1:2) case.

  real, dimension(10), allocatable :: a(10)

rightfully errors out on compilation with a somewhat unclear error message

    3 |   real, dimension(10) :: a(10)
      |                          1
Error: Symbol ‘a’ at (1) already has basic type of REAL

             reply	other threads:[~2021-03-25  9:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25  9:22 nickpapior at gmail dot com [this message]
2021-03-25 11:43 ` [Bug fortran/99765] " dominiq at lps dot ens.fr
2021-03-25 11:47 ` nickpapior at gmail dot com
2021-03-25 15:48 ` burnus at gcc dot gnu.org
2021-03-26  6:41 ` nickpapior at gmail dot com
2021-03-26  7:36 ` burnus 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-99765-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).