From: Eli Zaretskii <eliz@gnu.org>
To: vibhavp@gmail.com, rms@gnu.org
Cc: akrl@sdf.org, 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: Sun, 20 Nov 2022 09:37:27 +0200 [thread overview]
Message-ID: <83zgcm5b60.fsf@gnu.org> (raw)
In-Reply-To: <E1owYvl-00044o-F4@fencepost.gnu.org> (message from Richard Stallman on Sat, 19 Nov 2022 20:15:33 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: vibhavp@gmail.com, akrl@sdf.org, luangruo@yahoo.com,
> emacs-devel@gnu.org
> Date: Sat, 19 Nov 2022 20:15:33 -0500
>
> > I'm not aware of any aspect of the change which would cause crashes in
> > these cases.
>
> It is possible I misunderstood what the change was for. The message
> seemed to say that it would put the values of variables defined with
> `defconst' into read-only memory. If there are cases in which that
> affects the program's execution, I expect it will cause a failure of
> some sort in those same cases.
I'd need to understand what does "read-only memory" mean in this context.
Does the code use some memory-protection capabilities to enforce that? Or
does it do something else?
Vibhav, please chime in and help us understand what the code does.
next prev parent reply other threads:[~2022-11-20 7:37 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
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 [this message]
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=83zgcm5b60.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akrl@sdf.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=rms@gnu.org \
--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).