From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 83145 invoked by alias); 28 Jan 2016 21:13:13 -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 83128 invoked by uid 89); 28 Jan 2016 21:13:12 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=rolls, 2038 X-HELO: zimbra.cs.ucla.edu Subject: Re: Second draft of the Y2038 design document To: Albert ARIBAUD , GNU C Library References: <20160128204114.6c7dbbf7.albert.aribaud@3adev.fr> From: Paul Eggert Message-ID: <56AA8465.5040803@cs.ucla.edu> Date: Thu, 28 Jan 2016 21:13:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <20160128204114.6c7dbbf7.albert.aribaud@3adev.fr> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2016-01/txt/msg00837.txt.bz2 Some typos: "1901-12-13 19:55:13 UTC" should be "1901-12-13 20:45:52 UTC". "sentive" should be "sensitive". "20338" should be "2038". "Thins" should be "This". I don't see why functions like 'time' and 'gettimeofday' should be allowed to misbehave on 64-bit hosts after 2038. They should just work. Glibc should not worry about 64-bit kernels without 64-bit time support. Any such kernels should just get fixed before 2038 rolls around. Why are struct rusage, getrusage, etc. Y2038-sensitive? They hold intervals, not absolute times.