public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/98129] Failure on reading big chunk of /dev/urandom
Date: Fri, 22 Jan 2021 12:12:02 +0000	[thread overview]
Message-ID: <bug-98129-4-4LkpkIxBns@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98129-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #12)
> I had one (random?) failure with append_1.f90 which I am unable to reproduce.

Likely origin: parallel make -j4 check-fortran and

% grep -il open.*[\"\']foo[\'\"] gcc/testsuite/gfortran.dg/ -r
gcc/testsuite/gfortran.dg/append_1.f90
gcc/testsuite/gfortran.dg/direct_io_2.f90
gcc/testsuite/gfortran.dg/io_constraints_7.f03
gcc/testsuite/gfortran.dg/large_unit_2.f90
gcc/testsuite/gfortran.dg/open_access_1.f90
gcc/testsuite/gfortran.dg/open_access_append_1.f90
gcc/testsuite/gfortran.dg/open_status_1.f90
gcc/testsuite/gfortran.dg/pr20163-2.f

The additional read seen in the strace output comes from the first read
attempt on the file which is shorter (169 bytes) that the buffer (8k),
so there is another read attempt (returning 0) because of end of file.
So that is a feature of the present fix.

      parent reply	other threads:[~2021-01-22 12:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 20:01 [Bug libfortran/98129] New: " tkoenig at gcc dot gnu.org
2020-12-04 10:41 ` [Bug libfortran/98129] " dominiq at lps dot ens.fr
2020-12-04 12:40 ` tkoenig at gcc dot gnu.org
2020-12-04 12:50 ` tkoenig at gcc dot gnu.org
2020-12-04 15:27 ` kargl at gcc dot gnu.org
2020-12-04 16:17 ` tkoenig at gcc dot gnu.org
2020-12-04 18:16 ` kargl at gcc dot gnu.org
2020-12-04 18:37 ` anlauf at gcc dot gnu.org
2020-12-04 21:32 ` anlauf at gcc dot gnu.org
2020-12-04 22:09 ` anlauf at gcc dot gnu.org
2020-12-04 22:28 ` tkoenig at gcc dot gnu.org
2020-12-04 22:38 ` anlauf at gcc dot gnu.org
2021-01-21 21:58 ` anlauf at gcc dot gnu.org
2021-01-22 12:12 ` anlauf at gcc dot gnu.org [this message]

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-98129-4-4LkpkIxBns@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).