GNU bug report logs - #71555
29.3.50; Native-compilation sets some variable to nil unexpectedly.

Previous Next

Full log

Message #17 received at 71555 <at> debbugs.gnu.org (full text, mbox):

From: Andrea Corallo <acorallo <at> gnu.org>
To: Sévère Durand <mmemmew <at> gmail.com>
Cc: 71555 <at> debbugs.gnu.org, eliz <at> gnu.org
Subject: Re: bug#71555: 29.3.50; Native-compilation sets some variable to
 nil unexpectedly.
Date: Mon, 17 Jun 2024 04:00:08 -0400

Sévère Durand <mmemmew <at> gmail.com> writes:

> Hello Mr.Andrea:
> Thanks for your reply and that of Mr.Gerd!
> I did not know that this was fixed on the master branch.  In this case, I think I can just add a notification to my
> package's readme, warning users that if they want to natively compile the package, then they should use the master branch
> (or the version 30) to avoid the bug.
> Thanks for the help!
> ---
> Durand

Hi Sévère,

another workaround that should work would be to add to your function:

(declare (speed 0))

This should work around the issue on all the already released releases.

Could you give it a try?

Thanks

  Andrea

Previous Next

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