This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: src/winsup/cygwin ChangeLog include/cygwin/sig ...
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-developers at cygwin dot com
- Date: Fri, 26 Oct 2012 17:59:03 +0200
- Subject: Re: src/winsup/cygwin ChangeLog include/cygwin/sig ...
- References: <20121026092149.4969.qmail@sourceware.org> <508AA114.3070007@redhat.com> <20121026144641.GC5582@calimero.vinschen.de>
- Reply-to: cygwin-developers at cygwin dot com
On Oct 26 16:46, Corinna Vinschen wrote:
> On Oct 26 08:41, Eric Blake wrote:
> > On 10/26/2012 03:21 AM, corinna@cygwin.com wrote:
> > > CVSROOT: /cvs/src
> > > Module name: src
> > > Changes by: corinna@sourceware.org 2012-10-26 09:21:49
> > >
> > > Modified files:
> > > winsup/cygwin : ChangeLog
> > > winsup/cygwin/include/cygwin: signal.h
> > >
> > > Log message:
> > > * include/cygwin/signal.h (sigset_t): Define here.
> >
> > >
> > > +typedef __uint32_t sigset_t;
> >
> > Are there plans to widen this to 64 bits for 64-bit cygwin, so that we
> > can finally implement real-time signals as required by POSIX?
>
> Look at the end of
>
> http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/include/cygwin/signal.h.diff?cvsroot=src&only_with_tag=cygwin-64bit-branch&r1=1.19.4.1&r2=1.19.4.2
>
> ABI changes galore, just as with time_t. Somebody has to... well, you
> know.
Oh btw.
Linux defines all signals beyond SIGRTMIN as RT signals. Do we follow
the lead or is there some good reason to restrict the number of RT
signals to keep space for later extensions?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat