From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.cs.ucla.edu (mail.cs.ucla.edu [131.179.128.66]) by sourceware.org (Postfix) with ESMTPS id E19503858D20 for ; Wed, 17 Apr 2024 21:14:40 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E19503858D20 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 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org E19503858D20 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=131.179.128.66 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1713388482; cv=none; b=vHTtX28YHx/+JPBQan5ZMCJDxG3AnmUWs9tecd93LhYEGaCdnMTC4Qkpns9wR1F1wxeNfv3eLZDPrDHzFcXQPGUlvVlUlqyJQUwLdjvd/qOqbE5plwiw1exGjizaAaZkxK+0ci7Ju2KjbDLMMHL7TYIjG43aYPJ9O9VAkZ+JkJI= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1713388482; c=relaxed/simple; bh=AF03RhzzcuM8aodJOn+ry0TaZd9EDhEc+N+/hd0ujMI=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=R/LTXtGA7SyvrtVj1jb5YuwMJcN0rCrD1gcjJKrn7J43i48j1d6zJdxO2Ka+2XnrlnEHtL2mgDttxtxx5e3eWcxUHnqYT/npk0LP2DYm1hbQY4pJYZdWiGpn2pHwg9iwZDyWzGQKBQNbYuawsxzuY5oTMtDWSj70kFUzKieZ/NM= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id 666883C00E410; Wed, 17 Apr 2024 14:14:40 -0700 (PDT) Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10032) with ESMTP id 1a6AnAL2LeiR; Wed, 17 Apr 2024 14:14:40 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id 15E103C011BDB; Wed, 17 Apr 2024 14:14:40 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cs.ucla.edu 15E103C011BDB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.ucla.edu; s=9D0B346E-2AEB-11ED-9476-E14B719DCE6C; t=1713388480; bh=azMm0+NdbLYK31POcIoQMj4Z2PKLSys5ZXUDAKTF800=; h=Message-ID:Date:MIME-Version:To:From; b=EqyAu+6DurJ8ddyG5EGCguLg9qW8iji/X2vTk/UlPCH//hYbCHBWGcSTjwMeTpuRZ ktXPfk5Lxo98Q0/VRzU55KTHBisjV0ty+cJFTPJ2OcZgxwPOk4hQf2rpAu6DLjzkSR 4DiXvnWcX1ATIxjd5f2nqwk7fQpSeT2/oiNXtzq3weuZOiX2na2JfK2gKncvApdsw1 ke1x9gUo9PonuLsobw1OUu/PDl36B0ZuIsgqRmTvSYUSbiCRdd0aCPTBcz7zaKkwea SqHjwNj12xPXeJMQqCpWHxPwzZf8y71a0r4x7N7mcl8Qbg5L8WFz8Gb2PhTSBeN/vX Hhwf6ke3K45VA== X-Virus-Scanned: amavis at mail.cs.ucla.edu Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id y4I2tbdv9bfO; Wed, 17 Apr 2024 14:14:40 -0700 (PDT) Received: from [131.179.64.200] (Penguin.CS.UCLA.EDU [131.179.64.200]) by mail.cs.ucla.edu (Postfix) with ESMTPSA id EDA2E3C011BDA; Wed, 17 Apr 2024 14:14:39 -0700 (PDT) Message-ID: Date: Wed, 17 Apr 2024 14:14:39 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v3 2/3] login: structs utmp, utmpx, lastlog _TIME_BITS independence (bug 30701) To: Florian Weimer Cc: libc-alpha@sourceware.org References: <1600e516-8a88-4ddb-af2f-3e29fd605592@cs.ucla.edu> <87h6g3nfe0.fsf@oldenburg.str.redhat.com> Content-Language: en-US From: Paul Eggert Organization: UCLA Computer Science Department In-Reply-To: <87h6g3nfe0.fsf@oldenburg.str.redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,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 4/15/24 02:28, Florian Weimer wrote: > I can implement it that way, but I'm not sure if it's > worth the complexity. This would only benefit obsolescent applications > that are recompiled. You're right, it would benefit only those old applications, and only when they are built in an obsolescent way (i.e., with 32-bit time_t). If it's greater complexity to support obsolescent builds I suppose you're right, and let's not bother. The old applications I help maintain are all using _TIME_BITS=64 on these platforms, so they won't be built in an obsolescent way and won't care about this.