[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [feature/native-comp] breakage on build

From: Eli Zaretskii
Subject: Re: [feature/native-comp] breakage on build
Date: Sun, 31 Jan 2021 17:29:30 +0200

> From: Andrea Corallo <akrl@sdf.org>
> Cc: phillip.lord@russet.org.uk,  emacs-devel@gnu.org
> Date: Sat, 30 Jan 2021 20:17:58 +0000
> >> native-lisp/28.0.50-x86_64-w64-mingw32-HASH1/titdic-cnv-HASH2-HASH3.eln
> >> 
> >> - HASH1 disambiguate triplet, Emacs configuration, version etc.
> >
> > But that information is already present in the text before:
> > 28.0.50-x86_64-w64-mingw32.  What else is missing that we need a hash?
> I left the text before as indicative and human readable but
> unfortunatelly that's not complete.
> The list of all primitive functions contribute to the eln linking
> mechanism we use and is accounted in this hash.  Also we can trigger the
> generation of a new hash each time we deploy an eln ABI breaking change.

Sorry, I don't follow.  You said HASH1 disambiguates the triplet, and
that is already present in the name.  Please elaborate on the other
factors that affect HASH1, as what you said (primitives that
contribute? eln ABI breaking changes?) isn't enough for me to
understand what information they record.  And in any case, if the
triplet is in HASH1, why not remove its human-readable representation
and save a few bytes?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]