From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: --with-native-compilation build failure on 32-bit systems Date: Thu, 18 Aug 2022 13:31:11 +0300 Message-ID: <83h729c07k.fsf@gnu.org> References: <86k07nl9qe.fsf@phe.ftfl.ca> <87bksyc36k.fsf@gnus.org> <83h72lvf8g.fsf@gnu.org> <838rnmceq7.fsf@gnu.org> <83lermarzk.fsf@gnu.org> <83ilmpc2bi.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39854"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, jrm@ftfl.ca, emacs-devel@gnu.org, emacs@FreeBSD.org To: Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Aug 18 12:33:01 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 1oOcpg-000A66-Ol for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Aug 2022 12:33:00 +0200 Original-Received: from localhost ([::1]:45926 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oOcpf-0007xD-3Q for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Aug 2022 06:32:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55542) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oOco8-0007Ez-LT for emacs-devel@gnu.org; Thu, 18 Aug 2022 06:31:27 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:56066) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oOco6-0001q4-8C; Thu, 18 Aug 2022 06:31:22 -0400 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=gRUpeFytJuJlRYspPqaOPCEFlnN2hnKltiKuIdzIRxQ=; b=LREvJiDJK7am kNs1iX5rHKtQ+a1jhkMLQqo8VTuRJ6+u1KESSqQSUaGOUa+x6x3X1JqdSt+AQhj3kbHRmlK9syztN 6tI1793Qa4QwRz/Xuk9RHi80ZrrKKxbv3A+D6Xf+X9ZSDOef5ai7lCpTPy9PiUiEjBWn/ZKYa9aDG ApxbrtlagP6EdAQBfE8twIO/6t6eqgpM+K4Ji3jh9/dXHnKok6kH/DxndEzt4PbaGFVIpXLiknKwN PWQ7a1/gdiCu3KmHoQEl/TyBuuCBH4UVZwNmCItKnPptVYrnS4qM//Ke03r5qRPzAWDh8PZ6Er6O/ oH5bNhStONagio99im68XA==; Original-Received: from [87.69.77.57] (port=4727 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oOco3-00062e-2n; Thu, 18 Aug 2022 06:31:22 -0400 In-Reply-To: (message from Andrea Corallo on Thu, 18 Aug 2022 09:57:32 +0000) 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:293598 Archived-At: > From: Andrea Corallo > Cc: larsi@gnus.org, jrm@ftfl.ca, emacs-devel@gnu.org, emacs@FreeBSD.org > Date: Thu, 18 Aug 2022 09:57:32 +0000 > > Eli Zaretskii writes: > > >> What I see comparing the two builds (my testbed is ATM on aff5961274) is > >> that we overflow on both, but on the 64bit we do it a little later in > >> the execution so the GC has the chance to collect ediff-hook before we > >> overflow purespace. > > > > That's strange, because I just built the unexec build on a 64-bit > > system, and it didn't overflow for me. > > > > Does it overflow on your system during bootstrap, i.e. when it loads > > all the Lisp packages in source form? Or does it overflow when it > > loads the *.elc byte-compiled files? Or is this a native-comp build, > > and it overflows when loading the *.eln files? > > Mine is a build with native compilation, there are many variables into > play and indeed native compilation might be one of the main responsible > for the higher use the purespace here. > > It does overflow during bootstrap after having loaded the eln files. How many more bytes do you need to avoid overflowing? I guess we will need to enlarge SYSTEM_PURESIZE_EXTRA in the native-comp build. The question above will allow to figure out by how much to enlarge it.