[Bug fortran/30626] Wrong-code for internal read

2007-02-02 Thread pault at gcc dot gnu dot org
--- Comment #6 from pault at gcc dot gnu dot org 2007-02-02 12:36 --- Subject: Bug 30626 Author: pault Date: Fri Feb 2 12:35:57 2007 New Revision: 121500 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121500 Log: 2007-02-02 Paul Thomas [EMAIL PROTECTED] PR

[Bug fortran/30626] Wrong-code for internal read

2007-02-01 Thread pault at gcc dot gnu dot org
--- Comment #5 from pault at gcc dot gnu dot org 2007-02-01 10:17 --- The fix will be posted to the list, this weekend. Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/30626] Wrong-code for internal read

2007-01-30 Thread pault at gcc dot gnu dot org
--- Comment #2 from pault at gcc dot gnu dot org 2007-01-30 10:56 --- FX, It's funny that you should alight on this one - Last night, I forwarded a patch to Jerry that cures the front-end problems but breaks in transfer.c. As well as the testcase from PR30284, I sent him one that is

[Bug fortran/30626] Wrong-code for internal read

2007-01-30 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2007-01-30 14:36 --- Paul's preliminary patch for pr30284 fixes this bug. The library side still shows a potential problem, but we don't hit it with the test cases here because we are only reading one record. Here is dump for

[Bug fortran/30626] Wrong-code for internal read

2007-01-30 Thread pault at gcc dot gnu dot org
--- Comment #4 from pault at gcc dot gnu dot org 2007-01-30 17:30 --- (In reply to comment #3) Paul's preliminary patch for pr30284 fixes this bug. The library side still shows a potential problem, but we don't hit it with the test cases here because we are only reading one

[Bug fortran/30626] Wrong-code for internal read

2007-01-29 Thread fxcoudert at gcc dot gnu dot org
-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last

[Bug fortran/30626] Wrong-code for internal read

2007-01-29 Thread fxcoudert at gcc dot gnu dot org
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2007-01-29 21:55 --- What's funny is that we create the temporary well (see original dump): static char date[1][1:12] = {200612231200}; { char A.2[1][1:4]; struct array1_unknown atmp.1; atmp.1.dim[0].stride = 1;