From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EBAC53858D32; Mon, 30 Oct 2023 20:05:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EBAC53858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1698696354; bh=FLU6IbBACpkQIPqQK6P8/NPofcCyTPsc4U44ZKzEBVc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=sBzybVjg+eDjvkIc9Ho3kwybVuemYb3omDMRAeshbqYipP1L4JdBeDggJFu95CAQy 06jjqtjrPeps7kKD9jCz7ztnzqoHbxgudqIWkcAPyIxcKEpaGnbiWIUwLSXiVVzGwy pZpIWmApmTost85skyRK9wRSgFAdaLjNzM64QC0c= From: "matthew.thompson at nasa dot gov" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/110415] (Re)allocation on assignment to allocatable polymorphic variable from allocatable polymorphic function result Date: Mon, 30 Oct 2023 20:05:54 +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: 13.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: matthew.thompson at nasa dot gov 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: 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=3D110415 Matt Thompson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthew.thompson at nasa d= ot gov --- Comment #2 from Matt Thompson --- I was about to file a bug, but I was pointed to search for bug by Brad Richardon and...yep, this is the one we hit. We found it in one of our base layers, yaFyaml: https://github.com/Goddard-Fortran-Ecosystem/yaFyaml but it's a paradigm we use in codes that use this as well, so... Thus, +1 from me and I can confirm this is still a bug in 13.2.0. I haven't tried GNU 14, but I'm guessing since this is still at "NEW" it would be an issue there as well.=