From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C52A73858002; Mon, 20 Mar 2023 14:48:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C52A73858002 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1679323693; bh=SM07+OUYvw6m3xuVRLA4onv9Pvdpaer7CAttEQkh7yk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=eYZICfq4ywu7KltTXWpukBzc/vevjFzzXzpBYPO6G0hN4N9mhZAG/4A308vy0GEYh ArTuY1TszxuPYjVFdKa1fVRt1VjXiE6Lgbtm7M5DMxhlqyk+tKvV91r5ej3q3uHndX FGfcJdngOsywAzECBMnf3M5CXtLe+r5N8iJ4l3DI= From: "vegard.g.j at icloud dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/82943] [F03] Error with type-bound procedure of parametrized derived type Date: Mon, 20 Mar 2023 14:48:11 +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.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: vegard.g.j at icloud dot com 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=3D82943 vegard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vegard.g.j at icloud dot c= om --- Comment #10 from vegard --- (In reply to kargl from comment #9) > (In reply to alig from comment #8) > > The problem still persists with GNU Fortran (GCC) 11.1.0. >=20 > The problem is likely to persist for the foreseeable future > as there is no one left to work on gfortran bugs. Lacking=20 > a sudden influx of new volunteer contributors, it seems > the only way forward is to NOT use parameterized derived=20 > types with gfortran. Any news here? I seem to be having this issue with gfortran (Homebrew GCC) 12.2.0 As a side note: I'm somewhat new to the fortran community, but could see my= self contributing to gfortran in the future. Do you think you could point me to where I should read up on contributing?=