From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 251123858C2C; Mon, 17 Apr 2023 12:14:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 251123858C2C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1681733653; bh=SaUBVKHIAfQzFxaLi44i7grD/YbGorVEdKIma/nlEBA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ikxayjo8CIUnXkTsFsinHcBWouU4xGQyhDaxLy9JUVqQpRmvmZj6pOxgFIy95zmbi wUgcJ9iaJif0kM9OCYCc71yGA8wmEtXmYNHWmZ6ObNVJWP6quPGGSN9ENSx4hqXbtd 1pheY0lZApVGQY5iqRKCyQ7brAsahpAvqBroBoGY= From: "leandro.lupori at linaro dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/109500] SIGABRT when calling a function that returns an unallocated value Date: Mon, 17 Apr 2023 12:14:12 +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: leandro.lupori at linaro dot 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 #10 from Leandro Lupori --- Wouldn't it be better to turn this into a warning? Although using the result of a function as an allocatable argument doesn't conform with Fortran standards, it has been supported by gfortran for quite some time. This change may break existing code.=