This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: src/winsup/cygwin ChangeLog include/cygwin/sig ...
On Oct 26 12:52, Eric Blake wrote:
> On 10/26/2012 12:29 PM, Corinna Vinschen wrote:
> > If there's no reason to keep space, I would opt for this implementation:
> >
> > #ifdef __x86_64__
> > #define NSIG 65 /* signal 0 implied */
> > #else
> > #define NSIG 33 /* signal 0 implied */
> > #endif
> >
> > /* Real-Time signals per SUSv3. RT_SIGMAX in limits.h has to agree. */
> > #define SIGRTMIN 32
> > #define SIGRTMAX (NSIG - 1)
> >
> > It's not dynamic, but it doesn't seem to make a lot of sense to make it
> > dynamic. Even in the 32 bit case, if we change the number of available
> > RT signals it can also occur together with the ABI change, so an old
> > application would still have the old number of RT signals, despite any
> > effort to make the number dynamic. Me thinks.
>
> Seems reasonable to me - if there is ever a new signal added, we'd also
I don't quite understand. The joke here is that the above would NOT allow
to add any further signal. Ever. Except for more RT signals in the 32
bit case. What am I missing?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat