From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11640 invoked by alias); 30 Apr 2013 16:44:40 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 11589 invoked by uid 48); 30 Apr 2013 16:44:36 -0000 From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/57126] Matching host-associated generic vs. same-named use-associated generic Date: Tue, 30 Apr 2013 16:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: CC Summary Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 X-SW-Source: 2013-04/txt/msg02446.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57126 Tobias Burnus changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org Summary|Wrongly rejects a generic |Matching host-associated |call because it doesn't |generic vs. same-named |match the intrinsic while |use-associated generic |another specific matches | --- Comment #1 from Tobias Burnus 2013-04-30 16:44:36 UTC --- For clarification: - ABS and SIZE are both generic names, either having an intrinsic and a user specific procedure. - In "sub", the specific functions of "SIZE" do not match the rejected calls. - The specific functions of "ABS" do match - and both have the same generic name See: USE MOO, ONLY: RENAME => ABS CONTAINS SUBROUTINE SUB USE MOO, ONLY: RENAME => SIZE, T Thus, the question is whether the generic "rename" are merged or whether the inner "rename" overrides the host-associated "rename". If they are merged, the question is how ambiguity is handled.