[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e87dc192-4799-df0b-8a9f-524f10fbd267@cs.ucla.edu>
Date: Sat, 10 Aug 2019 13:15:34 -0700
From: Paul Eggert <eggert@...ucla.edu>
To: Rich Felker <dalias@...c.org>, libc-alpha@...rceware.org
Cc: musl@...ts.openwall.com
Subject: Re: time64 abi choices for glibc and musl
Rich Felker wrote:
> For struct stat, I think it's almost necessary to preserve the
> existing layout and add new time64 members on the end, and to continue
> filling in the time32 members.
This won't be reliable for applications that call 'stat', fiddle with the
timestamps in the resulting 'struct stat', and then pass the fiddled-with struct
to some other function. If they fiddle with the 64-bit timestamp the 32-bit copy
will become wrong, and vice versa.
There are similar issues for applications that create struct stat values by
hand, without calling a 'stat'-like function.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
