This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/67585] Retry system calls failing with EINTR
- From: "dominiq at lps dot ens.fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 15 Sep 2015 13:56:34 +0000
- Subject: [Bug libfortran/67585] Retry system calls failing with EINTR
- Auto-submitted: auto-generated
- References: <bug-67585-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67585
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2015-09-15
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> libgfortran should retry system calls failing with EINTR, with the exception
> of close(). Rationale and further reading e.g. at
> https://www.python.org/dev/peps/pep-0475/
I don't understand what is expected. The only place where EINTR is used is in
raw_write file io/unix.c with a comment
/* We must write in a loop since some systems don't restart system
calls in case of a signal. */
For raw_read, the comment is
/* For read we can't do I/O in a loop like raw_write does, because
that will break applications that wait for interactive I/O. */