From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79228 invoked by alias); 21 Jun 2016 22:58:55 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 79212 invoked by uid 89); 21 Jun 2016 22:58:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.3 required=5.0 tests=BAYES_40,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=cordialement, fourth, Albert, H*r:470 X-HELO: smtp2-g21.free.fr Date: Tue, 21 Jun 2016 22:58:00 -0000 From: Albert ARIBAUD To: GNU C Library Subject: Fourth draft of the Y2038 design document Message-ID: <20160622005838.60a95c44.albert.aribaud@3adev.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SW-Source: 2016-06/txt/msg00824.txt.bz2 Hi all, I have produced a fourth draft of what will eventually become the Y2038 design document: https://sourceware.org/glibc/wiki/Y2038ProofnessDesign?rev=83 Relative to the previous draft: * the scope clarifies that *only* Y2038 is considered, and no other doomsday such as Y2106 or Y9999; * all types directly or indirectly derived from time_t are now listed; * all APIs using these types are now listed; * all functions which use time_t internally are now listed; * also listed are types and APIs related to time but which are Y2038-safe (even though they might be unsafe for some other doomsday, e.g. struct rpc_timeval being Y2106-unsafe). As always, comments welcome. Cordialement, Albert ARIBAUD 3ADEV