From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2 4/5] mips: Fix SIGRTMAX definition
Date: Tue, 12 May 2020 18:00:34 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.2005121729290.677301@eddie.linux-mips.org> (raw)
In-Reply-To: <20200507142319.1978172-4-adhemerval.zanella@linaro.org>
On Thu, 7 May 2020, Adhemerval Zanella via Libc-alpha wrote:
> MIPS support up to 96 real time signal, instead of current 95.
[...]
> diff --git a/sysdeps/unix/sysv/linux/mips/bits/signum-arch.h b/sysdeps/unix/sysv/linux/mips/bits/signum-arch.h
> index c500d38322..5eeed367e8 100644
> --- a/sysdeps/unix/sysv/linux/mips/bits/signum-arch.h
> +++ b/sysdeps/unix/sysv/linux/mips/bits/signum-arch.h
> @@ -60,6 +60,9 @@
>
> /* By default no real-time signals are supported. */
> #define __SIGRTMIN 32
> -#define __SIGRTMAX 127
> +#define __SIGRTMAX 128
> +
> +/* MIPS used to define __SIGRTMAX as 127 and exported NSIG as 128. */
> +#define __OLD_NSIG 128
I don't think 128 can reliably work as a signal number as bit 7 in the
exit status denotes a core dump has been made and only bits 6:0 there hold
the signal number, which is why the upper limit of the range has been set
to 127. See also the WTERMSIG and WCOREDUMP macros.
Besides the range of 32..127 actually spans 96 individual signal numbers.
Maciej
next prev parent reply other threads:[~2020-05-12 17:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 14:23 [PATCH v2 1/5] signal: Add signum-{generic,arch}.h Adhemerval Zanella
2020-05-07 14:23 ` [PATCH v2 2/5] signal: Move sys_siglist to a compat symbol Adhemerval Zanella
2020-05-07 14:36 ` Andreas Schwab
2020-05-07 18:21 ` Adhemerval Zanella
2020-05-12 17:36 ` Carlos O'Donell
2020-05-07 14:23 ` [PATCH v2 3/5] signal: Move sys_errlist " Adhemerval Zanella
2020-05-07 14:37 ` Andreas Schwab
2020-05-08 12:12 ` Adhemerval Zanella
2020-05-07 21:28 ` Joseph Myers
2020-05-08 12:21 ` Adhemerval Zanella
2020-05-12 17:39 ` Carlos O'Donell
2020-05-07 14:23 ` [PATCH v2 4/5] mips: Fix SIGRTMAX definition Adhemerval Zanella
2020-05-12 17:00 ` Maciej W. Rozycki [this message]
2020-05-12 17:18 ` Adhemerval Zanella
2020-05-12 17:41 ` Carlos O'Donell
2020-05-12 17:50 ` Adhemerval Zanella
2020-05-12 17:51 ` Carlos O'Donell
2020-05-07 14:23 ` [PATCH v2 5/5] linux: Fix __NSIG_WORDS and add __NSIG_BYTES Adhemerval Zanella
2020-05-12 17:41 ` Carlos O'Donell
2020-05-07 17:38 ` [PATCH v2 1/5] signal: Add signum-{generic,arch}.h Paul E Murphy
2020-05-07 18:27 ` Adhemerval Zanella
2020-05-12 17:36 ` Carlos O'Donell
2020-05-12 17:38 ` Carlos O'Donell
-- strict thread matches above, loose matches on Subject: below --
2020-04-27 21:48 Adhemerval Zanella
2020-04-27 21:48 ` [PATCH v2 4/5] mips: Fix SIGRTMAX definition Adhemerval Zanella
2020-04-28 7:33 ` Andreas Schwab
2020-04-28 13:42 ` Adhemerval Zanella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.21.2005121729290.677301@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).