This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC2 RESEND PATCH] [AARCH64] ILP32: support stat syscall family
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Yury Norov <ynorov at caviumnetworks dot com>
- Cc: <libc-alpha at sourceware dot org>, <arnd at arndb dot de>, <catalin dot marinas at arm dot com>, <davem at davemloft dot net>, <szabolcs dot nagy at arm dot com>, <maxim dot kuvyrkov at linaro dot org>, <pinskia at gmail dot com>, <bamvor dot zhangjian at huawei dot com>, <schwab at suse dot de>, <fweimer at redhat dot com>, <Prasun dot Kapoor at cavium dot com>, <adhemerval dot zanella at linaro dot org>
- Date: Mon, 1 Aug 2016 16:47:14 +0000
- Subject: Re: [RFC2 RESEND PATCH] [AARCH64] ILP32: support stat syscall family
- Authentication-results: sourceware.org; auth=none
- References: <1467816908-15290-1-git-send-email-ynorov@caviumnetworks.com> <alpine.DEB.2.20.1607201556470.12251@digraph.polyomino.org.uk> <20160801155356.GA20010@yury-N73SV> <alpine.DEB.2.20.1608011556040.27018@digraph.polyomino.org.uk> <20160801163701.GB20010@yury-N73SV>
On Mon, 1 Aug 2016, Yury Norov wrote:
> 32-bit ports should have 64-bit time types and structures to be ready
> to Y2038, and for now we have no such structures.
If you are interested in Y2038 support, you need to engage in the threads
discussing successive revisions of
<https://sourceware.org/glibc/wiki/Y2038ProofnessDesign>. I imagine that
Albert ARIBAUD will be working on patches once the design is established.
> OK, I'll prepare the patch w/o unions. Anyway, I think we'd have
> 64-bit timespec for 32-bit ports. Are you OK if I will introduce
> struct timespec64 in separated installed header, and use it under
> SUPPORT_64_BIT_TIME_TYPES option?
SUPPORT_64_BIT_TIME_TYPES is in the user namespace; it has no business in
installed headers. The proposed design does not involve any APIs for
explicit 64-bit time use (APIs like lseek64 with off64_t in the
large-files case), only use of _TIME_BITS=64 to redirect existing APIs to
new ABIs (those ABIs being in the implementation namespace, of course, and
new ABIs only being present in those cases where the default interface
uses 32-bit time_t). Thus there should be no such type as struct
timespec64 in installed headers, only different definitions of struct
timespec depending on _TIME_BITS.
--
Joseph S. Myers
joseph@codesourcery.com