[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: For a cheaper ‘bytevector->pointer’
From: |
Amirouche Boubekki |
Subject: |
Re: For a cheaper ‘bytevector->pointer’ |
Date: |
Mon, 25 Nov 2019 07:26:03 +0100 |
Le dim. 24 nov. 2019 à 11:53, Ludovic Courtès <address@hidden> 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