From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: How to make aot native-compilation and pdmp creation reproduceable Date: Mon, 09 Oct 2023 17:20:35 +0300 Message-ID: <83edi3x4gc.fsf@gnu.org> References: <87edi6wa63.fsf@thaodan.de> <87v8bgvnmi.fsf@thaodan.de> <83sf6kvyws.fsf@gnu.org> <83jzrwvxnx.fsf@gnu.org> <83il7gvt6m.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="444"; mail-complaints-to="usenet@ciao.gmane.io" Cc: bjorn.bidar@thaodan.de, emacs-devel@gnu.org To: Gerd =?utf-8?Q?M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 09 16:21:36 2023 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 1qpr8Z-000APy-LE for ged-emacs-devel@m.gmane-mx.org; Mon, 09 Oct 2023 16:21:35 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qpr7t-00059P-F3; Mon, 09 Oct 2023 10:20:53 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qpr7s-00059H-Es for emacs-devel@gnu.org; Mon, 09 Oct 2023 10:20:52 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qpr7r-0008UP-A5; Mon, 09 Oct 2023 10:20:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=leiPpzIBnIelTUttnj087KtyBHhp5W4c3vLQed8EMl4=; b=oYP3qDARrQ//AvRHhPR6 bVZf2M3AAcrMc1XLT99Iv4hrk0M4zb0OsULieUq0q9kpxJYGvTKW5QDnpF6K6Y85h8KasCrDcmvpi q8V3s4vlVuqfrJmtXzIJOpqGoppqYX9KmPR6Wu6xkeMF7LM5/wze2YBXnMNQcDQzh/sha8c8CAgRU YYp/37soghu7QknEKAoauvJcYnct0cjIY22hov1GNYQ1wcePIdqSwfl/7KLDStO2tvtLVV1am3OJZ 8+6gtvr03s6mkuMgPVMVdA7aAyq3jy+MKefLfVgMocT5MLDnWzUOhFzMF+0oP3tFk3FCtJyuhBcpw JxxZmCOGfzBrow==; In-Reply-To: (message from Gerd =?utf-8?Q?M?= =?utf-8?Q?=C3=B6llmann?= on Mon, 09 Oct 2023 15:33:59 +0200) 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:311373 Archived-At: > From: Gerd Möllmann > Cc: bjorn.bidar@thaodan.de, emacs-devel@gnu.org > Date: Mon, 09 Oct 2023 15:33:59 +0200 > > Eli Zaretskii writes: > > >> From: Gerd Möllmann > >> Cc: bjorn.bidar@thaodan.de, emacs-devel@gnu.org > >> Date: Mon, 09 Oct 2023 13:55:30 +0200 > >> > >> Eli Zaretskii writes: > >> > >> >> My hypothesis is that x-win.eln changes between builds (print-circle > >> >> etc.) => make-fingerprint computes a different ingerprint and so on. > >> > > >> > If x-win.el didn't change, x-win.eln will not be regenerated, so > >> > something else is at work here. > >> > >> But x-win.elc _did_ change. To cite one of Björn's mails > > > > If x-win.elc or x-win.eln change between builds (meaning x-win.el or > > one of the *.el files it 'require's changed), why do we expect the > > builds to be identical? > > AIAIU, the assumption that an .el file has changed doesn't hold. > Instead, comp.el prints a constant list and produces a different $n= > label in both cases. The diff of the .eln's shows that. If there are > no further diffs in the .eln that weren't shown, everything else is > identical. Once again: why is x-win.el being ELN-compiled in the first place? Are you saying that every time you say "make", we compile all the preloaded *.el files, even if they didn't change? That is definitely not true. So the question IMO is: why is x-win.eln being regenerated?