From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org, Lukasz Majewski <lukma@denx.de>
Subject: Re: Missing time64 prototypes for !__REDIRECT compilers
Date: Mon, 05 Jul 2021 14:15:36 +0200 [thread overview]
Message-ID: <878s2lot1z.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <db8aef62-b67b-e080-ec4f-204c86f242dd@linaro.org> (Adhemerval Zanella's message of "Mon, 5 Jul 2021 09:06:30 -0300")
* Adhemerval Zanella:
> On 05/07/2021 06:48, Florian Weimer wrote:
>> This pattern looks incorrect to me:
>>
>> #ifdef __USE_GNU
>> /* Receive up to VLEN messages as described by VMESSAGES from socket FD.
>> Returns the number of messages received or -1 for errors.
>>
>> This function is a cancellation point and therefore not marked with
>> __THROW. */
>> # ifndef __USE_TIME_BITS64
>> extern int recvmmsg (int __fd, struct mmsghdr *__vmessages,
>> unsigned int __vlen, int __flags,
>> struct timespec *__tmo);
>> # else
>> # ifdef __REDIRECT
>> extern int __REDIRECT (recvmmsg, (int __fd, struct mmsghdr *__vmessages,
>> unsigned int __vlen, int __flags,
>> struct timespec *__tmo),
>> __recvmmsg64);
>> # else
>> # define recvmmsg __recvmmsg64
>> # endif
>> # endif
>> #endif
>>
>> For the !__REDIRECT case, a prototype for __recvmmsg64 is still needed.
>
> There is some fixes for recvmsg and recvmmsg that I am working on,
> I will add this as well.
I'm working on adding some missing time64 aliases. I've got a
SCM_RIGHTS smoke test.
Thanks,
Florian
next prev parent reply other threads:[~2021-07-05 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 9:48 Florian Weimer
2021-07-05 12:06 ` Adhemerval Zanella
2021-07-05 12:15 ` Florian Weimer [this message]
2021-07-05 12:26 ` Adhemerval Zanella
2021-07-05 12:42 ` Florian Weimer
2021-07-05 12:44 ` Adhemerval Zanella
2021-07-05 12:50 ` Florian Weimer
2021-07-05 12:55 ` 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=878s2lot1z.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=lukma@denx.de \
/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).