From: Andreas Schwab <schwab@suse.de>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org, Kabe <skabe@vega.pgw.jp>
Subject: Re: [PATCH v3] Linux: Add ppoll fortify symbol for 64 bit time_t (BZ# 29746)
Date: Tue, 08 Nov 2022 14:28:16 +0100 [thread overview]
Message-ID: <mvm8rkld18v.fsf@suse.de> (raw)
In-Reply-To: <20221108131525.1070162-1-adhemerval.zanella@linaro.org> (Adhemerval Zanella's message of "Tue, 8 Nov 2022 10:15:25 -0300")
On Nov 08 2022, Adhemerval Zanella wrote:
> diff --git a/include/sys/poll.h b/include/sys/poll.h
> index f904e21f89..af032048e4 100644
> --- a/include/sys/poll.h
> +++ b/include/sys/poll.h
> @@ -2,16 +2,22 @@
> # include <io/sys/poll.h>
>
> #ifndef _ISOMAC
> +#include <include/struct___timespec64.h>
> +
> extern int __poll (struct pollfd *__fds, unsigned long int __nfds,
> int __timeout);
> libc_hidden_proto (__poll)
> +
> libc_hidden_proto (ppoll)
>
> # if __TIMESIZE == 64
> -# define __ppoll64 __ppoll
> +# define ppoll64 ppoll
> +# define __ppoll64 ppoll
> +# define __ppoll64_chk __ppoll_chk
> # else
> # include <time.h>
> # include <signal.h>
> +# define ppoll64 __ppoll64
Why do you need that indirection through the ppoll64 macro?
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2022-11-08 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 13:15 Adhemerval Zanella
2022-11-08 13:28 ` Andreas Schwab [this message]
2022-11-08 13:58 ` Adhemerval Zanella Netto
2022-11-08 14:03 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2022-11-07 18:36 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=mvm8rkld18v.fsf@suse.de \
--to=schwab@suse.de \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=skabe@vega.pgw.jp \
/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).