From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 536B6388211C; Fri, 14 Jun 2024 21:18:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 536B6388211C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1718399901; bh=P21MAlwNnUgHXJTr+jJQP/DNh48wuYVvRV1EPp6Jlfc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=GMHJ2DfF4cRg4EGhGE5ti7dkzAzZFiIf7LQ8T+k7gB7WBlyTzNDBzGvJDGVFj7cxD gM0yOFlzftPdtIqRFvCYO5TBMyoOGAdebGw01Dysjn8aFkSqzXbiQufmYq0JG2B43D jSuAJLvzrocZPQczMz5yGTJMtHHJTvvaa1oOMbho= From: "heinzell at ucar dot edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/115491] Internal compiler error: in resolve_typebound_procedure, at fortran/resolve.cc:14913 Date: Fri, 14 Jun 2024 21:18:20 +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: 14.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: heinzell at ucar dot edu X-Bugzilla-Status: UNCONFIRMED 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=3D115491 --- Comment #2 from Dom Heinzeller --- (In reply to kargls from comment #1) > (In reply to Dom Heinzeller from comment #0) > > I am working on a fairly complicated modeling code used by the U.S. Nav= al > > Research Lab and I am hitting internal compiler errors that prevent us = from > > using gcc. I tested versions 10 through 14 (14.1.0), all with the same > > results. It's going to be complicated to resolve, since I cannot share = the > > code, but hopefully we can find a way to address the problem. >=20 > It seems you'll need to do some old fashion debugging for us. > Compile your code. With the problematic file that causes the ICE, > you'll need to start commenting out chunks. Hopefully, you > can isolate a small example, which can then be posted here. Thanks! That is what I started early today, and I do indeed have an update.= I can get the code to compile if I change the location of Fortran "use" statements. Basically, it looks like this in the failing code: module abc ... end module abc submodule (abc) def contains module procedure xyz use some_overloaded_procedure ! an interface for several type-bound procedures ... end module procedure xyz end submodule def This code, however, works: module abc ... end module abc submodule (abc) def use some_overloaded_procedure ! an interface for several type-bound procedures contains module procedure xyz ... end module procedure xyz end submodule def=