From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 780443858D33; Fri, 31 Mar 2023 07:04:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 780443858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1680246273; bh=qGIv9j/a+ZWc8gkiBwbLq41NkSLcDpMWCP9QAyRg5GY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=qif+7pEHxr5AO1K3NWfuSs/E4mcO0LULYCsS7lfOMWz2t6ux/vAC96qhJ5zBiVGLJ lo4qErISgptEdD7Y2/67ZquTqJBKOr95tqMhTSMKryByyV3xN2BxwLe/3HgJwG3686 Xqpv7SOJFP3Sbo89OkuMMYrgir0a5sPLcYNKBXuY= From: "pault at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/101047] Pointer explicit initialization fails Date: Fri, 31 Mar 2023 07:04:32 +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: patch, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: pault at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jrfsousa at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_reconfirmed_on bug_status everconfirmed cc 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=3D101047 Paul Thomas changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-03-31 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC| |pault at gcc dot gnu.org --- Comment #4 from Paul Thomas --- (In reply to Jerry DeLisle from comment #3) > Did we let this fall in a crack or was there some other holdup? I cannot speak for anybody else but it came up during my long break from gfortran support and so I certainly missed it. I feel that this is sufficiently obtrusive that it will have to wait for 14= .0.0 to open. That said, I have put it on my TODO list to review. I discovered that pointer initialization is an issue just yesterday after taking a peek at recent posts by Peter Klausler on clf. Paul=