From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fw@deneb.enyo.de>,
Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/4] ia64: Remove sigprocmask/sigblock objects from libpthread
Date: Tue, 21 Apr 2020 09:06:52 -0300 [thread overview]
Message-ID: <3351fe25-042a-1826-1f4e-ce431c387701@linaro.org> (raw)
In-Reply-To: <87o8rlrr0v.fsf@mid.deneb.enyo.de>
On 21/04/2020 08:56, Florian Weimer wrote:
> * Adhemerval Zanella via Libc-alpha:
>
>> It is required because __libc_unwind_longjmp (used on thread
>> cancellation) calls __sigprocmask. Replace with a direct call.
>>
>> The sigblock was never exported and thus unused.
>
> Perhaps:
>
> They are required because __libc_unwind_longjmp (used for thread
> cancellation) calls __sigprocmask. Replace this with a direct call.
>
> The sigblock function is not exported and is not used internally, so
> it can be removed.
Ack, I have changed the commit message.
>
>
>> Checked on cross build for ia64-linux-gnu.
>
> I can put this through a build-many-glibcs.py run just to be sure
> (once the first patch is ready as well), but change itself looks good
> to me.
>
I will double check with a full build-many-glibcs.py as well.
next prev parent reply other threads:[~2020-04-21 12:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 19:48 [PATCH v2 1/4] nptl: Move pthread_sigmask implementation to libc Adhemerval Zanella
2020-03-13 19:48 ` [PATCH 2/4] ia64: Remove sigprocmask/sigblock objects from libpthread Adhemerval Zanella
2020-04-17 13:25 ` Adhemerval Zanella
2020-04-21 11:56 ` Florian Weimer
2020-04-21 12:06 ` Adhemerval Zanella [this message]
2020-03-13 19:48 ` [PATCH v2 3/4] linux: Use pthread_sigmask on sigprocmask Adhemerval Zanella
2020-04-17 13:25 ` Adhemerval Zanella
2020-04-21 12:01 ` Florian Weimer
2020-04-21 12:30 ` Adhemerval Zanella
2020-04-21 12:35 ` Florian Weimer
2020-04-21 13:01 ` Adhemerval Zanella
2020-03-13 19:48 ` [PATCH 4/4] signal: Only handle on NSIG signals on signal functions (BZ #25657) Adhemerval Zanella
2020-04-17 13:25 ` Adhemerval Zanella
2020-04-21 12:53 ` Florian Weimer
2020-04-21 13:11 ` Adhemerval Zanella
2020-04-21 13:14 ` Florian Weimer
2020-04-21 13:29 ` Adhemerval Zanella
2020-04-21 13:47 ` Florian Weimer
2020-04-21 14:02 ` Adhemerval Zanella
2020-04-21 14:07 ` Florian Weimer
2020-04-21 14:10 ` Adhemerval Zanella
2020-04-21 14:35 ` Florian Weimer
2020-04-21 14:36 ` Adhemerval Zanella
2020-04-21 15:05 ` Andreas Schwab
2020-04-21 17:28 ` Florian Weimer
2020-04-21 17:49 ` Adhemerval Zanella
2020-04-21 18:40 ` Andreas Schwab
2020-04-21 19:00 ` Adhemerval Zanella
2020-04-21 21:14 ` Andreas Schwab
2020-04-22 8:32 ` Florian Weimer
2020-04-22 11:34 ` Adhemerval Zanella
2020-04-17 13:25 ` [PATCH v2 1/4] nptl: Move pthread_sigmask implementation to libc Adhemerval Zanella
2020-04-21 11:50 ` Florian Weimer
2020-04-21 14:06 ` 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=3351fe25-042a-1826-1f4e-ce431c387701@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fw@deneb.enyo.de \
--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).