[Bug fortran/40045] ICE with type extension and -fdump-parse-tree

2009-05-14 Thread domob at gcc dot gnu dot org
--- Comment #5 from domob at gcc dot gnu dot org 2009-05-14 20:03 --- Subject: Bug 40045 Author: domob Date: Thu May 14 20:02:46 2009 New Revision: 147540 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=147540 Log: 2009-05-14 Daniel Kraft d...@domob.eu PR fortran/40045

[Bug fortran/40045] ICE with type extension and -fdump-parse-tree

2009-05-14 Thread domob at gcc dot gnu dot org
--- Comment #6 from domob at gcc dot gnu dot org 2009-05-14 20:05 --- Fixed (not addressing the related part in comment #2, but Janus promised to work on it). -- domob at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/40045] ICE with type extension and -fdump-parse-tree

2009-05-06 Thread dominiq at lps dot ens dot fr
--- Comment #1 from dominiq at lps dot ens dot fr 2009-05-06 14:31 --- Confirmed and this is regression with repect to 4.4.0: [karma] f90/bug% gfc -fdump-parse-tree pr40045.f90 Namespace: A-H: (REAL 4) I-N: (INTEGER 4) O-Z: (REAL 4) procedure name = MAIN__

[Bug fortran/40045] ICE with type extension and -fdump-parse-tree

2009-05-06 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2009-05-06 14:39 --- Regarding the segfault, valgrind shows: ==14376== Invalid read of size 1 ==14376==by 0x616A4F7: fprintf (in /lib64/libc-2.9.so) ==14376==by 0x4B4BF1: show_typebound (dump-parse-tree.c:693) The line is:

[Bug fortran/40045] ICE with type extension and -fdump-parse-tree

2009-05-06 Thread janus at gcc dot gnu dot org
--- Comment #3 from janus at gcc dot gnu dot org 2009-05-06 14:58 --- (In reply to comment #2) and the interesting question is: Why is it called? There are no type-bound procedures (and also no components [except of t2%t]. If it's a regression it may be caused by Daniel's r146733

[Bug fortran/40045] ICE with type extension and -fdump-parse-tree

2009-05-06 Thread domob at gcc dot gnu dot org
--- Comment #4 from domob at gcc dot gnu dot org 2009-05-06 15:01 --- Yes, that sounds like a problem caused by my patch; it did change the structure of storing the type-bounds, so maybe simply changing the if to the one shown by Tobias was wrong. I will look into this! -- domob at