From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29047 invoked by alias); 21 Feb 2007 13:53:41 -0000 Received: (qmail 29023 invoked by uid 48); 21 Feb 2007 13:53:32 -0000 Date: Wed, 21 Feb 2007 13:53:00 -0000 Message-ID: <20070221135332.29022.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/30873] ENTRY without explict RESULT does not work for recursive functions In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "burnus 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: 2007-02/txt/msg02456.txt.bz2 ------- Comment #3 from burnus at gcc dot gnu dot org 2007-02-21 13:53 ------- > Removing the error call > if (proc->attr.recursive && result == NULL) > { > gfc_error ("RESULT attribute required in ENTRY statement at %C"); > return MATCH_ERROR; > } > at decl.c:3032 fixes the problem. This is a very old check. I could trace it back to: r69825: * gcc/fortran: New front end. I just checked the current g95 source code and it also doesn't contain this error anymore. > I guess that there is a testsuite case for this? I have not regtested it. > This looks to me as if it is a mis-interpretation or simplification of the > standard - it had better be checked. I just comment it and run a make check-gfortran, which succeeded. Maybe one should re-read the ENTRY section of the standard and try to come up with something which is not covered, but I think this patch has no unwanted side effects. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30873