public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zackw@panix.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [COMMITTED PATCH] Make sysdeps/generic/internal-signals.h less stubby.
Date: Wed, 04 Apr 2018 17:49:00 -0000	[thread overview]
Message-ID: <CAKCAbMgeJTZH1PVaRYfy_ah71-KO=BiAHFtaH-p1eYJR=b5rRA@mail.gmail.com> (raw)
In-Reply-To: <8f56a2a9-7c17-857c-0e7b-d003156536c2@linaro.org>

On Wed, Apr 4, 2018 at 1:42 PM, Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
> On 04/04/2018 13:45, Zack Weinberg wrote:
>> Three of the functions defined by internal-signals.h were not actually
>> fulfilling their contracts when the sysdeps/generic version of that
>> file was used.  Also, the Linux version included several more headers
>> than the generic version, which is the root cause of a build failure
>> on Hurd (already addressed in another way, but I think it is proper to
>> make the headers match).
>>
>> In principle, __libc_signal_block_all, __libc_signal_block_app, and
>> __libc_signal_restore_set could be defined in non-system-dependent
>> code, leaving only __is_internal_signal and __clear_internal_signal to
>> be defined by a sysdeps header, but the Linux version of
>> internal-signals.h wants to inline a raw rt_sigprocmask syscall, and I
>> don't feel like messing with that today.
>
> Thanks for catching it.  If I remember correctly, I used an inlined
> rt_sigprocmask for Linux because both sigprocmask and pthread_sigmask
> filter both SIGCANCEL and SIGSETXID. We could use it for
> __libc_signal_block_app, but __libc_signal_block_all and
> __libc_signal_restore_set would require a new symbol.

Yeah, that's what I thought was going on.  I think it's fine the way
it is at least for now.

zw

      reply	other threads:[~2018-04-04 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04 16:45 Zack Weinberg
2018-04-04 17:42 ` Adhemerval Zanella
2018-04-04 17:49   ` Zack Weinberg [this message]

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='CAKCAbMgeJTZH1PVaRYfy_ah71-KO=BiAHFtaH-p1eYJR=b5rRA@mail.gmail.com' \
    --to=zackw@panix.com \
    --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).