From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: --with-native-compilation build failure on 32-bit systems Date: Thu, 18 Aug 2022 09:40:41 -0400 Message-ID: References: <86k07nl9qe.fsf@phe.ftfl.ca> <87bksyc36k.fsf@gnus.org> <83h72lvf8g.fsf@gnu.org> <834jyace4m.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29493"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Andrea Corallo , larsi@gnus.org, jrm@ftfl.ca, emacs-devel@gnu.org, emacs@FreeBSD.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Aug 18 15:42:14 2022 Return-path: 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 ) id 1oOfmn-0007Vk-Oi for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Aug 2022 15:42:13 +0200 Original-Received: from localhost ([::1]:38656 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oOfmm-0008Sl-MZ for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Aug 2022 09:42:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50162) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oOflR-0007ir-JH for emacs-devel@gnu.org; Thu, 18 Aug 2022 09:40:49 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:39763) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oOflP-000726-4d; Thu, 18 Aug 2022 09:40:48 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 7599B100142; Thu, 18 Aug 2022 09:40:44 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 1877B100129; Thu, 18 Aug 2022 09:40:43 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1660830043; bh=NCmMWP1WjrWkewzECJScsvGc3cc3dJIuC4SZt48NU90=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=T4YevhV3e7tXjt2BaYpH3Qq81h0U+QapsxxYKBc3NoA6Q5OZZZmim0b+t2IGBLfYp ihOc6f5+o//dXYr3uIfduIrdIN4Ot7G9mYlG8qA6aOyfacqk50ckFahs9lZYMbx5eP a3SnUvEh4TyOI73zMHpvBEaitJen2v3b/1SrgKOXnqaOcX90G0+jo1Y77fubieBB5z jKHuqPLMhhAfQf9ZPZbZ+RrHTpXXLTk8LtANd2dU70gqJXEeohb3kchmAqhAEczpYc pmwDK/tq6NTlcaRANMmh6ajpBN+1v9kN9xKabaiGXD4Z8kviwxO12qP6E5xGDeoD9y 9VoHC8RrtEEng== Original-Received: from pastel (unknown [45.72.195.111]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id D2DE41201DD; Thu, 18 Aug 2022 09:40:42 -0400 (EDT) In-Reply-To: <834jyace4m.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Aug 2022 08:30:33 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:293607 Archived-At: >> - I suspect there's some good reason I'm not aware of why we don't >> eb539e92e9 at all (this is not necessary to fix the reported issue >> tho). > > Like I said earlier, I always thought that this problem doesn't affect > the pdumper builds. Perhaps that's not true with native-compilation? I can't see any good reason not to warn about purespace overflow, regardless if it leads to misbehavior or not: we clearly do want to size the purespace to avoid overflow. Stefan