From: Alistair Francis <alistair23@gmail.com>
To: Alistair Francis <alistair.francis@wdc.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] tst-clone3: Use __NR_futex_time64 if we don't have __NR_futex
Date: Thu, 19 Dec 2019 20:02:03 -0800 [thread overview]
Message-ID: <CAKmqyKPpkqejMX1yq+jjT8YJsf6t-v-ea=SyyPrSJyQeE7uJ5A@mail.gmail.com> (raw)
In-Reply-To: <CAKmqyKOkkd1eJ6ndeUibW9u=ngWodhTyXaMYYR1B2T3ZDUiMQQ@mail.gmail.com>
On Mon, Dec 9, 2019 at 10:54 AM Alistair Francis <alistair23@gmail.com> wrote:
>
> On Tue, Dec 3, 2019 at 10:56 AM Alistair Francis <alistair23@gmail.com> wrote:
> >
> > On Tue, Nov 12, 2019 at 9:42 AM Alistair Francis
> > <alistair.francis@wdc.com> wrote:
> > >
> > > We can't include sysdep.h in the test case (it introduces lots of
> > > strange failures) so __NR_futex isn't redifined to __NR_futex_time64 by
> > > 64-bit time_t 32-bit archs (y2038 safe).
> > >
> > > To allow the test to pass let's just do the __NR_futex_time64 syscall if
> > > we don't have __NR_futex defined.
> >
> > Ping!
>
> Ping^2
Ping^3
>
> >
> > Alistair
> >
> > >
> > > Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
> > > ---
> > > sysdeps/unix/sysv/linux/tst-clone3.c | 4 ++++
> > > 1 file changed, 4 insertions(+)
> > >
> > > diff --git a/sysdeps/unix/sysv/linux/tst-clone3.c b/sysdeps/unix/sysv/linux/tst-clone3.c
> > > index 76f8b08a692..c211445e77f 100644
> > > --- a/sysdeps/unix/sysv/linux/tst-clone3.c
> > > +++ b/sysdeps/unix/sysv/linux/tst-clone3.c
> > > @@ -56,7 +56,11 @@ f (void *a)
> > > static inline int
> > > futex_wait (int *futexp, int val)
> > > {
> > > +#ifdef __NR_futex
> > > return syscall (__NR_futex, futexp, FUTEX_WAIT, val);
> > > +#else
> > > + return syscall (__NR_futex_time64, futexp, FUTEX_WAIT, val);
> > > +#endif
> > > }
> > >
> > > static int
> > > --
> > > 2.23.0
> > >
next prev parent reply other threads:[~2019-12-20 4:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 17:36 [PATCH] tst-clone3: Use __NR_futex_time64 if we don't have __NR_futex Alistair Francis
2019-12-03 18:56 ` Alistair Francis
2019-12-09 18:54 ` Alistair Francis
2019-12-20 4:02 ` Alistair Francis [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-31 17:03 Alistair Francis
2020-01-31 21:47 ` Arnd Bergmann
2020-01-31 23:46 ` Alistair Francis
2020-02-14 16:40 ` Alistair Francis
2020-02-14 17: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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKmqyKPpkqejMX1yq+jjT8YJsf6t-v-ea=SyyPrSJyQeE7uJ5A@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.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).