From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9373A3858C50; Fri, 17 Mar 2023 22:41:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9373A3858C50 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1679092890; bh=BOXCvXn2MjoLEF9R8jjIrGivkMGO4myMpYwtHT1orJg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ilvHvXk93mnqoWtLBn+Fbl7QYi1ncfkoKEEK9g55AdQJJ03SFtUBEhT59jh+iu8Fe 7cYI8yCFj+hnBquKPKhCFELoxlqnFArUHCO/4THJklP1KsWgOcDj3g5Jqs+mz5Qyt1 ZAP9GOvpjHbZHOqnC3UIfthxN85uuMWU7y8g4F9U= From: "urbanjost at comcast dot net" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/109171] initialization using %re causes segfault, as an assignment does not Date: Fri, 17 Mar 2023 22:41: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.2.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: urbanjost at comcast dot net X-Bugzilla-Status: NEW 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: 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=3D109171 --- Comment #3 from urbanjost at comcast dot net --- When you said you thought it was a duplicate I spent some time rechecking, and I think this is covered by 50991? Very different keywords and example, but if no pointer allocation is working at all, this is just a case of that more generic issue?=