From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Merging scratch/no-purespace to remove unexec and purespace
Date: Sat, 04 Jan 2025 15:50:46 +0200
Message-ID: <86ikqud6x5.fsf@gnu.org>
References: <CADwFkmmX7pxzLCRU3aU=oZS1NRdVuxxU-JCHpO2=e3J-mRS55Q@mail.gmail.com>
 <yp1v7vgaapz.fsf@fencepost.gnu.org> <875xng9g48.fsf@protonmail.com>
 <CADwFkmmQteY16=y9_FGz6guFkvrPDgN3mDJFkKQcS-u5hQAS3A@mail.gmail.com>
 <87ttaz98q1.fsf@protonmail.com>
 <CADwFkm=gNE3AxMPW9ow6xUTZ9dej=_FwA8uxU_K-e6-xkcvmHg@mail.gmail.com>
 <87y10b77p7.fsf@protonmail.com> <87ikqvikzr.fsf@protonmail.com>
 <86ldvrf39r.fsf@gnu.org> <875xmuj0k3.fsf@protonmail.com>
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="12238"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: emacs-devel@gnu.org, stefankangas@gmail.com,
 gerd.moellmann@gmail.com, monnier@iro.umontreal.ca
To: Pip Cet <pipcet@protonmail.com>, acorallo@gnu.org
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jan 04 14:51:50 2025
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1tU4ZC-00032q-9y
	for ged-emacs-devel@m.gmane-mx.org; Sat, 04 Jan 2025 14:51:50 +0100
Original-Received: from localhost ([::1] helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces@gnu.org>)
	id 1tU4YV-0005wo-Dp; Sat, 04 Jan 2025 08:51:07 -0500
Original-Received: from eggs.gnu.org ([2001:470:142:3::10])
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>) id 1tU4YN-0005wS-NQ
 for emacs-devel@gnu.org; Sat, 04 Jan 2025 08:51:01 -0500
Original-Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1tU4YJ-00087U-UX; Sat, 04 Jan 2025 08:50:57 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
 mime-version; bh=mmgJMsBryTiAEeMqQQalLeHTkVLtoz9P8lBvqN5jUtE=; b=HG/GNQjbblAQ
 jMA3mLZCOyXPGkkpBu/smklRRXNd4tJgH9uDOxTr2ZzcXOAC4vuOS9rB7+t3/lVEzBSdZ6Y6YpeWZ
 XPJuXi8O5sG7Fbn9fvy5afB98wGexHyZ/0rpRm4bZ7si5cge1dKOB0xNcgAbNVVLEed0KU3pdnG2k
 WIwMGQhjBlo2OgJPXKriPKJvnJuSyDx/DBKWyliOPI2UKPQAtkdhY2M6c0JsdvCr+0oKoxIQeNjg/
 zsNFkRWkpNHza6JdWPxo4or2/Gr2sG3sap9tdGtnMmoP0O/GpUdBKEt0F6/nM6TbT95JQgNgUh/8i
 apxzSJhoc3yRC64d/aOeeg==;
In-Reply-To: <875xmuj0k3.fsf@protonmail.com> (message from Pip Cet on Sat, 04
 Jan 2025 11:12:48 +0000)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Xref: news.gmane.io gmane.emacs.devel:327664
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/327664>

> 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.