From: Andrea Corallo <akrl@sdf.org>
To: Vibhav Pant <vibhavp@gmail.com>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: scratch/comp-static-data 5aa3db2f11: comp: Add support for compiling elisp constants into static data.
Date: Thu, 17 Nov 2022 19:59:39 +0000 [thread overview]
Message-ID: <xjfv8ndcpxw.fsf@ma.sdf.org> (raw)
In-Reply-To: <f4222827186442c0e61cb946537c890d3ed3cadc.camel@gmail.com> (Vibhav Pant's message of "Thu, 17 Nov 2022 01:06:39 +0530")
Vibhav Pant <vibhavp@gmail.com> writes:
[...]
> Hi Andrea,
>
> This branch was mostly inspired by your comment in `emit_static_object'
> that mentioned how libgccjit didn't support static initializers
> (presumably back then). Now that there is some support for initializing
> static globals with constant expressions, I have been working on this
> patch for the last few weeks with the aim of trying to reduce the use
> of `read' for initializing constants referenced by elisp code
> (therefore drastically reducing the amount of heap allocations and
> improving eln load times), by compiling them into the eln as static
> (optionally const) data. Think of it as every eln module having its own
> pure storage.
>
> There are still a bunch of TODOs, the first one being reducing the size
> of the generated binaries (which is mostly due to how `comp_init_obj'
> works right now). Nonetheless, I decided to make this code public once
> it was passing basic sanity tests (including the comp-tests.el suite)
> and was in a more or less working condition as a daily driver. As a
> result, the branch is still a WIP, but I will try to document more of
> the code moving forward.
>
> Best,
> Vibhav
Hi Vibhav,
as usual when you are ready I suggest you to show the pseudo C generated
with native-comp-debug >= 2 for the stock system and for the one with
your patch. This for a _minimal_ example.
Thanks for working on this.
Andrea
next prev parent reply other threads:[~2022-11-17 19:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166844679660.19180.3470364122428955894@vcs2.savannah.gnu.org>
[not found] ` <20221114172637.78215C0E4C7@vcs2.savannah.gnu.org>
2022-11-15 0:30 ` scratch/comp-static-data 5aa3db2f11: comp: Add support for compiling elisp constants into static data Po Lu
2022-11-15 9:06 ` Andrea Corallo
2022-11-16 19:36 ` Vibhav Pant
2022-11-17 19:59 ` Andrea Corallo [this message]
2022-11-17 4:32 ` Richard Stallman
2022-11-17 8:46 ` Vibhav Pant
2022-11-18 5:07 ` Richard Stallman
2022-11-18 8:28 ` Eli Zaretskii
2022-11-20 1:15 ` Richard Stallman
2022-11-20 7:37 ` Eli Zaretskii
2022-11-20 16:37 ` vibhavp
2022-11-20 16:54 ` Eli Zaretskii
2022-11-20 18:47 ` Stefan Monnier
2022-11-21 15:59 ` vibhavp
2022-11-21 0:37 ` Po Lu
2022-11-16 19:26 ` Vibhav Pant
2022-11-17 4:51 ` Po Lu
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=xjfv8ndcpxw.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=vibhavp@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).