From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from zimbra.cs.ucla.edu (zimbra.cs.ucla.edu [131.179.128.68]) by sourceware.org (Postfix) with ESMTPS id 2DE8D3858D33 for ; Fri, 3 Mar 2023 05:46:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2DE8D3858D33 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=cs.ucla.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=cs.ucla.edu Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id E9302160084; Thu, 2 Mar 2023 21:46:43 -0800 (PST) Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id G3TCX-qVKiOs; Thu, 2 Mar 2023 21:46:43 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 210C716008B; Thu, 2 Mar 2023 21:46:43 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.9.2 zimbra.cs.ucla.edu 210C716008B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.ucla.edu; s=78364E5A-2AF3-11ED-87FA-8298ECA2D365; t=1677822403; bh=1Fe99jVddk1M/0LJ4S217WEjw1el0jFY9apPw770Q8E=; h=Message-ID:Date:MIME-Version:Subject:To:From:Content-Type: Content-Transfer-Encoding; b=rGBXBsLN8aUot4Y2/EnX0SutDxaPeqjQa6QdWIVmOJjHOpKrCo1VHjentj8wUMO6n 8MVVHSNUjBH4gnyd4bkS79cE73Ar4rRbVC3sf3eDiUkRPoBNgrkcyD9jZ5Lc9VGhtt BX9CVOhRiYTVMEtZ+lz/YJyLm562spruIxvSlC0g= X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id kcMmLA2bMsjc; Thu, 2 Mar 2023 21:46:43 -0800 (PST) Received: from [131.179.64.200] (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 8F3EC160084; Thu, 2 Mar 2023 21:46:42 -0800 (PST) Message-ID: Date: Thu, 2 Mar 2023 21:46:42 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: On time64 and Large File Support Content-Language: en-US To: Andreas Schwab Cc: =?UTF-8?Q?Daniel_P=2e_Berrang=c3=a9?= , Demi Marie Obenour , Eric Blake , Sam James , Carlos O'Donell via Libc-alpha , autoconf@gnu.org, c-std-porting@lists.linux.dev, Zack Weinberg , David Seifert , Gentoo Toolchain , =?UTF-8?Q?Arsen_Arsenovi=c4=87?= , rjones@redhat.com References: <20230301223859.chl5o3bedqckf3tx@redhat.com> <086d6fcd-3738-cc7f-db72-6a8d19d33e30@gmail.com> <7253e4c5-0f36-e725-f180-624f8887bf08@cs.ucla.edu> From: Paul Eggert Organization: UCLA Computer Science Department In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,JMQ_SPF_NEUTRAL,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 3/2/23 02:38, Andreas Schwab wrote: > There is a huge difference between them: time_t has a flag day, off_t > doesn't. Absolutely right. Another thing that's different is that when off_t grew in the 1990s, people said they needed a wider off_t RIGHT NOW, because programs wouldn't work on large inputs otherwise. The pressure to build with _FILE_OFFSET_BITS=64 was large enough that a working consensus was reached pretty quickly to build that way. In contrast, people don't urgently need a wider time_t until 2038. So the "let's be organized about this and do things systematically" sentiment wins, and because other things take priority time_t conversion never gets done. (Or possibly the "either the platform or I will be dead by 2038 so let's do nothing" sentiment wins, which is another seemingly-good reason to do nothing....)