[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: emacs reproducible builds part1 of 2 : eln
From: |
Andrea Corallo |
Subject: |
Re: emacs reproducible builds part1 of 2 : eln |
Date: |
Sat, 10 Feb 2024 13:31:22 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> We collect all possible return values iterating over the basic blocks of
>> the functions, these are stored in hash table so we walk order is I
>> believe *not* deterministic.
>
> The walk order is officially undefined, but in practice with the current
> implementation of hash-tables it is fully determined by the order in
> which elements have been added/removed (and unaffected by the hash
> values).
>
> 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?
Thanks
Andrea
- Re: emacs reproducible builds part1 of 2 : eln, Andrea Corallo, 2024/02/10
- Re: emacs reproducible builds part1 of 2 : eln, Stefan Monnier, 2024/02/10
- Re: emacs reproducible builds part1 of 2 : eln,
Andrea Corallo <=
- Re: emacs reproducible builds part1 of 2 : eln, Stefan Monnier, 2024/02/10
- Re: emacs reproducible builds part1 of 2 : eln, Andrea Corallo, 2024/02/10
- Re: emacs reproducible builds part1 of 2 : eln, Andrea Corallo, 2024/02/11
- Re: emacs reproducible builds part1 of 2 : eln, Stefan Monnier, 2024/02/11
- Re: emacs reproducible builds part1 of 2 : eln, Andrea Corallo, 2024/02/11