From: Arnd Bergmann <arnd@arndb.de>
To: Alistair Francis <alistair23@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Alistair Francis <alistair.francis@wdc.com>,
Lukasz Majewski <lukma@denx.de>
Subject: Re: 32-bit time_t inside itimerval
Date: Mon, 30 Dec 2019 23:11:32 +0100 [thread overview]
Message-ID: <CAK8P3a0zbcTMr0fQB35E9Y9r0DUS9-W4h9z1zOv+coKiH56HZg@mail.gmail.com> (raw)
In-Reply-To: <CAKmqyKMtZTaQVP-x0fLr3Uo_u5p0dbPo8fR4-b9Yey4hSRSudg@mail.gmail.com>
On Mon, Dec 30, 2019 at 10:22 PM Alistair Francis <alistair23@gmail.com> wrote:
> On Mon, Dec 30, 2019 at 12:11 PM Arnd Bergmann <arnd@arndb.de> wrote:
> > On Mon, Dec 30, 2019 at 8:57 PM Alistair Francis <alistair23@gmail.com> wrote:
> > >
> > > Yeah, agreed. I have updated the RV32 port to internally convert
> > > between 32/64-bit.
> >
> > Any chance of making this the default implementation for 32-bit
> > rather than RV32 specific? The code should be the same for any
> > time64 user space regardless of the architecture.
>
> I was thinking about this.
>
> I don't know of a good way to make it apply only to 32-bit archs with
> a 64-bit time_t.This could actually just apply to all 32-bit archs.
> That way ones that are 64-bit time_t are covered and ones that aren't
> will just do an extra conversion with no effect.
>
> Making it 32-bit in general seems reasonable to me, I just have to
> figure out a way to test it though.
Maybe Lukasz already has a plan for this, I don't think it's
fundamentally different from the other system calls that he has
converted already to work with time64 callers.
Arnd
next prev parent reply other threads:[~2019-12-30 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 22:28 32-bit time_t inside itimerval Alistair Francis
2019-12-21 13:31 ` Arnd Bergmann
2019-12-21 17:18 ` Alistair Francis
2019-12-30 10:02 ` Arnd Bergmann
2019-12-30 19:51 ` Alistair Francis
2019-12-30 20:11 ` Arnd Bergmann
2019-12-30 21:16 ` Alistair Francis
2019-12-30 22:11 ` Arnd Bergmann [this message]
2020-01-02 12:08 ` Lukasz Majewski
2020-01-02 12:28 ` Arnd Bergmann
2020-01-04 18:03 ` Alistair Francis
2020-01-05 16:07 ` Lukasz Majewski
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=CAK8P3a0zbcTMr0fQB35E9Y9r0DUS9-W4h9z1zOv+coKiH56HZg@mail.gmail.com \
--to=arnd@arndb.de \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--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).