From: "Ludovic Courtès" <ludo@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@igalia.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: Immediate doubles (up to 2^256) and rationals coming to Guile 3
Date: Tue, 11 Jun 2019 14:21:55 +0200 [thread overview]
Message-ID: <875zpc1fdo.fsf@gnu.org> (raw)
In-Reply-To: <87y32875ib.fsf@netris.org> (Mark H. Weaver's message of "Tue, 11 Jun 2019 06:58:09 -0400")
Hi,
Mark H Weaver <mhw@netris.org> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>> Though an immediate, like a fixnum or an iflo, is still something
>> different from a tagged heap object like a pair, right? So I would
>> expect SCM_THOB_P to be a different test, not a drop-in replacement for
>> SCM_NIMP, is that correct?
>
> That's right. It's not possible to create a drop-in replacement for
> SCM_NIMP, because it is being used to answer two different questions
> which used to be effectively equivalent, but no longer are:
>
> (1) Is X a pointer to a heap object with a heap tag in the first word?
> (2) Is X a reference to a heap object?
>
> Test (1) needs to be done before checking the heap tag, to implement
> type predicates for heap objects. Test (2) is needed in relatively few
> places, e.g. to decide whether to register disappearing links when
> adding an entry to a weak hash table.
>
> Actually, in my current branch I've removed the SCM_IMP and SCM_NIMP
> macros outright, because it seems to me they are likely to be misused.
>
> SCM_THOB_P implements test (1) and SCM_HEAP_OBJECT_P implements test (2).
I see.
> There's no masking involved. Rather, it is subtracted from the pointer,
> which allows the tag to be fused with the field offset. For example, on
> x86-64, whereas CAR and CDR were previously:
>
> 1c0: 48 8b 07 mov (%rdi),%rax ;old car
> and:
> 1d0: 48 8b 47 08 mov 0x8(%rdi),%rax ;old cdr
>
> Now they become:
>
> 1e0: 48 8b 47 fa mov -0x6(%rdi),%rax ;new car
> and:
> 1f0: 48 8b 47 02 mov 0x2(%rdi),%rax ;new cdr
Looks reasonable. :-)
> Fortunately, BDW-GC provides GC_REGISTER_DISPLACEMENT, which allows us
> to register a small offset K, such that BDW-GC should recognize pointers
> that point K bytes into a heap block. We've been using this in both 2.0
> and 2.2 from scm_init_struct (), and in 'master' it's done in
> scm_storage_prehistory ().
>
> This new approach entails registering one additional displacement.
Cool; if it’s just one displacement, that’s OK.
> What do you think?
It all looks perfectly reasonable to me!
Thanks for explaining,
Ludo’.
next prev parent reply other threads:[~2019-06-11 12:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 9:40 Immediate doubles (up to 2^256) and rationals coming to Guile 3 Mark H Weaver
2019-06-06 12:56 ` Mark H Weaver
2019-06-06 19:37 ` Arne Babenhauserheide
2019-06-12 0:03 ` Mark H Weaver
2019-06-06 20:09 ` tomas
2019-06-07 19:46 ` Ludovic Courtès
2019-06-09 16:56 ` Mark H Weaver
2019-06-09 17:30 ` Mark H Weaver
2019-06-11 8:39 ` Ludovic Courtès
2019-06-11 10:58 ` Mark H Weaver
2019-06-11 12:21 ` Ludovic Courtès [this message]
2019-06-11 11:34 ` Mark H Weaver
2019-06-08 1:13 ` Mark H Weaver
2019-06-08 8:07 ` Arne Babenhauserheide
2019-06-08 9:08 ` Chris Vine
2019-06-08 9:46 ` Arne Babenhauserheide
2019-06-08 10:24 ` Chris Vine
2019-06-08 13:12 ` Hans Åberg
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zpc1fdo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@igalia.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.
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).