From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bernhardout@lsmod.de, emacs-devel@gnu.org,
"Stefan Monnier" <monnier@iro.umontreal.ca>,
"Mattias Engdegård" <mattias.engdegard@gmail.com>
Subject: Re: emacs reproducible builds part1 of 2 : eln
Date: Sat, 10 Feb 2024 11:35:27 -0500 [thread overview]
Message-ID: <yp15xywcm5s.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <yp1a5p9woeg.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Sat, 13 Jan 2024 04:52:55 -0500")
Okay did some more investigation on this and I think I've a decent
understanding of the problem, this is not related to the printer but is
entirely on the native compiler.
When we compile 'vendor-specific-keysyms' the native compiler is doing
its value type propagation collecting all possible return values.
This function is returning various possible different lists.
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. That's the source of the trouble because
these lists gets collected (and then stored into the function type)
inside the eln.
With other type of objects we normalize the list of possible returned
objects (ex symbols) sorting them, but how to do it with list?
Option 1 would be to ignore completly objects behind conses and just
propagating the type (cons). IOW going from:
(subr-type (native-compile '(lambda (x)
(if x
'(1 2)
'(2 3)))))
=> (function (t) (member (1 2) (2 3)))
to
=> (function (t) cons)
Option 2 is to sort those lists to keep the computed function type
stable over different compilation runs.
BTW IIUC CL goes for option 1 [1] but at the time I thought it was easy
(and nice as well) to support the full object behind the cons. Was it a
bad idea?
Thanks
Andrea
[1] <http://clhs.lisp.se/Body/t_member.htm>
next prev parent reply other threads:[~2024-02-10 16:35 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yp15xywcm5s.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.