public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99765] Explicit dimension size declaration of pointer array allowed
Date: Thu, 25 Mar 2021 11:43:58 +0000	[thread overview]
Message-ID: <bug-99765-4-4F5EQpAoN9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99765-4@http.gcc.gnu.org/bugzilla/>

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2021-03-25
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
The standard says:

C832 An array with the POINTER or ALLOCATABLE attribute shall have an
array-spec 
that is a deferred-shape-spec-list.

so I think

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

and

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

are invalid and shall give an error.

Note that a(1:2)(1:10) looks like C syntax, a rank 2 array is a(1:2,1:10).
The only case for valid fortran is for a being of type CHARACTER, a(1;2) being
a slice and (1:10) a substring.

  reply	other threads:[~2021-03-25 11:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25  9:22 [Bug fortran/99765] New: " nickpapior at gmail dot com
2021-03-25 11:43 ` dominiq at lps dot ens.fr [this message]
2021-03-25 11:47 ` [Bug fortran/99765] " 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-4F5EQpAoN9@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).