Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sources DOT redhat DOT com
To: cygwin AT cygwin DOT com
From: ejrh AT paradise DOT net DOT nz
Subject: Re: Signal handling in tight loops
Date: Tue, 7 Aug 2001 23:33:07 GMT
Message-Id: <20010807233307.3FC3F1F9E2D@deborah.paradise.net.nz>

> Why don't you write a simple test case?

Because I am at work where I don't have cygwin, or any compiler of any 
form for that matter.

> This technique should be much more useful than inviting random opinions
> from a mailing list and it should be MUCH faster.

I've only had one random opinion so far.  :)

Original question:
> > the alarm signal could not be raised in very tight loops, because
> > signals were only checked when memory was accessed.  Does this apply
> > to cygwin, by any chance?


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/