GNU bug report logs - #78340
[PATCH] New option for comp *.eln file name by the file timestamp of *.el

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lynn Winebarger <owinebar <at> gmail.com>
Cc: sunlin7 <at> hotmail.com, acorallo <at> gnu.org, 78340 <at> debbugs.gnu.org
Subject: bug#78340: [PATCH] New option for comp *.eln file name by the file timestamp of *.el
Date: Mon, 12 May 2025 16:53:01 +0300

> From: Lynn Winebarger <owinebar <at> gmail.com>
> Date: Mon, 12 May 2025 09:42:06 -0400
> Cc: acorallo <at> gnu.org, sunlin7 <at> hotmail.com, 78340 <at> debbugs.gnu.org
> 
> I don't really follow the logic on why the content hash of the current
> source is required to keep emacs from *crashing*, as opposed to just
> being inconsistent with the current source.

How else can you make sure the native code is safe to run?  E.g., what
if the code calls primitives that don't exist in Emacs, or their
signature is different?

> That state of affairs has always been considered acceptable for byte
> compiled libraries.

It was a requirement to prevent crashing a session due to loading
incompatible native code, because loading byte-code doesn't crash.

> So, instead of checking file times, why not just put the content hash
> in the .elc, and if loading the elc would be acceptable (determined by
> file times), then use the value from the elc file (stored in the
> comment block at the start so the Fread procedure is not required).

I don't see how the time stamp of the .elc file is more reliable than
of the .el file.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.