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

Previous Next

Package: emacs;

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

Date: Fri, 14 Jun 2024 16:14:02 UTC

Severity: normal

Found in version 29.3.50

Done: Andrea Corallo <acorallo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #46 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 10:41:38 -0400
Andrea Corallo <acorallo <at> gnu.org> writes:

> Sévère Durand <mmemmew <at> gmail.com> writes:
>
>> Hello Mr.Andrea:
>> Thanks for the suggestion.
>> Unfortunately when I tried the afore-mentionned snippet with `(declare (speed 0))` added after the documentation string
>> of the `test` function, the execution results still indicate that the START variable is unexpectedly set to nil, for some
>> reason.
>
> I think it's because you are giving to the native compiler an already
> defined function to compile.
>
> If you use M-x emacs-lisp-native-compile-and-load or (load
> (native-compile FILE)) it will work.  I tried the first on 29 and work
> around the original issue successfully.
>
> BTW I believe this different handling of the declare could be worth a
							^^^
                                                       should
> separate bug.
>
> Thanks
>
>   Andrea




This bug report was last modified 337 days ago.

Previous Next


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