[Bug libfortran/18891] write with no open causes core dump

[pinskia at gcc dot gnu dot org]

-- 
   What|Removed |Added

   Target Milestone|--- |4.0.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18891

[Bug libfortran/18891] write with no open causes core dump

[pinskia at gcc dot gnu dot org]

-- 
   What|Removed |Added

  Component|fortran |libfortran


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18891

[Bug libfortran/18891] write with no open causes core dump

[sje at cup dot hp dot com]

--- Additional Comments From sje at cup dot hp dot com  2004-12-08 19:06 
---
The same problem exists in next_record_w, there there are two statments of the
form '*((gfc_offset *) p) = m;' and again there is no gaurentee that p is an
aligned address.  These must also be fixed for this test case to run.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18891

[Bug libfortran/18891] write with no open causes core dump

[bdavis at gcc dot gnu dot org]

--- Additional Comments From bdavis at gcc dot gnu dot org  2004-12-09 
09:41 ---
sounds reasonable to me. note that gfc_offset is either a 32 or a 63 bit value
depending on offset_t.

there is a testsuite file to test this exact problem,

unopened_unit_1.f90
! PR 14565
program unopened_unit_1
  Integer I,J
  Do I = 1,10
Write(99,*)I
  End Do
  Rewind(99)
  Do I = 1,10
Read(99,*)J
If (J.ne.I) Call abort
  End Do
End program

so fixing this PR should also fix at least one testsuite failure on you 
platform.

--bud


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18891

[Bug libfortran/18891] write with no open causes core dump

[bdavis at gcc dot gnu dot org]

--- Additional Comments From bdavis at gcc dot gnu dot org  2004-12-09 
12:07 ---
32 or 64 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18891

[Bug libfortran/18891] write with no open causes core dump

[pinskia at gcc dot gnu dot org]

--- Additional Comments From pinskia at gcc dot gnu dot org  2004-12-10 
17:44 ---
Patch here: .

-- 
   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed||1
   Keywords||patch
   Last reconfirmed|-00-00 00:00:00 |2004-12-10 17:44:02
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18891

[Bug libfortran/18891] write with no open causes core dump

[pinskia at gcc dot gnu dot org]

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-01-25 
17:33 ---
Fixed by:
2004-12-14  Steve Ellcey  <[EMAIL PROTECTED]>

* libgfortran/io/transfer.c (us_read): Use memcpy/memset
instead of assignment to fill unaligned buffer.
(us_write): Ditto.
(next_record_w): Ditto.

Next time try placing PR component/bug number in the changelog/commit message 
and bugzilla will 
pick it up automatically.

-- 
   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18891

[Bug libfortran/18891] write with no open causes core dump

[sje at cup dot hp dot com]

--- Additional Comments From sje at cup dot hp dot com  2005-01-25 17:20 
---
The patch for this fix was checked in.  The final patch was:

http://gcc.gnu.org/ml/gcc-patches/2004-12/msg00953.html

Does anything else need to be done for this to be closed?

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18891