public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: FX <fxcoudert@gmail.com>
Cc: Janne Blomqvist <blomqvist.janne@gmail.com>,
	fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, libgfortran] PR 67585 Handle EINTR
Date: Fri, 07 Oct 2016 19:18:00 -0000	[thread overview]
Message-ID: <BB657D24-1762-4B01-B6BA-96B838959EE4@comcast.net> (raw)
In-Reply-To: <F04C59DD-1F6D-4E26-AC2E-A1981551A555@gmail.com>

On Oct 7, 2016, at 5:41 AM, FX <fxcoudert@gmail.com> wrote:
> 
>> Many POSIX systems have the bad habit of not restarting interrupted
>> syscalls. On these systems it's up to the user to check for an error
>> with errno == EINTR and restart manually. This patch does this for
>> libgfortran, so that GFortran users don't have to do it.
> 
> I have not much experience with EINTR, but is it garanteed that those EINTR loops will never cycle forever?

They will not.  You get at most 1 for 1 signal, sometimes less.  If you have a finite number of signals, you will have a finite number of loops.

  parent reply	other threads:[~2016-10-07 19:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 12:26 Janne Blomqvist
2016-10-07 12:41 ` FX
2016-10-07 12:59   ` Janne Blomqvist
2016-10-07 14:50     ` Fritz Reese
2016-10-07 16:09       ` Janne Blomqvist
2016-10-07 16:42         ` Jack Howarth
2016-10-07 19:55           ` Mike Stump
2016-10-07 19:46       ` Mike Stump
2016-10-07 19:26     ` Mike Stump
2016-10-07 19:18   ` Mike Stump [this message]
2016-10-09 13:59 ` [PATCH] " Janne Blomqvist

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=BB657D24-1762-4B01-B6BA-96B838959EE4@comcast.net \
    --to=mikestump@comcast.net \
    --cc=blomqvist.janne@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.com \
    --cc=gcc-patches@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).