From: Andrea Corallo <acorallo@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Eli Zaretskii" <eliz@gnu.org>,
bernhardout@lsmod.de, emacs-devel@gnu.org,
"Mattias Engdegård" <mattias.engdegard@gmail.com>,
"Bernhard M. Wiedemann" <bernhardout@lsmod.de>
Subject: Re: emacs reproducible builds part1 of 2 : eln
Date: Sun, 11 Feb 2024 05:24:10 -0500 [thread overview]
Message-ID: <yp1sf1zb8ol.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <yp1wmrcawdp.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Sat, 10 Feb 2024 15:37:38 -0500")
Andrea Corallo <acorallo@gnu.org> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>>> So, I'm not sure it explains the phenomenon you're seeing (I haven't
>>>> seen the rest of this thread yet).
>>>
>>> Interesting, I imagined the walk order is defined but my question is
>>> what about two hash table with the same content but created in two
>>> different sessions?
>>
>> Depends how they were filled: if they were filles by the same sequence
>> of operations, then they should have the same walk-order.
>> If not, then all bets are off.
>
> Okay that's good news, I'll investigate more tomorrow, the case is
> pretty well defined now so should be possible to understand exactly what
> is going on.
Okay cool I pushed a fix in emacs29, with that installed we don't try to
sort anymore conses based on their 'sxhash-equal' value because this is
not stable over different Emacs sessions. With the change installed the
build looks finally reproducible here.
Bernhard please let us know if this solves the problem on your side as
well.
Thanks
Andrea
next prev parent reply other threads:[~2024-02-11 10:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 21:17 emacs reproducible builds part1 of 2 : eln Bernhard M. Wiedemann
2024-01-12 8:22 ` Eli Zaretskii
2024-01-12 16:19 ` Andrea Corallo
2024-01-12 16:26 ` Eli Zaretskii
2024-01-13 9:52 ` Andrea Corallo
2024-02-10 16:35 ` Andrea Corallo
2024-02-10 17:45 ` Stefan Monnier
2024-02-10 18:31 ` Andrea Corallo
2024-02-10 18:44 ` Stefan Monnier
2024-02-10 20:37 ` Andrea Corallo
2024-02-11 10:24 ` Andrea Corallo [this message]
2024-02-11 20:13 ` Stefan Monnier
2024-02-11 21:44 ` Andrea Corallo
2024-05-22 6:06 ` Bernhard M. Wiedemann
2024-05-22 12:31 ` Eli Zaretskii
2024-05-27 17:33 ` Andrea Corallo
2024-05-28 15:20 ` Andrea Corallo
2024-05-31 7:26 ` Bernhard M. Wiedemann
2024-05-31 7:44 ` Andrea Corallo
2024-05-31 8:22 ` Bernhard M. Wiedemann
2024-05-31 10:45 ` Eli Zaretskii
2024-05-31 10:33 ` Eli Zaretskii
2024-01-12 16:14 ` Simon Tournier
2024-01-12 20:13 ` Eli Zaretskii
2024-02-12 7:10 ` Björn Bidar
[not found] ` <87il2ub1jy.fsf@>
2024-02-12 8:17 ` Andrea Corallo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yp1sf1zb8ol.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=bernhardout@lsmod.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).