From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: --with-native-compilation build failure on 32-bit systems Date: Thu, 18 Aug 2022 08:06:43 +0000 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="12426"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: 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 10:18:49 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 1oOajo-00033k-SX for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Aug 2022 10:18:48 +0200 Original-Received: from localhost ([::1]:56648 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oOajn-0003YM-UF for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Aug 2022 04:18:47 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43534) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oOaYF-00037l-N0 for emacs-devel@gnu.org; Thu, 18 Aug 2022 04:06:58 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:53054) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oOaYD-00057w-8d; Thu, 18 Aug 2022 04:06:50 -0400 Original-Received: from ma.sdf.org (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 27I86hDk029132 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Thu, 18 Aug 2022 08:06:43 GMT 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=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-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:293590 Archived-At: Eli Zaretskii writes: >> From: Andrea Corallo >> Cc: larsi@gnus.org, jrm@ftfl.ca, emacs-devel@gnu.org, emacs@FreeBSD.org >> Date: Wed, 17 Aug 2022 21:01:48 +0000 >> >> > So yeah I guess tomorrow I'll prepare the patch were we keep a list of >> > loaded CU to fix-up. >> >> Right I pushed the fix to scratch/better-cu-fixup so far as: >> >> - I don't know if we want 1a637303b4 and 4bdda39f71 in master or 28. > > The problem doesn't exist on emacs-28, does it? AFAIK we never got a report of it. > I use a 32-bit build > of that branch all the time, including Emacs 28.1 and the pretests of > Emacs 28.2, and never had any problems. > > If the problem doesn't exist on the release branch, I'd prefer to > leave it alone, as these changes are not entirely trivial, although > look quite simple. I agree. >> - 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? Certainly native-compilation was relying more on the GC than the standard build for the discussed mechanism, OTOH I'm not sure how potentially having the GC not functional in temacs is a serious issue. But is also worth considering that, given almost no-one is building with unexec now days, if we don't monitor for purespace overflow in pdumper we'll regularly overflow from time to time without noticing it. Regards Andrea