This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch, libgfortran] [4.3/4.4/4.5 Regression] I/O: Problems reading partial records in formatted direct access files

From: Jerry DeLisle <jvdelisle at verizon dot net>
To: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
Cc: gfortran list <fortran at gcc dot gnu dot org>, gcc patches <gcc-patches at gcc dot gnu dot org>
Date: Wed, 18 Nov 2009 20:47:00 -0800
Subject: Re: [patch, libgfortran] [4.3/4.4/4.5 Regression] I/O: Problems reading partial records in formatted direct access files
References: <4B04C762.6080904@verizon.net> <20091119042727.GA51135@troutmask.apl.washington.edu>

On 11/18/2009 08:27 PM, Steve Kargl wrote:

On Wed, Nov 18, 2009 at 08:19:46PM -0800, Jerry DeLisle wrote:
Hi Folks,
This patch is fairly straight forward.  We were calling skip_record telling
it to skip 0 bytes.  Then in skip_record we tested for zero bytes and
returned, doing nothing.  I guess we never thought of a partial read
before. ;)
Regression tested on X86-64 linux.

Test case provided.

OK for trunk and 4.4 and 4.3?
OK. Are we still "supporting" 4.3?

Not too sure on 4.3. I am not even sure the patch would be the same there, but I will check.

Jerry

Follow-Ups:
- Re: [patch, libgfortran] [4.3/4.4/4.5 Regression] I/O: Problems reading partial records in formatted direct access files
  - From: Tobias Burnus

References:
- [patch, libgfortran] [4.3/4.4/4.5 Regression] I/O: Problems reading partial records in formatted direct access files
  - From: Jerry DeLisle
- Re: [patch, libgfortran] [4.3/4.4/4.5 Regression] I/O: Problems reading partial records in formatted direct access files
  - From: Steve Kargl

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]