From: Andrea Corallo <acorallo@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Helmut Eller <eller.helmut@gmail.com>,
Eli Zaretskii <eliz@gnu.org>, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: MPS: hash tables / obarrays
Date: Wed, 29 May 2024 12:52:08 -0400 [thread overview]
Message-ID: <yp1wmncsgqv.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m28qzseg6b.fsf@pro2.fritz.box> ("Gerd Möllmann"'s message of "Wed, 29 May 2024 18:28:12 +0200")
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> Helmut Eller <eller.helmut@gmail.com> writes:
>
>> On Wed, May 29 2024, Gerd Möllmann 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
next prev parent reply other threads:[~2024-05-29 16:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 8:38 MPS: hash tables / obarrays Gerd Möllmann
2024-05-19 8:57 ` Eli Zaretskii
2024-05-19 9:12 ` Gerd Möllmann
2024-05-19 9:50 ` Helmut Eller
2024-05-19 10:14 ` Gerd Möllmann
2024-05-19 10:30 ` Helmut Eller
2024-05-19 11:21 ` Gerd Möllmann
2024-05-19 20:36 ` Helmut Eller
2024-05-20 4:27 ` Gerd Möllmann
2024-05-20 6:13 ` Gerd Möllmann
2024-05-20 8:10 ` Helmut Eller
2024-05-20 8:43 ` Gerd Möllmann
2024-05-29 12:00 ` Helmut Eller
2024-05-29 13:30 ` Gerd Möllmann
2024-05-29 15:00 ` Helmut Eller
2024-05-29 16:28 ` Gerd Möllmann
2024-05-29 16:52 ` Andrea Corallo [this message]
2024-05-29 18:03 ` Gerd Möllmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yp1wmncsgqv.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).