From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2534B3858D38; Sun, 26 Jul 2020 20:43:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2534B3858D38 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1595796197; bh=5u5cyZr0+plg9v48hKxLkZuDORDaDnD4zEQ8prTQgAI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=VAXfoHUJTQEYskGdPT92OiUpPoVCdwEvZ1oY9mObNPmq21GIrAajZBdoRSI7jYuSm xAmnmQndytelLlKHGCNzN+VgRx3TyLKuBHjjscDoUrlTJhcTHlAB04ggxArbkDmHfn rLX//xs2xevTGYtTym05XYkshmGAUHldpM/2JVyY= From: "chilikin.k at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/96325] Invalid call of a type-bound procedure is accepted Date: Sun, 26 Jul 2020 20:43:17 +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: chilikin.k at gmail dot com 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jul 2020 20:43:17 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96325 --- Comment #2 from Kirill Chilikin --- Yes, there is no type-bound procedure really, and, yes, there is a bug in t= he code (intentionally: it was called for the wrong variable, which is removed= for the test case). The module M2 indeed does not use anything from M1 (due to simplification of the real code). And, yes, the gfortran should tell that t= his statement is not classifiable - 8.3.0 does this, but 10.2.0 successfully compiles the code without reporting any error.=