From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 96EAE3840914; Wed, 14 Dec 2022 20:54:57 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 96EAE3840914 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1671051297; bh=8o/ImY7s4nLb4u6GOglYDClvWzTT246jkc0NwM0VNbQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=jKOitew606SJJrETXvVVRANzHTdafULqwNbdgUZk1tu0GEo7WCEAj1RqQKTEXuK4j x2S29beCYFaL9WpX5vAONNOvDnekG00GPtpJUItGjfOGOFxi50yEWhjCzipEsu7NVY NoWxThdIrdDcTVeIXIwUJx0HeVs4QLISgLh2x1Xg= From: "anlauf at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/95947] PACK intrinsic returns blank strings when an allocatable character array with allocatable length is used Date: Wed, 14 Dec 2022 20:54:56 +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: 8.3.1 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: anlauf at gcc dot gnu.org 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=3D95947 --- Comment #6 from anlauf at gcc dot gnu.org --- Setting a breakpoint in gfc_resolve_pack, I find for the len=3D: case: (gdb) p *array->ts.u.cl $12 =3D {length =3D 0x0, next =3D 0x2cc7af0, length_from_typespec =3D false, backend_decl =3D 0x0,=20 passed_length =3D 0x0, resolved =3D 1} Not good. I see similar problems for other intrinsics, such as in: m =3D adjustl (m([2])) which later ICEs...=