From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D9EC73858D37; Thu, 20 Apr 2023 19:04:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D9EC73858D37 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1682017464; bh=NzWAKZ5vCkTc9bgMAHu4OJrae0UwbZNEOVFmxQQVioA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KeTDr3etj2zUwY+2T3OUU/UxlsLpLju42O9Eu+WSyAO83NLiXrRa3iJ7wLDNtjXwo 6R11CliOtqj/snQPz7P93AbZsDflCEc355KZ3jSqrQ86TRjvLsga3AsJaKh++LtCxs DS/fBXzhJLJVdvM1qBOuApWZCMV9NOZyMnGSLqCU= From: "anlauf at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/109500] SIGABRT when calling a function that returns an unallocated value Date: Thu, 20 Apr 2023 19:04:24 +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: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109500 --- Comment #21 from anlauf at gcc dot gnu.org --- (In reply to Steve Kargl from comment #19) > PS: I think what you want to with a runtime check and an undefine > function result is a good idea. I haven't looked to see where > and how hard this might be to implement. I am considering to create a separate PR to track this.=