public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "federico.perini at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104927] Invalid array size specification accepted
Date: Tue, 15 Mar 2022 16:10:41 +0000	[thread overview]
Message-ID: <bug-104927-4-nVZqKUvzHS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104927-4@http.gcc.gnu.org/bugzilla/>

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

federico <federico.perini at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from federico <federico.perini at gmail dot com> ---
Yeah I'm surprised but wrong. The "overriding" option of the rhs size
specification is pretty clear from that statement from the standard.

This makes it even more evident: 

program test_invalid_shape
        implicit none

        integer, dimension(2,2) :: a(3),b(2,5),c

        print *, 'shape(a) = ',shape(a)
        print *, 'shape(b) = ',shape(b)
        print *, 'shape(c) = ',shape(c)

end program test_invalid_shape

produces 

 shape(a) =            3
 shape(b) =            2           5
 shape(c) =            2           2

  parent reply	other threads:[~2022-03-15 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15  8:46 [Bug fortran/104927] New: " federico.perini at gmail dot com
2022-03-15 15:27 ` [Bug fortran/104927] " kargl at gcc dot gnu.org
2022-03-15 16:10 ` federico.perini at gmail dot com [this message]
2022-03-15 16:34 ` sgk at troutmask dot apl.washington.edu

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-104927-4-nVZqKUvzHS@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).