unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Amirouche Boubekki <amirouche.boubekki@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Andy Wingo <wingo@igalia.com>, Guile Devel <guile-devel@gnu.org>
Subject: Re: For a cheaper ‘bytevector->pointer’
Date: Mon, 25 Nov 2019 07:26:03 +0100	[thread overview]
Message-ID: <CAL7_Mo_+k7sC+z_TpL3oRSKGXnsZRkCojreiSeU3govNEqDp9A@mail.gmail.com> (raw)
In-Reply-To: <87zhglzgue.fsf@gnu.org>

Le dim. 24 nov. 2019 à 11:53, Ludovic Courtès <ludo@gnu.org> a écrit :
>
> Hello!
>
> A few days ago David was explaining on #guile how ‘bytevector->pointer’
> was generating too much garbage for his use case.  An idea we came up
> with was to embed the pointer object in the bytevector.

I would be very happy to have a more performant bytevector->pointer
for my OKVS work.

>
> The patch below does that but it leads to segfaults because I’m guessing
> there’s generated bytecode somewhere that still uses the wrong offset; I
> adjusted code that emits ‘pointer-ref/immediate’, what else did I miss?
>
> Also, since we disable internal pointers, we’d need to register an
> additional displacement, and I’m not sure if this is a good idea.
>
> Thoughts?
>
> Thanks,
> Ludo’.
>


-- 
Amirouche ~ https://hyper.dev



  reply	other threads:[~2019-11-25  6:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-24 10:52 For a cheaper ‘bytevector->pointer’ Ludovic Courtès
2019-11-25  6:26 ` Amirouche Boubekki [this message]
2019-11-25  9:05 ` Andy Wingo
2019-11-25 22:03   ` Ludovic Courtès
2019-11-26 10:25     ` Andy Wingo

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=CAL7_Mo_+k7sC+z_TpL3oRSKGXnsZRkCojreiSeU3govNEqDp9A@mail.gmail.com \
    --to=amirouche.boubekki@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.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).