From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2109 invoked by alias); 25 May 2008 22:33:59 -0000 Received: (qmail 1979 invoked by uid 48); 25 May 2008 22:33:16 -0000 Date: Sun, 25 May 2008 22:33:00 -0000 Message-ID: <20080525223316.1978.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/msg01893.txt.bz2 ------- Comment #8 from janus at gcc dot gnu dot org 2008-05-25 22:33 ------- The failure of proc_decl_9.f90 was actually due to a bug that slipped in with my procedure declaration update patch from May 1st, which I have fixed now. So we're left with gomp/reduction3.f90, which contains this piece of code: interface function ior (a, b) integer :: ior, a, b end function end interface intrinsic ior This produces: intrinsic ior 1 Error: EXTERNAL attribute conflicts with INTRINSIC attribute at (1) I haven't checked the standard on this, but I bet the code is illegal. And after all: Why should one declare an explicit interface for an intrinsic (whose interface is known anyway) ...? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36325