From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 179D13858028; Fri, 26 Mar 2021 07:36:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 179D13858028 From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/99765] Explicit dimension size declaration of pointer array allowed Date: Fri, 26 Mar 2021 07:36:05 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.8.4 X-Bugzilla-Keywords: accepts-invalid X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Mar 2021 07:36:06 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D99765 Tobias Burnus changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #5 from Tobias Burnus --- (In reply to Nick from comment #4) > I see. I can't seem to find the mentioned line in f2003. Should be there as well. In Fortran 2008, it is in "5.2 Type declaration statements", p.88, lines 1-4 (same/similar to F2018). In Fortran 2003, it is in "5.1.2.5 DIMENSION attribute", p. 78, ll. 3-5: "The DIMENSION attribute specifies that an entity is an array. The rank or rank and shape is specified by the array-spec, if there is one, in the entity-decl, or by the array-spec in the DIMENSION attr-spec otherwise." That choice makese sense, e.g. for: complex(kind=3Dmy_cmplx_kind), intent(in), asynchronous, dimension(n,n) :: = A, B, C, D, v(n) such that one does not need to repeat all the lengthy stuff just to denote = the different array spec for 'v'. (On the other hand, whether there is a need to specify everything in several different ways and permit overriding in addit= ion is another question.) Thus, the standard made a sensible choice =E2=80=93 and the standard is the= standard :-)=20 > In any case, I would be fine if this is marked as invalid Done so: CLOSE as INVALID. > Sorry for the blurp. Better some noise than missing some real bugs or useful improvements. Hence: Thanks!=