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: glibc 2.29: Reminder, only ~3 weeks to freeze!


Hi Joseph,

On Tue, 18 Dec 2018 17:33:55 +0000, Joseph Myers
<joseph@codesourcery.com> wrote :

> On Tue, 18 Dec 2018, Albert ARIBAUD wrote:
> 
> > Would such internal changes be OK for 2.29?  
> 
> If reviewed before 1 January, but you shouldn't really expect much patch 
> review to take place in the last couple of weeks in December.
> 
> > defining a 64-bit struct timespec and struct timeval (their kernel
> > Y2038 versions are pretty much agreed upon) and switching to using them  
> 
> Is there going to be a new kernel version of struct timeval at all (as 
> opposed to the new versions of timeval-using kernel/userspace interfaces 
> using the 64-bit version of struct timespec)?

Not sure about the kernel indeed.

But what about existing user code which calls public glibc interfaces
which deal with struct timeval? So far there is the assumption that
time-related user source code which compiles with 32-bit time should
compile with 64-bit time without modification. Would we break this and
not "port" existing struct timeval based public interfaces from 32- to
64-bit time?

Cordialement,
Albert ARIBAUD
3ADEV


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