From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E80F83858D28; Thu, 31 Aug 2023 17:20:11 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E80F83858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1693502411; bh=9jc1JjrG5jjj2l5SiEdJ4iDDbWaN5aobHYFBiygnlSs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=YJanJN2vTJu9yJsO1DDDYQ9IwNhP+SECJW+c5Ak8cwBZWTMWLV9Ct/5QbpwJ2SXYK P3BlVeWryPZjhahCRdcp6X9lSVLiJS0BlpXaQEE8utlEmsPhHuApb79lRF1NfzfDf4 sk8nkFKeOorPaOg7eWwAS+NSN1lrJz65bMMDpQKA= From: "sgk at troutmask dot apl.washington.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/99711] Crash when reading an allocated character array in namelist Date: Thu, 31 Aug 2023 17:20:09 +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: 10.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu 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=3D99711 --- Comment #19 from Steve Kargl = --- On Thu, Aug 31, 2023 at 12:58:15PM +0000, philippe.wautelet at aero dot obs-mip.fr wrote: >=20 > What is the status of this bug? >=20 > It seems that it is not present any more in the 12.x and 13.x GCC version= s. >=20 Looks like it is fixed by the patch for some other bug report. A scan of gcc/fortran/ChangeLog shows a number patches that tinker with the character length for deferred length strings. I don't which one is the responsiblei, and since I don't use=20 git (other than for trivial 'git diff' and 'git pull') doing a bisection is beyond my skillset. Someone should likely convert your testcase into something that the testsuite can digest, and commit it.=