This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


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

Re: Signal handling in tight loops


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


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