GNU bug report logs -
#78394
31.0.50; Questions about native-comp-speed and type decl
Previous Next
Reported by: "Yue Yi" <include_yy <at> qq.com>
Date: Mon, 12 May 2025 15:56:01 UTC
Severity: normal
Found in version 31.0.50
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Sat, 12 Jul 2025 12:16:10 +0300
with message-id <86h5zheplx.fsf <at> gnu.org>
and subject line Re: bug#78394: 31.0.50; Questions about native-comp-speed and type decl
has caused the debbugs.gnu.org bug report #78394,
regarding 31.0.50; Questions about native-comp-speed and type decl
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
78394: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=78394
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
[Message part 3 (text/plain, inline)]
Hello Emacs maintainers, When modifying an org HTML export backend, I tentatively added type annotations to a function to make the code run faster. However, during unit testing, byte compilation produced correct results, while native compilation did not. Specifically, the following cleaned-up code illustrates the issue: --------------------------->8<----------------------------- (defconst my/plist '(:html-checkbox-type unicode)) (defconst t-checkbox-types '(( unicode . ((on . "☑") (off . "☐") (trans . "☒"))))) (let ((native-comp-speed 2)) (defun t--checkbox (checkbox info) "Format CHECKBOX into HTML." (declare (ftype (function (t plist) string)) (side-effect-free t) (important-return-value t)) (cdr (assq checkbox (cdr (assq (plist-get info :html-checkbox-type) t-checkbox-types))))) (defun t--format-checkbox (checkbox info) "Format a CHECKBOX option to string. CHECKBOX can be `on', `off', `trans', or anything else. Returns an empty string if CHECKBOX is not one of the these three." (declare (ftype (function (t plist) string)) (side-effect-free t) (important-return-value t)) (let ((a (t--checkbox checkbox info))) (concat a (and a " ")))) ;; native comp (native-compile 't--checkbox) (native-compile 't--format-checkbox)) --------------------------->8<----------------------------- AFACK, the default value of `native-comp-speed' is 2. In this case, the behavior of the following code is inconsistent with that of the byte-compiled or non-compiled code: --------------------------->8<----------------------------- ;; normal (t--format-checkbox nil my/plist) ;;=> "" ;; byte-code (t--format-checkbox nil my/plist) ;;=> "" ;; speed 1 (t--format-checkbox nil my/plist) ;;=> "" ;; speed 2 (t--format-checkbox nil my/plist) ;;=> " " --------------------------->8<----------------------------- Of course, we can notice that the type declaration for `t--checkbox' is problematic --- its return type should be (or null string) instead of string. After correcting this mistake, the function works properly under speed=2. In C, we generally avoid aggressive optimizations because they can lead to unpredictable behavior. What I’d like to ask is whether similar situations can occur in Emacs Lisp’s native compilation as well --- like the issue I encountered here? Another question is about `compilation-safety'. As I understand it, when set to 1, it prevents Emacs from crashing due to faulty optimizations. Does this mean the variable only guards against the most severe cases, rather than ensuring the correctness of optimizations in general? Best regards.
[Message part 4 (text/html, inline)]
[Message part 5 (message/rfc822, inline)]
> From: "Yue Yi" <include_yy <at> qq.com>
> Cc: "acorallo" <acorallo <at> gnu.org>, "78394" <78394 <at> debbugs.gnu.org>
> Date: Sat, 12 Jul 2025 16:19:55 +0800
>
> It鈥檚 good enough for me, feel free to close it, TIA.
Thanks, closing.
This bug report was last modified 1 day ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.