public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kishore96 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107031] New: endfile truncates file at wrong position
Date: Sun, 25 Sep 2022 06:34:45 +0000	[thread overview]
Message-ID: <bug-107031-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107031
           Summary: endfile truncates file at wrong position
           Product: gcc
           Version: 12.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: kishore96 at gmail dot com
  Target Milestone: ---

SUMMARY
-------
When `endfile` is used to truncate a file after a read statement, gfortran
wrongly inserts end-of-file after the next line, rather than after the current
line.

STEPS TO REPRODUCE
------------------
1. create the following program, truncate.f90:
```fortran
program test_truncate
    integer :: num_rec, tmp, i, ioerr

    open(1, file="in.dat", action='readwrite')

    num_rec = 5
    i = 1
    ioerr = 0
    do while (i <= num_rec .and. ioerr == 0)
        read(1, *, iostat=ioerr) tmp
        i = i+1
    enddo

    !backspace(1)
    endfile(1)
    close(1)
end program test_truncate
```

2. Create the following text file, `in.dat`
```
1
2
3
4
5
6
7
8
9
10
```

3. Compile the program: `gfortran truncate.f90`

4. Run the program: `./a.out`

OBSERVED RESULTS
----------------
```bash
$cat in.dat
1
2
3
4
5
6
```

EXPECTED RESULTS
----------------
```bash
$cat in.dat
1
2
3
4
5
```

Since after the end of the loop, the current record is `5`, one would expect
endfile to write an end-of-file record as the next record (e.g.
<https://docs.oracle.com/cd/E19957-01/805-4939/6j4m0vn8v/index.html>), leading
to the result above.

SOFTWARE VERSIONS
-----------------
OS: Arch Linux
gfortran: 12.2.0


ADDITIONAL INFORMATION
----------------------
Intel ifort (version 19.0.5.281 20190815) produces the expected result.

May be related to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52387, but I
think not, since my example program doesn't use nonadvancing reads anywhere.

Uncommenting the `backspace(1)` gives output
```bash
$cat in.dat
1
2
3
4
```

             reply	other threads:[~2022-09-25  6:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25  6:34 kishore96 at gmail dot com [this message]
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
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@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).