unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dale Sedivec <dale@codefu.org>
Cc: 44221@debbugs.gnu.org
Subject: bug#44221: 28.0.50; native-compile fails on cl-lib if delete-region has around advice
Date: Mon, 26 Oct 2020 16:42:01 +0000	[thread overview]
Message-ID: <xjfwnzdey7a.fsf@sdf.org> (raw)
In-Reply-To: <3B1B0B89-30E8-4D73-849E-26D35C281C8A@codefu.org> (Dale Sedivec's message of "Sun, 25 Oct 2020 16:14:03 -0500")

Dale Sedivec <dale@codefu.org> writes:

> 1. Start with emacs -Q
>
> 2. Enter IELM
>
> 3. Add trivial advice to `delete-region':
>
>     (define-advice delete-region (:around (orig-fun &rest args) my:test)
>       (apply orig-fun args))
>
> 4. Attempt native compilation of cl-lib:
>
>     (require 'find-func)
>     (native-compile (find-library-name "cl-lib"))
>
> Expected result: cl-lib experiences native compilation
>
> Actual result:
>
>     *** Eval error ***  Internal native compiler error: "/Users/dale/Applications/Emacs.app/Contents/Resources/lisp/emacs-lisp/cl-lib.el.gz", "not a subr", #[128 "\300\301\302#\207" [apply delete-region@my:test #<subr delete-region> nil] 5 nil "r"]
>
> I discovered this via the volatile-highlights package, which advises
> `delete-region', among other things.

Hi Dale,

thanks for reporting this, fd9e9308d2 should fix the issue.

Please confirm works for you with your package.

Thanks!

  Andrea





  reply	other threads:[~2020-10-26 16:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-25 21:14 bug#44221: 28.0.50; native-compile fails on cl-lib if delete-region has around advice Dale Sedivec
2020-10-26 16:42 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-10-27 20:28   ` Dale Sedivec
2020-10-28 14:13     ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=xjfwnzdey7a.fsf@sdf.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=44221@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=dale@codefu.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).