This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC PATCH] AARCH64/ILP32: introduce kernel time types


On Tue, 28 Jun 2016, Szabolcs Nagy wrote:

> i agree with andreas.
> 
> i don't think kernel names should be involved here.

I also agree.  The types in utmp have *nothing* to do with the kernel.  
Kernel time types should not appear in any public glibc interfaces at all, 
only in code translating between kernel and glibc interfaces.

> (ideally the on-disk format would be the same on all
> abis not just on the ilp32 and lp64 abi of the same arch,
> since the same rootfs may be mounted on different hosts
> with a proper multiarch setup..  and ideally the public
> struct types would not need any changes to make this work,
> they could be serialized into a portable format.)

Yes (subject to a question of whether we actually care about 
endianness-independence of the on-disk format, or only about such cases as 
AArch32 / AArch64 ILP32 / AArch64 LP64 all of same endianness).  I think 
the goal should be that the struct types in the headers are 
POSIX-conforming on all architectures, with translation for file input / 
output as needed so that applications with 32-bit and 64-bit time_t, and 
applications for different ABI variants, can access the same files, those 
files always storing 64-bit time values.  So if any changes to utmp 
structures are being made, let's make them in that direction.

-- 
Joseph S. Myers
joseph@codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]