From: Andreas Schwab <schwab@linux-m68k.org>
To: Rich Felker <dalias@aerifal.cx>
Cc: Yousong Zhou <yszhou4tech@gmail.com>,
Pedro Alves <palves@redhat.com>,
gdb-patches@sourceware.org, musl@lists.openwall.com
Subject: Re: [musl] Re: [PATCH] Fix invalid sigprocmask call
Date: Fri, 24 Mar 2017 18:33:55 +0100 [thread overview]
Message-ID: <8737e24m0s.fsf@linux-m68k.org> (raw)
In-Reply-To: <20170324153530.GF17319@brightrain.aerifal.cx> (Rich Felker's message of "Fri, 24 Mar 2017 11:35:30 -0400")
On Mär 24 2017, Rich Felker <dalias@aerifal.cx> wrote:
> If you file a report and it's deemed a bug in the standard and
> changed, I'm happy to change this on the musl side. Just keep me
> posted on what happens. I don't have any preference on what the
> behavior "should" be here (IMO imposing a behavior when the caller has
> violated constraints like passed a wrong value for how is pointless
> anyway) but I do want to conform to the standard.
The standard says that how must be ignored if set is NULL.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-03-24 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1490324519-11228-1-git-send-email-yszhou4tech@gmail.com>
[not found] ` <2b0bab84-e36e-e109-5444-dc84369dddce@redhat.com>
[not found] ` <CAECwjAgARveAhY=8e8J6Bcv+5=W=YnGcLY9G9Dv1sEnkNePVZA@mail.gmail.com>
[not found] ` <39f28782-65e8-0f52-3c8f-134a6f05788b@redhat.com>
2017-03-24 13:05 ` Yousong Zhou
2017-03-24 13:37 ` Pedro Alves
2017-03-25 0:35 ` Yousong Zhou
2017-03-24 15:35 ` [musl] " Rich Felker
2017-03-24 15:52 ` Pedro Alves
2017-03-24 16:41 ` Rich Felker
2017-03-24 17:33 ` Andreas Schwab [this message]
2017-03-24 18:14 ` Rich Felker
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=8737e24m0s.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=dalias@aerifal.cx \
--cc=gdb-patches@sourceware.org \
--cc=musl@lists.openwall.com \
--cc=palves@redhat.com \
--cc=yszhou4tech@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).