From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: What were the Emacs versions with dates limited to 1970 .. 2037 year range? Date: Sun, 12 Jun 2022 10:21:39 -0400 Message-ID: References: <8735gaqm6i.fsf@localhost> <83wndmutg7.fsf@gnu.org> <87tu8qp5um.fsf@localhost> <83r13uurom.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37867"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Ihor Radchenko , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 12 16:22:39 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o0OUA-0009em-I7 for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 16:22:38 +0200 Original-Received: from localhost ([::1]:57916 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o0OU9-00030d-09 for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 10:22:37 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49652) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0OTN-0002KX-CA for emacs-devel@gnu.org; Sun, 12 Jun 2022 10:21:49 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:59801) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0OTJ-0001ZF-Ja; Sun, 12 Jun 2022 10:21:47 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 1195680783; Sun, 12 Jun 2022 10:21:42 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id EB1D58004C; Sun, 12 Jun 2022 10:21:40 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1655043700; bh=GnANLHgJ1JEPintLsLFDkf/5BdPqxjhbrRGAaaOkeP4=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=kN6sqDSEIbTHmhX7V3vffpuvMCccghU4dI4hU8/miLb4W/DMsOC9lH2YxJu8hZYW5 vRvdNQXXEN5XklE7Eeyy8DWecZi5CjX+iCzEMKm69bhQX0wIRcktNREQEBfpOvgDZQ K8KkFKUQsl7ch/1wOxTsEi7p9JCATlknEngyzdCyBlyPgvabWMWrqnZAHpdqaGgRHj k2DgOUf6oo5+RW+NFg/tExb0QduthPuJgbRR5wNu/2kGDgtn6+V0ECs0q+ZhyXF8qa YW43dyZED6w7nJaUGBalkVRjAxbrtK7v9RoSn/BbiRj8MnWml+4rDdfjVJ58GDq6Va SoPmM/JO2Da6Q== Original-Received: from pastel (unknown [45.72.221.51]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id AC1D11204E5; Sun, 12 Jun 2022 10:21:40 -0400 (EDT) In-Reply-To: <83r13uurom.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 12 Jun 2022 13:00:57 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:291094 Archived-At: Eli Zaretskii [2022-06-12 13:00:57] wrote: >> > Any 32-bit build of Emacs is potentially prone to this problem, >> > depending on what time-related APIs it is using. If time_t is a >> > 32-bit type, this problem will still exist. >> >> Thanks for the clarification! >> >> I am now wondering if it is soon going to be the time to do something >> about it. 2037 is getting closer and the 32-bit limitation may become a >> real issue for the 32-bit Emacs builds. > > Yes, at some point in the not-so-distant future we will have to face > the issue. I thought there was nothing to be done on our side: we only suffer from the limitations that are imposed by the libc (and only when the value needs to be passed to libc), and as soon as the underlying OS/libc is updated to avoid those problems, the problem also disappears in Emacs. Stefan