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 09:06:14 +0000 Message-ID: References: <86k07nl9qe.fsf@phe.ftfl.ca> <87bksyc36k.fsf@gnus.org> <83h72lvf8g.fsf@gnu.org> <838rnmceq7.fsf@gnu.org> <83lermarzk.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="21100"; 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 11:24:28 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 1oOblL-0005LD-Uo for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Aug 2022 11:24:27 +0200 Original-Received: from localhost ([::1]:43476 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oOblK-0008GC-TF for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Aug 2022 05:24:26 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45182) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oObTq-00057G-60 for emacs-devel@gnu.org; Thu, 18 Aug 2022 05:06:22 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:64450) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oObTo-0004n3-22; Thu, 18 Aug 2022 05:06:21 -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 27I96EPt026942 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Thu, 18 Aug 2022 09:06:14 GMT In-Reply-To: <83lermarzk.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Aug 2022 11:14:07 +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:293594 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 07:59:22 +0000 >> >> > Thanks, but why does this only affect 32-bit builds? >> >> That's a good question, I guess for some reason we overflowed only on >> the 32-bit builds? > > That's unlikely to happen, AFAIU. It's more likely to be the other > way around: the 64-bit builds overflow sooner, due to wider data > types. That's correct, but is not that simple. I see also pure_size depends on many factors. Ex: I've it as 2000000 on the 32bit build and 3333333 on the 64bit. 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. I pushed the fix for the nativecomp side to master as we understood the mechanism needed improvement. I let maintainers choose for the purespace overflow warning one. Thanks! Andrea