From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D9E63A2C for ; Thu, 2 Mar 2023 10:38:36 +0000 (UTC) Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id 5BB791FE66; Thu, 2 Mar 2023 10:38:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1677753509; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PZhzmq+pjukRJRw/80THNn2ZCA/R0VoFaRfJO2UvDH4=; b=Qw1axKy09nPb7J4lfeF1qOrjE1PzKLCYyd28PW3UnsAG2PqBKxukxZuDtNq4r3+tDLAKLk 0DYSyHjoD1X0PESGYN7I5ETMKcYuumcH7Xp9/NKrWpVg4LVWbAAOWfvTZ2268nzySz7w4h ZD60tIp6/cMMuYjiLgB8wQFca2dcNy0= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1677753509; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PZhzmq+pjukRJRw/80THNn2ZCA/R0VoFaRfJO2UvDH4=; b=wP2Sxz3L4rzGbz3Sdhc66FXyinRzz0v4naN4keghu271gIIBTD+2vGF5aEALPXekKVvsOD qXs6b6kyvGY+KdBw== Received: from hawking.suse.de (unknown [10.168.4.11]) by relay2.suse.de (Postfix) with ESMTP id 39C002C142; Thu, 2 Mar 2023 10:38:27 +0000 (UTC) Received: by hawking.suse.de (Postfix, from userid 17005) id C4F1B442EE6; Thu, 2 Mar 2023 11:38:27 +0100 (CET) From: Andreas Schwab To: Paul Eggert Cc: Daniel P. =?utf-8?Q?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 , Arsen =?utf-8?Q?Arsenovi=C4=87?= , rjones@redhat.com Subject: Re: On time64 and Large File Support References: <20230301223859.chl5o3bedqckf3tx@redhat.com> <086d6fcd-3738-cc7f-db72-6a8d19d33e30@gmail.com> <7253e4c5-0f36-e725-f180-624f8887bf08@cs.ucla.edu> X-Yow: CALIFORNIA is where people from IOWA or NEW YORK go to subscribe to CABLE TELEVISION!! Date: Thu, 02 Mar 2023 11:38:27 +0100 In-Reply-To: <7253e4c5-0f36-e725-f180-624f8887bf08@cs.ucla.edu> (Paul Eggert's message of "Thu, 2 Mar 2023 02:28:28 -0800") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) Precedence: bulk X-Mailing-List: c-std-porting@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit On Mär 02 2023, Paul Eggert wrote: > Fifteen years from now we'll be saying the same thing about > _TIME_BITS. There will be some pain in the meantime, just as there was > with the _FILE_OFFSET_BITS transition, something I lived through and was > not too happy about either. There is a huge difference between them: time_t has a flag day, off_t doesn't. You can still run with 32-bit off_t today and have everything working. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."