From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22729 invoked by alias); 28 Oct 2010 15:33:03 -0000 Received: (qmail 22691 invoked by uid 22791); 28 Oct 2010 15:33:01 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,MISSING_MID X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 28 Oct 2010 15:32:57 +0000 From: "janus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/46196] [OOP] gfortran compiles invalid generic TBP: dummy arguments are type compatible X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: janus at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: janus at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: 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 Date: Thu, 28 Oct 2010 15:33:00 -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 X-SW-Source: 2010-10/txt/msg02413.txt.bz2 Message-ID: <20101028153300.yKxVny8ItasjTvP4kFx1REXRYR2WLOnQ4GmRitWyVM0@z> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46196 --- Comment #4 from janus at gcc dot gnu.org 2010-10-28 15:32:44 UTC --- (In reply to comment #3) > With the patch in comment #2, several of my codelets are rejected: for instance > the test in comment #24 of pr42274 is rejected with: > > [macbook] f90/bug% gfc pr42274_5.f90 > pr42274_5.f90:14.33: > > generic, public :: extract => make_integer_2 > 1 > Error: 'make_integer_2' and 'make_integer' for GENERIC 'extract' at (1) are > ambiguous Yes, this is expected. The test case is invalid. > If you need I can sort out the other similar new errors tomorrow. Maybe you could check if there are any 'false alarm' errors among that ...