public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/107031] endfile truncates file at wrong position
Date: Mon, 26 Sep 2022 00:18:31 +0000	[thread overview]
Message-ID: <bug-107031-4-icKf8UPHzU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107031-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107031

--- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Sun, Sep 25, 2022 at 08:56:22PM +0000, kargl at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107031
> 
> --- Comment #4 from kargl at gcc dot gnu.org ---
> (In reply to anlauf from comment #3)
> > (In reply to kargl from comment #2)
> > > gfortran's current behavior is correct.
> > > 
> > > 
> > >    12.3.4.4 File position after data transfer
> > > 
> > >    In all other cases, the file is positioned after the record just
> > >    read or written and that record becomes the preceding record.
> > > 
> > >    12.8.3 ENDFILE statement
> > > 
> > >    Execution of an ENDFILE statement for a file connected for sequential
> > >    access writes an endfile record as the next record of the file.
> > > 
> > > After reading '5', the file is position at the record that contains '6'.
> > > So, ENDIFLE writes the endfile record after the record with '6'.
> > 
> > Hmm, interpretation of text?
> > 
> > I read "as the next record", not "after the next record".
> > 
> > gfortran differs here from Intel, NAG, Nvidia, AMD Flang, Crayftn.
> 
> If the current record contain '6', the next record contains '7'.
> 'next' does not mean 'current' in the English language.  It means
> something that 'follows'.
> 

Further confusion, maybe?

12.3.4 File position

12.3.4.1 General
...
Let n be the number of records in the file.
...
If 1 <= i < n and a file is positioned within the ith record or
between the ith and (i + 1)th record, the (i + 1)th record is the
next record.

  parent reply	other threads:[~2022-09-26  0:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25  6:34 [Bug fortran/107031] New: " kishore96 at gmail dot com
2022-09-25 19:21 ` [Bug libfortran/107031] " anlauf at gcc dot gnu.org
2022-09-25 19:46 ` kargl at gcc dot gnu.org
2022-09-25 20:07 ` anlauf at gcc dot gnu.org
2022-09-25 20:56 ` kargl at gcc dot gnu.org
2022-09-26  0:18 ` sgk at troutmask dot apl.washington.edu [this message]
2022-09-26 14:33 ` kargl at gcc dot gnu.org
2024-03-26  0:13 ` urbanjost at comcast dot net
2024-03-26  0:38 ` jvdelisle at gcc dot gnu.org
2024-03-26  1:51 ` jvdelisle at gcc dot gnu.org
2024-03-27  0:17 ` cvs-commit at gcc dot gnu.org
2024-04-10  2:41 ` jvdelisle at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-107031-4-icKf8UPHzU@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).