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: MPS: hash tables / obarrays Date: Wed, 29 May 2024 12:52:08 -0400 Message-ID: References: <87plt4keu5.fsf@gmail.com> <87jzjck6hj.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30215"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Helmut Eller , Eli Zaretskii , Emacs Devel To: Gerd =?utf-8?Q?M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 29 18:52:59 2024 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 1sCMXr-0007do-LQ for ged-emacs-devel@m.gmane-mx.org; Wed, 29 May 2024 18:52:59 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sCMXA-0001se-2t; Wed, 29 May 2024 12:52:16 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sCMX8-0001sG-7h for emacs-devel@gnu.org; Wed, 29 May 2024 12:52:14 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sCMX7-00034H-Uh; Wed, 29 May 2024 12:52:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=EtwUjXJhHLMNyhshZijfR/olUq2EV9H1s8u12jDXsFU=; b=Cu4iJhXfv+fmNP2cU+mb t/N6BMqsIx6+SZWlEy2yKGiBIzaUu+YCB29TT8khKbEziHfPbsVysLzndXZAHVOVu50qyTvSrhRXa JRlYkDRsnIjZyn/MHAjFR7ZtQrlvThpo92usQjYUOHFHeLKHB2S3+IfHCXv+6Bzq04CBRoZv7CgXm 3R5G1xTQA3VVdXzkMIIoEFiQis/Z9FKu2E0leVdxyPqAdWezvakX8cDZlRyM3TUHXsJ0tUanhcie/ KwuWAUBYtS/UkAEAqsggvl00bKQc8wC40Qi0MFB1FDKs6BNBy40lOIYripTg7rTHu4Imhtt0tFEql FrOxd5JwJm8dOA==; Original-Received: from acorallo by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1sCMX5-0008EU-1e; Wed, 29 May 2024 12:52:13 -0400 In-Reply-To: ("Gerd =?utf-8?Q?M=C3=B6llman?= =?utf-8?Q?n=22's?= message of "Wed, 29 May 2024 18:28:12 +0200") 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:319701 Archived-At: Gerd M=C3=B6llmann writes: > Helmut Eller writes: > >> On Wed, May 29 2024, Gerd M=C3=B6llmann wrote: >> >>> BTW, I've made another attempt to get a grip on the native build on >>> arm64/macOS. No success. Strangely, when I built with -lmps instead of >>> -lmps-debug that worked. >>> >>> Do you build with -lmps-debug? >> >> Yes, I always used the debug version. Have you tried to the make the >> entire rdstack and the prstack ambiguous roots? Or perhaps there's >> another simple way to rule out bugs with reading/printing? > > I've made the specbindings and bytecode stack ambiguous roots in their > entirety with no effect whatsoever. > > The rd and pr stacks I've left alone because they don't really fit what > little I could see. One example, native-compiled: > > (defun byte-compile-eval (form) > "Eval FORM and mark the functions defined therein. > Each function's symbol gets added to `byte-compile-noruntime-functions'." > (let ((hist-orig load-history) > (hist-nil-orig current-load-list)) > (prog1 (eval form lexical-binding) > (when (byte-compile-warning-enabled-p 'noruntime) > (let* ((hist-new > ;; Get new `current-load-list' for the locally defined funs. > (cons (butlast current-load-list > (length hist-nil-orig)) > load-history))) > > Here length found that the first cons of the hist-nil-orig has been > forwarded. And the C code generated for soeed 0 and 1 is almost > identical. 0 works, 1 doesn't. Hi Gerd, in case you need you can decouple the optimizations we do un our compiler from the GCC ones forcing the number you want in our call to 'gcc_jit_context_set_int_option' in comp.c. That said if you see almost no differences in the pseudo C we ask GCC to compile you've probably got already the answer. Anyway IMO the big diff from -O0 -O1 here should be that values are not constantly loaded and stored into the stack, this might indeed make a difference on the GC. Andrea