From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Pip Cet <pipcet@protonmail.com>,
emacs-devel@gnu.org, stefankangas@gmail.com,
gerd.moellmann@gmail.com, monnier@iro.umontreal.ca
Subject: Re: Merging scratch/no-purespace to remove unexec and purespace
Date: Mon, 06 Jan 2025 14:05:18 -0500 [thread overview]
Message-ID: <yp1zfk34vbl.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <86ikqud6x5.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 04 Jan 2025 15:50:46 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sat, 04 Jan 2025 11:12:48 +0000
>> From: Pip Cet <pipcet@protonmail.com>
>> Cc: emacs-devel@gnu.org, stefankangas@gmail.com, acorallo@gnu.org, gerd.moellmann@gmail.com, monnier@iro.umontreal.ca
>>
>> "Eli Zaretskii" <eliz@gnu.org> writes:
>>
>> > Is this about bug#74966? If so, let's not discuss the same issue
>>
>> No. This is about the --enable-checking code treating --lambda-fixup as
>> a forbidden symbol and crashing if it is used in the obvious fashion by
>> any code that happens to be native-compiled, which is the current status
>> on scratch/no-purespace.
>
> Then I'd like to hear Andrea's opinion on this.
My opinion is that, to fix the scratch/no-purespace bug, I'm okay with
the #$ solution if it works. Honestly I'd be fine also using a comp
specific symbol like comp--something which is documented not to be
compilable, maybe less nice but probably less convoluted. Anyway if Pip
prefers #$ and is not too complex I'm okay with that.
Andrea
next prev parent reply other threads:[~2025-01-06 19:05 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 10:47 Merging scratch/no-purespace to remove unexec and purespace Stefan Kangas
2024-12-17 13:12 ` Gerd Möllmann
2024-12-17 14:20 ` Gerd Möllmann
2024-12-17 14:30 ` Gerd Möllmann
2024-12-17 17:56 ` Gerd Möllmann
2024-12-17 18:50 ` Eli Zaretskii
2024-12-17 18:56 ` Gerd Möllmann
2024-12-18 12:55 ` Andrea Corallo
2024-12-18 14:03 ` Gerd Möllmann
2024-12-18 16:05 ` Pip Cet via Emacs development discussions.
2024-12-18 16:30 ` Gerd Möllmann
2024-12-18 16:25 ` Pip Cet via Emacs development discussions.
2024-12-18 22:27 ` Andrea Corallo
2024-12-19 9:28 ` Pip Cet via Emacs development discussions.
2024-12-19 10:38 ` Andrea Corallo
2024-12-19 10:50 ` Stefan Kangas
2024-12-19 12:08 ` Pip Cet via Emacs development discussions.
2024-12-19 17:55 ` Stefan Kangas
2024-12-19 20:13 ` Pip Cet via Emacs development discussions.
2024-12-20 15:59 ` Stefan Monnier
2024-12-20 16:22 ` Pip Cet via Emacs development discussions.
2024-12-20 17:25 ` Gerd Möllmann
2024-12-20 20:35 ` Andrea Corallo
2024-12-20 20:39 ` Pip Cet via Emacs development discussions.
2024-12-21 6:33 ` Gerd Möllmann
2024-12-21 6:56 ` Andrea Corallo
2024-12-20 20:38 ` Pip Cet via Emacs development discussions.
2024-12-20 20:57 ` Gerd Möllmann
2025-01-03 22:36 ` Pip Cet via Emacs development discussions.
2025-01-03 23:50 ` Stefan Monnier
2025-01-04 7:26 ` Eli Zaretskii
2025-01-04 11:12 ` Pip Cet via Emacs development discussions.
2025-01-04 13:50 ` Eli Zaretskii
2025-01-06 19:05 ` Andrea Corallo [this message]
2025-01-07 12:46 ` Pip Cet via Emacs development discussions.
2024-12-20 8:42 ` Pip Cet via Emacs development discussions.
2024-12-18 0:18 ` Stefan Kangas
2024-12-17 19:30 ` Helmut Eller
2024-12-17 20:47 ` Stefan Monnier
2024-12-18 2:15 ` Stefan Kangas
2024-12-18 7:11 ` Helmut Eller
2024-12-18 13:35 ` Pip Cet via Emacs development discussions.
2024-12-18 6:56 ` Helmut Eller
2024-12-21 17:41 ` Helmut Eller
2024-12-21 18:32 ` Gerd Möllmann
2024-12-21 22:19 ` Pip Cet via Emacs development discussions.
2024-12-22 1:28 ` Stefan Kangas
2024-12-22 11:12 ` Pip Cet via Emacs development discussions.
2024-12-22 13:07 ` Eli Zaretskii
2024-12-22 14:12 ` Pip Cet via Emacs development discussions.
2024-12-22 15:51 ` Stefan Monnier
2024-12-22 17:09 ` Gerd Möllmann
2024-12-22 17:10 ` Pip Cet via Emacs development discussions.
2025-01-04 0:09 ` Stefan Monnier
2024-12-22 13:13 ` Pip Cet via Emacs development discussions.
2024-12-22 14:16 ` Helmut Eller
2024-12-18 9:30 ` Pip Cet via Emacs development discussions.
2024-12-18 0:50 ` Po Lu
2024-12-18 2:12 ` Stefan Kangas
2024-12-18 21:26 ` Stefan Monnier
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=yp1zfk34vbl.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=pipcet@protonmail.com \
--cc=stefankangas@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).