This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH, libgfortran] PR 67585 Handle EINTR

From: Mike Stump <mikestump at comcast dot net>
To: FX <fxcoudert at gmail dot com>
Cc: Janne Blomqvist <blomqvist dot janne at gmail dot com>, fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Date: Fri, 7 Oct 2016 12:18:39 -0700
Subject: Re: [PATCH, libgfortran] PR 67585 Handle EINTR
Authentication-results: sourceware.org; auth=none
References: <1475843186-3429-1-git-send-email-blomqvist.janne@gmail.com> <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.

References:
- [PATCH, libgfortran] PR 67585 Handle EINTR
  - From: Janne Blomqvist
- Re: [PATCH, libgfortran] PR 67585 Handle EINTR
  - From: FX

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]