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 ED256385841D; Thu, 13 Apr 2023 17:06:53 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ED256385841D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1681405613;
	bh=+jLpMJGdryvPU17E82OyEbg8k0U6TX3qUt3Wosm9P5M=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=f8i/mTVHAvzlWXNZf5UwfOtrHCrvhaYcNS6XPUekqEtSBUFEgqMQ7OJPGxr/qGbLj
	 8ngFZ9BQPVoNgHAR1vsPjGbf1rgnGaVLSCFXooBVuM10Z9G+euiA5gFfvfBDWbjy/b
	 FR3MFqHSzConCTw1OI/dltxSYRA+icujAxNUs14g=
From: "leandro.lupori at linaro dot 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: Thu, 13 Apr 2023 17:06:53 +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: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: leandro.lupori at linaro dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
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-109500-4-2FuArzTzaA@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

--- Comment #2 from Leandro Lupori <leandro.lupori at linaro dot org> ---
Thanks for the quick response.

What if 'f' is changed to this:

function f()
  integer, allocatable :: f

  allocate(f)
  f =3D 123
  deallocate(f)
end function

Is the program still invalid? gfortran -Wall doesn't complain in this case,=
 but
I get a SIGSEGV instead of SIGABRT.=