From: Lukasz Majewski <lukma@denx.de>
To: Rich Felker <dalias@libc.org>
Cc: libc-alpha@sourceware.org, musl@lists.openwall.com,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [musl] time64 abi choices for glibc and musl
Date: Mon, 12 Aug 2019 23:12:47 +0200 [thread overview]
Message-ID: <20190812231247.4e2587db@jawa> (raw)
In-Reply-To: <20190812175556.GT9017@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 2170 bytes --]
Hi Rich,
> On Sat, Aug 10, 2019 at 01:58:08PM -0400, Rich Felker wrote:
> > Note: this email is to glibc list and particularly seeking feedback
> > from glibc folks, but CC'd to musl list as well.
> >
> > As far as I can tell, most time64 work/discussion on the glibc side
> > so far has been about implementation mechanisms and symbol-binding
> > ABI aspects, and one aspect that doesn't seem to have been
> > addressed is making good choices about the actual types involved.
> > Some of them have been done:
> >
> > struct timespec (endian-matching padding)
> > struct timeval (64-bit suseconds_t)
> > struct itimerspec, itimerval, utimbuf, timeb (obvious definitions)
> >
> > but I haven't seen a clear proposal with rationale for the choices
> > in defining:
> >
> > struct stat
> > struct msqid_ds, semid_ds, shmid_ds (sysvipc)
> > struct rusage
> > struct timex
> > struct utmp[x]
> >
> > [...]
>
> The wiki at https://sourceware.org/glibc/wiki/Y2038ProofnessDesign
> does not seem to cover any of this issue,
> and the two branch links
> that should shed light on the types seem to be down/deleted:
>
> https://sourceware.org/git/?p=glibc.git;a=log;h=refs/heads/aaribaud/y2038-2.26
> https://sourceware.org/git/?p=glibc.git;a=log;h=refs/heads/aaribaud/y2038-2.26-rfc-2
>
> I'm guessing the following is the current one that should be linked
> instead, no?
>
> https://sourceware.org/git/?p=glibc.git;a=log;h=refs/heads/aaribaud/y2038
The most recent development of this code - i.e. 2.29 glibc working with
warrior Yocto/OE can be found here:
https://github.com/lmajewski/y2038_glibc/commits/Y2038-2.29-glibc-warrior-01-08-2019
(At least on 32 bit system BSP build with Yocto/OE with glibc from above
link it is possible to set / read date beyond Y2038. However, there are
still some parts broken - like ping timestamps.)
>
> Rich
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-12 21:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 17:58 Rich Felker
2019-08-10 20:15 ` Paul Eggert
2019-08-11 2:18 ` [musl] " Rich Felker
2019-08-12 0:31 ` Paul Eggert
2019-08-12 1:55 ` Rich Felker
2019-08-12 18:01 ` Rich Felker
2019-08-12 18:20 ` Rich Felker
2019-08-12 16:29 ` Zack Weinberg
2019-08-12 17:11 ` Rich Felker
2019-08-12 17:55 ` [musl] " Rich Felker
2019-08-12 21:12 ` Lukasz Majewski [this message]
2019-08-12 20:13 ` Joseph Myers
2019-08-12 21:54 ` Rich Felker
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=20190812231247.4e2587db@jawa \
--to=lukma@denx.de \
--cc=dalias@libc.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).