This is the mail archive of the cygwin-developers 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] |
Other format: | [Raw text] |
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 want to add it to 32-bit cygwin, at which point we will have to tackle the ABI problem, and can therefore tackle the ABI problem in both builds at once. -- Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |