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 85BF83858C5E; Fri, 14 Apr 2023 19:24:31 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 85BF83858C5E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1681500271;
	bh=D4w5LoPqAVVJVrGJF0ZeGtYfmvoo7dd4H3a7whKyg70=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=xzfb6sOim3h6klnbwlFxdAhb/XXhZP2AOj8MMjGivioUhH/FRAZfOS/kitTBJR6il
	 YMnEOiyZgyHMl6H1KtdGTMFXwQ2l8+NRB5tMhtFuC6Y5sFMVUHF03aNOCwm5U2G1gt
	 JR9xHrLnGN5Z7oQdmIYotvr+Q7jzlnjSXv0UGO1Y=
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/109500] SIGABRT when calling a function that returns an
 unallocated value
Date: Fri, 14 Apr 2023 19:24:30 +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: 12.0
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: anlauf at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cf_reconfirmed_on bug_status everconfirmed
 keywords priority bug_severity
Message-ID: <bug-109500-4-Qm8KozuqLJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109500-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109500-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
List-Id: <gcc-bugs.sourceware.org>

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

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2023-04-14
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
           Keywords|                            |accepts-invalid, diagnostic
           Priority|P3                          |P5
           Severity|normal                      |enhancement

--- Comment #8 from anlauf at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #7)
> I suspect it works by accident, but I don't have enough
> time at the moment to go read the gfortran source.  What=20
> is likely happening is gfortran checks that the actual
> and dummy argument both have the allocatable attribute.
> For the actual argument, the symbol is probably marked
> an allocatable attribute and an internal attribute=20
> that designates this as a function-result, and gfortran
> does not check for the latter.

So marking as a missed diagnostic for invalid code.=