This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [Patch, Fortran] PR 39996: Double typing of function results not detected
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Janus Weil <janus at gcc dot gnu dot org>
- Cc: gfortran <fortran at gcc dot gnu dot org>, gcc patches <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 12 May 2009 15:22:01 -0700
- Subject: Re: [Patch, Fortran] PR 39996: Double typing of function results not detected
- References: <854832d40905090954m4b15450fj4e5c4aaff4c1cbd1@mail.gmail.com>
On Sat, May 09, 2009 at 06:54:08PM +0200, Janus Weil wrote:
>
> In my opinion it is hard enough to build a compiler which is able to
> check pedantically if a given program is valid with respect to F95,
> F2003 and/or F2008. So there is need for us to invent yet another
s/is need/is no need/
I agree!
> (GNU) version of the standard, and we should really avoid this!
>
> 2009-05-09 Janus Weil <janus@gcc.gnu.org>
>
> PR fortran/39996
> * decl.c (gfc_match_function_decl): Use gfc_add_type.
> * symbol.c (gfc_add_type): Better checking for duplicate types in
> function declarations. And: Always give an error for duplicte types,
> not just a warning with -std=gnu.
>
>
> 2009-05-09 Janus Weil <janus@gcc.gnu.org>
>
> PR fortran/39996
> * gfortran.dg/func_decl_2.f90: Modified (replacing warnings by errors).
> * gfortran.dg/duplicate_type_2.f90: Ditto.
> * gfortran.dg/duplicate_type_3.f90: New.
OK.
--
Steve