From: Andreas Schwab <schwab@linux-m68k.org>
To: "Alejandro Colomar (man-pages) via Libc-alpha"
<libc-alpha@sourceware.org>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
Florian Weimer <fweimer@redhat.com>,
"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: pthread_cleanup_push_defer_np.3: missing functions in glibc
Date: Mon, 08 Mar 2021 12:05:20 +0100 [thread overview]
Message-ID: <87lfax52j3.fsf@igel.home> (raw)
In-Reply-To: <1ee301e5-d3a4-2e0e-3473-6b0eea304266@gmail.com> (Alejandro Colomar via Libc-alpha's message of "Mon, 8 Mar 2021 11:35:35 +0100")
On Mär 08 2021, Alejandro Colomar (man-pages) via Libc-alpha wrote:
> While adding 'restrict' to the prototypes, I found that the functions
> defined in this page don't exist on glibc (or I couldn't find them).
sysdeps/nptl/pthread.h:# define pthread_cleanup_push_defer_np(routine, arg) \
sysdeps/nptl/pthread.h:# define pthread_cleanup_pop_restore_np(execute) \
sysdeps/nptl/pthread.h:# define pthread_cleanup_push_defer_np(routine, arg) \
sysdeps/nptl/pthread.h:# define pthread_cleanup_pop_restore_np(execute) \
sysdeps/nptl/pthread.h:# define pthread_cleanup_push_defer_np(routine, arg) \
sysdeps/nptl/pthread.h:# define pthread_cleanup_pop_restore_np(execute) \
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-03-08 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 10:35 pthread_cleanup_push_defer_np.3: missing functions in glibc Alejandro Colomar (man-pages)
2021-03-08 10:39 ` Florian Weimer
2021-03-08 10:54 ` Alejandro Colomar (man-pages)
2021-03-08 11:27 ` Florian Weimer
2021-03-08 11:05 ` Andreas Schwab [this message]
2021-03-08 13:12 ` Alejandro Colomar (man-pages)
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=87lfax52j3.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=alx.manpages@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.