From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id A1DD03857830; Fri, 29 Oct 2021 09:39:08 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A1DD03857830
From: "b.j.braams at cwi dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/102966] size() returns 0 for an unallocated array, no
 error message or error exit
Date: Fri, 29 Oct 2021 09:39:08 +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: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: b.j.braams at cwi dot nl
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
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: 
Message-ID: <bug-102966-4-oErjRLXqPf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-102966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-102966-4@http.gcc.gnu.org/bugzilla/>
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 <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2021 09:39:08 -0000

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

--- Comment #7 from Bastiaan Braams <b.j.braams at cwi dot nl> ---
Pleased to see that the run-time error is properly diagnosed in version 11.=
2.1
and later, and agreed that the matter is outside the fortran language stand=
ard.
Just one comment on the discussion in view of the WONTFIX label: the failur=
e to
generate a run-time error for this code may be viewed, I think, as a bug
against the specification of the -fcheck=3Dall option, which includes
-fcheck=3Dpointer with the description "Enable generation of run-time check=
s for
pointers and allocatables." It appears that an appropriate run-time check w=
as
not generated.=