[Bug fortran/33499] Rejects valid module with a contained function with an ENTRY

2007-11-25 Thread pault at gcc dot gnu dot org
--- Comment #11 from pault at gcc dot gnu dot org 2007-11-25 19:05 --- Fixed on trunk Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added Statu

[Bug fortran/33499] Rejects valid module with a contained function with an ENTRY

2007-11-25 Thread pault at gcc dot gnu dot org
--- Comment #10 from pault at gcc dot gnu dot org 2007-11-25 09:59 --- Subject: Bug 33499 Author: pault Date: Sun Nov 25 09:59:42 2007 New Revision: 130403 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=130403 Log: 2007-11-25 Paul Thomas <[EMAIL PROTECTED]> PR fortran

[Bug fortran/33499] Rejects valid module with a contained function with an ENTRY

2007-11-24 Thread patchapp at dberlin dot org
--- Comment #9 from patchapp at dberlin dot org 2007-11-24 11:10 --- Subject: Bug number PR33499 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-11/msg01273.html -- http://gcc.gnu.org/bugzilla/sh

[Bug fortran/33499] Rejects valid module with a contained function with an ENTRY

2007-11-23 Thread pault at gcc dot gnu dot org
--- Comment #8 from pault at gcc dot gnu dot org 2007-11-23 14:13 --- This is not regtested yet but seems to be OK: Index: gcc/fortran/decl.c === *** gcc/fortran/decl.c (révision 130286) --- gcc/fortran/decl.c (copie de t

[Bug fortran/33499] Rejects valid module with a contained function with an ENTRY

2007-11-23 Thread pault at gcc dot gnu dot org
--- Comment #7 from pault at gcc dot gnu dot org 2007-11-23 10:59 --- A workaround is to put the ENTRY declaration after the type specification: MODULE complex IMPLICIT NONE PRIVATE PUBLIC :: cx, OPERATOR(+) TYPE cx REAL :: imag END TYPE cx INTERFACE OPERATOR (+) MOD

[Bug fortran/33499] Rejects valid module with a contained function with an ENTRY

2007-10-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2007-10-26 03:15 --- I was in error, the function of interest is resolve_entries, here if the type is BT_UNKNOWN an attempt is made to get the type from the corresponding result. In this case the result is also BT_UNKNOWN. -- ht

[Bug fortran/33499] Rejects valid module with a contained function with an ENTRY

2007-10-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-10-26 02:22 --- FrRom my brief explorations, in resolve.c (resolve_entries) on or about line 560, we are NOT addressing the case for BT_DERIVED in the switch statement. If there we set sym = NULL for BT_DERIVED, we get past this

[Bug fortran/33499] Rejects valid module with a contained function with an ENTRY

2007-10-10 Thread tobi at gcc dot gnu dot org
--- Comment #4 from tobi at gcc dot gnu dot org 2007-10-10 20:15 --- Created an attachment (id=14337) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14337&action=view) A small cleanup patch -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33499

[Bug fortran/33499] Rejects valid module with a contained function with an ENTRY

2007-10-10 Thread tobi at gcc dot gnu dot org
--- Comment #3 from tobi at gcc dot gnu dot org 2007-10-10 20:12 --- The problem is that at the time we enter resolve_entries cx_radc has type BT_UNKNOWN. I have no idea why that's the case. Removing the interface fixes this. It's also a QOI issue that an error message about the maste