Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
To: cygwin@cygwin.com, cygwin@cygwin.com
From: ejrh@paradise.net.nz
Subject: Re: Signal handling in tight loops
Date: Wed, 8 Aug 2001 00:28:27 GMT
X-Mailer: Endymion MailMan Standard Edition v3.0.26
Message-Id: <20010808002827.9D02F1F9E58@deborah.paradise.net.nz>

> Wow.  You haven't been home for 24 hours?  I hope you're getting
> overtime.

I was at home when I sent the question (some time around midnight, I 
think), but it was here at work that I got your response.

No matter.  Assuming that SIGALRM can't be raised inside loops of the 
form,

L1: jmp L1

what do you say to the idea of parsing the .s files for this sort of 
pattern, and dealing with it there?



--
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/