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 683C53858C36 for ; Fri, 27 Jan 2023 23:51:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 683C53858C36 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 8D011160044; Fri, 27 Jan 2023 15:51:03 -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 aTT5oDFd1Tcc; Fri, 27 Jan 2023 15:51:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id BE6FB160082; Fri, 27 Jan 2023 15:51:02 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.9.2 zimbra.cs.ucla.edu BE6FB160082 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.ucla.edu; s=78364E5A-2AF3-11ED-87FA-8298ECA2D365; t=1674863462; bh=nw1kHLK1VRKv7Sdib+5Wma9BYrnw74+ecQM531s80hk=; h=Message-ID:Date:MIME-Version:To:From:Subject:Content-Type: Content-Transfer-Encoding; b=Rrt1rvcvBqO9Cj1SQfSiJQGP0KOp2gg8/ydL0eFfbI34TgOUxhgG09ocGIcfuxYEf Ap/jOIQKaTBK4USn0g2wRRAOQTHUkqAX+nAnrUeoKWf744C+pGAkFg0ulkPGaSQkFN 7KdSy2upq6fQJTk0qQazQjO30p8mZ2yOKRgGHftg= 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 kW25Cun2zF1N; Fri, 27 Jan 2023 15:51:02 -0800 (PST) Received: from [192.168.1.9] (cpe-172-91-119-151.socal.res.rr.com [172.91.119.151]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 91D47160044; Fri, 27 Jan 2023 15:51:02 -0800 (PST) Message-ID: Date: Fri, 27 Jan 2023 15:51:02 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Content-Language: en-US To: Adhemerval Zanella Netto Cc: libc-alpha@sourceware.org References: <10857996.18pcnM708K@pinacolada> <7196595.N7aMVyhfb1@pinacolada> <7271eb94-b5d7-69d6-9be0-ca1afda29a50@cs.ucla.edu> <2342ab66-6ac6-17d8-3693-8e2fd93fc8a1@linaro.org> From: Paul Eggert Organization: UCLA Computer Science Department Subject: Re: time64 / Large File Support: 2) default time64 breaks legacy 32bit binaries In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.7 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=ham 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 2023-01-27 09:40, Adhemerval Zanella Netto wrote: >> Another possibility is to adopt the milder approach for glibc version N, and switch to the more drastic approach in glibc version N+1.This would give distros time to test this new configure-time option before it's the default. > Do you mean add the --enable-hard-sys-types64 on glibc N, and then remove it on > N+1 and make the 64-bit the default? Sure, that would work. If that's too fast we could do something more gradual, like this: 1. glibc version N supports --enable-hard-sys-types64 and --disable-hard-sys-types64 and the default is disabled. 2. glibc version N+1 is the same, but the default is enabled. 3. glibc version N+2 removes support for --disable-hard-sys-types64; --enable-hard-sys-type64 remains as a no-op. However, your thought of skipping step (2) would be simpler.