unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: 64642@debbugs.gnu.org
Subject: bug#64642: 29.0.92; Native compiler doesn't compile dynamically bound functions.
Date: Sat, 15 Jul 2023 09:38:13 +0000	[thread overview]
Message-ID: <ZLJpBSjpLXR_iC21@ACM> (raw)

Hello, Emacs.

In the Emacs 29 pretest version (or the master version):
(i) emacs -Q
(ii) C-x b foo.el <RET>
(iii) M-x emacs-lisp-mode <RET>
Don't set lexical-binding in this buffer.
(iv) Enter a function called foo:
    (defun foo () "foo doc string"
      (lambda (bar) "lambda doc string" (car bar)))
(v) With point after the function, evaluate it with C-x C-e.

(vi) M-: (native-compile 'foo)
This signals an error, native-compiler-error-dyn-func.  This is a bug.

#########################################################################

The immediate cause of the bug is in the version of
comp-spill-lap-function which processes named functions (comp.el).
Unlike the other version of the cl-defmethod (which processes lambda
functions), there is no code for dynamic functions here.

If the intention is not to process dynamic functions, this should be
indicated by an error message rather than a signal.  Personally, I feel
that dynamic functions ought to be handled in Emacs-29.

Fixing this bug should be relatively straightforward, since it should
only involve copying and adapting the corresponding code in the lambda
version of comp-spill-lap-function.

-- 
Alan Mackenzie (Nuremberg, Germany).





             reply	other threads:[~2023-07-15  9:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-15  9:38 Alan Mackenzie [this message]
2023-07-15  9:53 ` bug#64642: 29.0.92; Native compiler doesn't compile dynamically bound functions Eli Zaretskii
2023-07-15 15:17   ` Alan Mackenzie
2023-07-17 13:42     ` Andrea Corallo
2023-07-17 16:06       ` Eli Zaretskii
2023-07-17 17:43         ` Alan Mackenzie
2023-07-19 11:31         ` Alan Mackenzie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZLJpBSjpLXR_iC21@ACM \
    --to=acm@muc.de \
    --cc=64642@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).