[Bug fortran/28722] Fortran front-end produces mismatch trees

2007-11-02 Thread fxcoudert at gcc dot gnu dot org
--- Comment #9 from fxcoudert at gcc dot gnu dot org 2007-11-02 14:55 --- Type-checking is now in mainline, and PR31608 is tracking the last remaining failure exposed in the testsuite. Closing this PR. -- fxcoudert at gcc dot gnu dot org changed: What|Removed

[Bug fortran/28722] Fortran front-end produces mismatch trees

2007-08-24 Thread rguenth at gcc dot gnu dot org
--- Comment #8 from rguenth at gcc dot gnu dot org 2007-08-24 16:03 --- None of the testcases in comment #3 fail on the mainline configured with --enable-checking=yes,types. So either this bug is fixed or the patches from Andrew did some slightly different checking. Or both ;) --

[Bug fortran/28722] Fortran front-end produces mismatch trees

2007-04-10 Thread pault at gcc dot gnu dot org
--- Comment #7 from pault at gcc dot gnu dot org 2007-04-10 09:28 --- (In reply to comment #6) Tobi, > (trans-expr.c:141) which looks like it gets the types right. Replacing the > call to fold_convert with an equivalent call to build_int_cst doesn't help > either, BTW. Does casting th

[Bug fortran/28722] Fortran front-end produces mismatch trees

2007-03-21 Thread tobi at gcc dot gnu dot org
--- Comment #6 from tobi at gcc dot gnu dot org 2007-03-21 15:04 --- I don't understand why it fails in the fourth case. The comparison it seems to complain about is generated via return build2 (NE_EXPR, boolean_type_node, decl, fold_convert (TREE_TYPE (decl), null_po

[Bug fortran/28722] Fortran front-end produces mismatch trees

2007-03-21 Thread tobi at gcc dot gnu dot org
--- Comment #5 from tobi at gcc dot gnu dot org 2007-03-21 14:54 --- Behavior is different with today's mainline on i386-darwin. Without optimization the first one gives an error further down the line, and the other three pass: 1.f90:3: internal compiler error: in simplify_subreg, at si

[Bug fortran/28722] Fortran front-end produces mismatch trees

2006-10-30 Thread fxcoudert at gcc dot gnu dot org
--- Comment #4 from fxcoudert at gcc dot gnu dot org 2006-10-30 08:30 --- (In reply to comment #3) > real c > if (loc(c) == 0) call abort > end This one has been fixed on mainline. -- fxcoudert at gcc dot gnu dot org changed: What|Removed |

[Bug fortran/28722] Fortran front-end produces mismatch trees

2006-10-02 Thread fxcoudert at gcc dot gnu dot org
--- Comment #3 from fxcoudert at gcc dot gnu dot org 2006-10-02 15:24 --- Here's a detailed analysis of the current testsuite failures with Andrew's patches from PR22368 (all patches applied) on i686-linux. First testcase (from actual_array_constructor_1.f90): subroutine bar(a)

[Bug fortran/28722] Fortran front-end produces mismatch trees

2006-08-18 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-08-18 19:13 --- This happens when the first patch in PR 22368 is added. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added -

[Bug fortran/28722] Fortran front-end produces mismatch trees

2006-08-18 Thread pault at gcc dot gnu dot org
--- Comment #1 from pault at gcc dot gnu dot org 2006-08-18 18:28 --- Andrew, How, when and where does this happen, please? Paul -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28722