public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: Missing time64 prototypes for !__REDIRECT compilers
Date: Mon, 5 Jul 2021 09:06:30 -0300	[thread overview]
Message-ID: <db8aef62-b67b-e080-ec4f-204c86f242dd@linaro.org> (raw)
In-Reply-To: <87h7h9ozvs.fsf@oldenburg.str.redhat.com>



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.

  reply	other threads:[~2021-07-05 12:06 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 [this message]
2021-07-05 12:15   ` Florian Weimer
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=db8aef62-b67b-e080-ec4f-204c86f242dd@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --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).