[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.1.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264
[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2005-12-19 07:22 --- Fixed in 4.1 and 4,2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264
[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2005-12-18 08:32 --- Subject: Bug 25264 Author: jvdelisle Date: Sun Dec 18 08:32:09 2005 New Revision: 108745 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108745 Log: 2005-12-17 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/25264 PR libgfortran/25349 * gfortran.dg/tl_editing.f90: Added additional checks. * gfortran.dg/t_editing.f: New test. * gfortran.dg/write_padding.f90: New test Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/t_editing.f branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/write_padding.f90 Modified: branches/gcc-4_1-branch/gcc/testsuite/ChangeLog branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/tl_editing.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264
[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2005-12-18 08:24 --- Subject: Bug 25264 Author: jvdelisle Date: Sun Dec 18 08:24:04 2005 New Revision: 108744 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108744 Log: 2005-12-17 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/25264 PR libgfortran/25349 * io/unit.c (get_unit): Delete code that cleared the string when the unit was opened, which is too soon. * io/transfer.c (next_record_w): Pass done flag in. Change logic for setting max_pos. Add code to position unit and pad record as needed. Modified: branches/gcc-4_1-branch/libgfortran/ChangeLog branches/gcc-4_1-branch/libgfortran/io/transfer.c branches/gcc-4_1-branch/libgfortran/io/unit.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264
[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2005-12-16 19:40 --- Subject: Bug 25264 Author: jvdelisle Date: Fri Dec 16 19:40:36 2005 New Revision: 108673 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108673 Log: 2005-12-16 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/25264 PR libgfortran/25349 * gfortran.dg/tl_editing.f90: Added additional checks. * gfortran.dg/t_editing.f: New test. * gfortran.dg/write_padding.f90: New test Added: trunk/gcc/testsuite/gfortran.dg/t_editing.f trunk/gcc/testsuite/gfortran.dg/write_padding.f90 Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/tl_editing.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264
[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2005-12-16 19:32 --- Subject: Bug 25264 Author: jvdelisle Date: Fri Dec 16 19:32:21 2005 New Revision: 108671 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108671 Log: 2005-12-16 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/25264 PR libgfortran/25349 * io/unit.c (get_unit): Delete code that cleared the string when the unit was opened, which is too soon. * io/transfer.c (next_record_w): Pass done flag in. Change logic for setting max_pos. Add code to position unit and pad record as needed. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/transfer.c trunk/libgfortran/io/unit.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264
[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2005-12-16 09:05 --- Patch submitted for review and approval. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264
[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2005-12-11 08:09 --- Patch submitted for approval. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264
[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-12-11 00:32 --- I have this beastie beat. The fix of the initial problem caused no less than 10 regressions (I estimate) and so I had to unmangle that. Talk about head spinning. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264
[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-12-07 05:16 --- I have found the offending code. I am working on the fix. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264
[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-12-06 03:21 --- I can confirm this behavior disagrees with ifort. I will investigate further. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added CC||jvdelisle at gcc dot gnu dot ||org AssignedTo|unassigned at gcc dot gnu |jvdelisle at gcc dot gnu dot |dot org |org Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2005-12-06 03:21:42 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264
