From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id AB4941F803 for ; Tue, 8 Jan 2019 00:06:43 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=sq5Hdsve4TufgmLz Hia/zpPkhPoatkb+6svDWIfMLuYYGoUV/nwtb+Bm2AFSIc01kqMhE6iioNAXzPOZ 7k00hRNVGWfr8IVRCW1cavEOHVwOjJ+sqht5c3QWBV/+iskMon/ogNJy1z6zhIpL 97ENwYnOUb7G9YRwak2LerdVRw8= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=VLgWmf0bku2A39h49gprmL fw8SQ=; b=Ure4CTQTs+qePqD+0U0zyF6HUFr8jOUm2QaPPNZ/XhrctVoI6++YAX vpfsjft+c3yGNcXsxOWIIToLdt50kYuIFY3CfT0+DBmKxJn03QmVaKG0sZjcwqBE ETsTyvMxaI9zIOaTwyLg1Feq0/sKPLEyF5eSLld8xW04UPnfZ3sno= Received: (qmail 95181 invoked by alias); 8 Jan 2019 00:06:40 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 95166 invoked by uid 89); 8 Jan 2019 00:06:39 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: zimbra.cs.ucla.edu Subject: Re: [PATCH] Deprecate 32-bit off_t support To: Joseph Myers , Florian Weimer Cc: Szabolcs Nagy , "libc-alpha@sourceware.org" , nd , Siddhesh Poyarekar References: <87sgy8ppeo.fsf@oldenburg2.str.redhat.com> <87muocfhor.fsf@oldenburg2.str.redhat.com> From: Paul Eggert Openpgp: preference=signencrypt Message-ID: Date: Mon, 7 Jan 2019 16:06:35 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 1/7/19 2:17 PM, Joseph Myers wrote: >> What do you propose instead? Mention int64_t and uint64_t only? > Programs and libraries should use types such as off_t, and arrange to be > built with _FILE_OFFSET_BITS=64, which would make them unaffected by a > future change to the default. +1. GNU applications have been doing this for nearly two decades. It's by far the best approach for free software. I suppose I should start adding "#define _TIME_BITS 64" to GNU applications, to future-proof them so that they will take advantage of 64-bit time_t on 32-bit platforms the instant that glibc starts publishing it. Are we definitely going to use this as the feature-test macro, or is it still possible that we'll use something else?