From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org, akrl@sdf.org
Subject: Re: Some native compiler related renaming
Date: Sun, 09 May 2021 09:49:45 +0300 [thread overview]
Message-ID: <83sg2w8kqe.fsf@gnu.org> (raw)
In-Reply-To: <YJcCZePhhA3n3+E7@ACM> (message from Alan Mackenzie on Sat, 8 May 2021 21:28:05 +0000)
> Date: Sat, 8 May 2021 21:28:05 +0000
> Cc: Andrea Corallo <akrl@sdf.org>, emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> The function `disassemble' works on natively compiled functions now, as
> well as on byte-compiled functions. Perhaps this should be mentioned
> somewhere in the new section about native compilation. I think the page
> "Disassembly" in the Elisp manual might need some radical surgery, to
> make it read smoothly for both types of compiled function.
That's a good idea, but I'd need some place with the description of
using that for native code, or someone who has experience in doing
that will have to describe that first. Any pointers?
> There may be other functions which Andrea has also enhanced to work on
> native compiled code. I found out about disassemble because I needed
> it, and I just tried it.
Specific function names whose descriptions you think need updates for
the native compilation would be welcome.
next prev parent reply other threads:[~2021-05-09 6:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 15:17 Some native compiler related renaming Andrea Corallo via Emacs development discussions.
2021-05-08 13:30 ` Eli Zaretskii
2021-05-08 15:03 ` Basil L. Contovounesios
2021-05-08 15:50 ` Eli Zaretskii
2021-05-08 17:01 ` Basil L. Contovounesios
2021-05-08 21:28 ` Alan Mackenzie
2021-05-09 6:49 ` Eli Zaretskii [this message]
2021-05-10 7:42 ` Andrea Corallo via Emacs development discussions.
2021-05-11 8:40 ` Andrea Corallo via Emacs development discussions.
2021-05-11 12:26 ` Eli Zaretskii
2021-05-11 16:33 ` Andrea Corallo via Emacs development discussions.
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=83sg2w8kqe.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=akrl@sdf.org \
--cc=emacs-devel@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).