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 19:35:01 +0000 Message-ID: References: <86k07nl9qe.fsf@phe.ftfl.ca> <83h72lvf8g.fsf@gnu.org> <838rnmceq7.fsf@gnu.org> <83lermarzk.fsf@gnu.org> <83ilmpc2bi.fsf@gnu.org> <83h729c07k.fsf@gnu.org> <83fshtbsy0.fsf@gnu.org> <83k075fx6r.fsf@gnu.org> <83fshtfstd.fsf@gnu.org> <83bkshfpd0.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="29671"; 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 21:36:23 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 1oOlJX-0007XI-8l for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Aug 2022 21:36:23 +0200 Original-Received: from localhost ([::1]:37976 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oOlJW-0005UG-Bh for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Aug 2022 15:36:22 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58092) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oOlIN-00047R-Qe for emacs-devel@gnu.org; Thu, 18 Aug 2022 15:35:11 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:61965) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oOlIL-0000NB-Q5; Thu, 18 Aug 2022 15:35:11 -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 27IJZ1GD000983 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Thu, 18 Aug 2022 19:35:01 GMT In-Reply-To: <83bkshfpd0.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Aug 2022 20:11:55 +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:293619 Archived-At: Eli Zaretskii writes: >> From: Andrea Corallo >> Cc: larsi@gnus.org, jrm@ftfl.ca, emacs-devel@gnu.org, emacs@FreeBSD.org >> Date: Thu, 18 Aug 2022 16:42:24 +0000 >> >> > So even if PURESIZE_RATIO and PURESIZE_CHECKING_RATIO are both 1, how >> > come you get 2000000 in the 32-bit build, when SYSTEM_PURESIZE_EXTRA >> > is zero? I must be missing something. >> >> It's 2000000 as my testbed for this bug as mentioned it is based on >> aff5961274 (a master around the time the bug was reported), so before >> your e46668847d. Your commit changed the constant we add for computing >> BASE_PURESIZE from 2000000 to 2750000. > > Ah, okay. So I guess the current values are already large enough, and > we don't need to do anything with this issue. Agree, still to be decided if warning when purespace is overflowed. I really don't see why we should not do that, so I propose to have a7abd8f235 and def6d57669 from scratch/pure-overflow-warn into master. Thanks Andrea