From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Andrea Corallo <akrl@sdf.org>
Subject: Re: Some native compiler related renaming
Date: Sat, 8 May 2021 21:28:05 +0000 [thread overview]
Message-ID: <YJcCZePhhA3n3+E7@ACM> (raw)
In-Reply-To: <83bl9l9wuz.fsf@gnu.org>
Hello, Eli.
On Sat, May 08, 2021 at 16:30:12 +0300, Eli Zaretskii wrote:
[ .... ]
> I have now written some documentation of this new feature [native
> compilation] in the ELisp manual. Suggestions for improvements are
> welcome. Bonus points for submitting patches that improve this
> documentation.
Thanks. This is most welcome.
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.
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.
I do not claim any bonus points at this stage.
[ .... ]
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2021-05-08 21:28 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 [this message]
2021-05-09 6:49 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YJcCZePhhA3n3+E7@ACM \
--to=acm@muc.de \
--cc=akrl@sdf.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.