[Bug fortran/36795] crash with character allocatable array argument

2008-10-21 Thread pault at gcc dot gnu dot org
--- Comment #7 from pault at gcc dot gnu dot org 2008-10-21 18:58 --- (In reply to comment #6) > I wonder if this bug can be closed, the testcase appears to work with trunk > Joost, I don't know what happened here. I have made a testsuite case out of the original and will commit it t

[Bug fortran/36795] crash with character allocatable array argument

2008-10-21 Thread pault at gcc dot gnu dot org
--- Comment #8 from pault at gcc dot gnu dot org 2008-10-21 20:28 --- Subject: Bug 36795 Author: pault Date: Tue Oct 21 20:27:27 2008 New Revision: 141277 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=141277 Log: 2008-10-21 Paul Thomas <[EMAIL PROTECTED]> PR libfortr

[Bug fortran/36795] crash with character allocatable array argument

2008-10-21 Thread pault at gcc dot gnu dot org
--- Comment #9 from pault at gcc dot gnu dot org 2008-10-21 20:30 --- Fixed on trunk as per #7. Thanks for the report Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added --

[Bug fortran/36795] crash with character allocatable array argument

2008-07-10 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2008-07-11 06:00 --- The problem is: call foo((xx),xx) gfortran simplifies the "(xx)" to "xx" by passing (-fdump-tree-orignal): foo (&xx, &xx, 10, 10); Since the second argument is nullified in "foo" as it is INTENT(OUT), it is obv

[Bug fortran/36795] crash with character allocatable array argument

2008-07-10 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2008-07-11 06:14 --- Looking at PR 36803, I think the general algorithm could be correct, however, it might not trigger for CHARACTER arrays. Maybe a fix for either PRs fixes both. -- burnus at gcc dot gnu dot org changed:

[Bug fortran/36795] crash with character allocatable array argument

2008-07-17 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2008-07-17 21:09 --- *** Bug 36803 has been marked as a duplicate of this bug. *** -- burnus at gcc dot gnu dot org changed: What|Removed |Added -

[Bug fortran/36795] crash with character allocatable array argument

2008-07-17 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2008-07-17 21:12 --- The problem is the following in matchexp.c: gfc_get_parentheses (gfc_expr *e) { gfc_expr *e2; /* This is a temporary fix, awaiting the patch for various other character problems. The resolution and transla

[Bug fortran/36795] crash with character allocatable array argument

2008-07-19 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2008-07-19 18:30 --- Subject: Bug 36795 Author: burnus Date: Sat Jul 19 18:29:18 2008 New Revision: 137986 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137986 Log: 2008-07-19 Tobias Burnus <[EMAIL PROTECTED]> PR fort

[Bug fortran/36795] crash with character allocatable array argument

2008-08-08 Thread jv244 at cam dot ac dot uk
--- Comment #6 from jv244 at cam dot ac dot uk 2008-08-08 22:33 --- I wonder if this bug can be closed, the testcase appears to work with trunk -- jv244 at cam dot ac dot uk changed: What|Removed |Added -