From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 65455@debbugs.gnu.org, acorallo@gnu.org
Subject: bug#65455: 30.0.50; Disassemble: error with "free-standing" native compiled function
Date: Tue, 22 Aug 2023 18:39:05 +0300 [thread overview]
Message-ID: <83zg2jrsrq.fsf@gnu.org> (raw)
In-Reply-To: <m2cyzfxkh7.fsf@Mini.fritz.box> (message from Gerd Möllmann on Tue, 22 Aug 2023 15:41:40 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: Andrea Corallo <acorallo@gnu.org>, 65455@debbugs.gnu.org
> Date: Tue, 22 Aug 2023 15:41:40 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > What happens if you do
> >
> > (native-compile 'foo "foo.eln")
> >
> > instead?
> >
> > Adding Andrea.
>
> Ok. I did
>
> (fmakunbound 'foo)
> (defun foo (a b)
> (list a b))
> (native-compile 'foo "foo.eln")
>
> That resulted in an error, with *Messages* containing
>
> comp--native-compile: Native compiler error: foo, "Compiling foo.eln...
> Wrong type argument: stringp, nil
Let's wait for Andrea to chime in. Maybe I misunderstood the intended
way of calling that function or what exactly its 2nd argument is.
next prev parent reply other threads:[~2023-08-22 15:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 13:17 bug#65455: 30.0.50; Disassemble: error with "free-standing" native compiled function Gerd Möllmann
2023-08-22 13:29 ` Eli Zaretskii
2023-08-22 13:41 ` Gerd Möllmann
2023-08-22 15:39 ` Eli Zaretskii [this message]
2023-08-25 8:11 ` Andrea Corallo
2023-08-25 10:30 ` Eli Zaretskii
2023-08-25 11:43 ` Andrea Corallo
2023-08-25 11:47 ` Eli Zaretskii
2023-08-25 11:52 ` Andrea Corallo
2023-08-25 13:01 ` Eli Zaretskii
2023-08-25 14:11 ` Andrea Corallo
2023-08-25 14:56 ` Eli Zaretskii
2023-08-27 13:34 ` Andrea Corallo
2023-08-27 13:40 ` Eli Zaretskii
2023-08-27 15:41 ` Andrea Corallo
2023-08-27 14:43 ` Andrea Corallo
2023-08-27 16:21 ` Eli Zaretskii
2023-08-27 18:04 ` Andrea Corallo
2023-08-27 18:22 ` Eli Zaretskii
2023-10-26 6:53 ` Gerd Möllmann
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=83zg2jrsrq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65455@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=gerd.moellmann@gmail.com \
/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).