From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31315 invoked by alias); 25 May 2008 16:37:50 -0000 Received: (qmail 31244 invoked by uid 48); 25 May 2008 16:37:07 -0000 Date: Sun, 25 May 2008 16:37:00 -0000 Message-ID: <20080525163707.31243.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "janus at gcc dot gnu dot org" 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: 2008-05/txt/msg01862.txt.bz2 ------- Comment #4 from janus at gcc dot gnu dot org 2008-05-25 16:37 ------- (In reply to comment #2) > Others testcases (like argument_checking_3.f90) fail because they define lots > of specific interfaces, but no external implementation for those. Obviously I got this wrong. The actual reason for these tests failing is that with my patch all the interfaces acquire the EXTERNAL attribute (which they didn't have before), and apparently there is no argument checking done for external procedures. Which leads me to think we should probably implement this (for the case that the interface is explicit). Or is there any good reason that this is not done? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36325