[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GUILE 2/3 and string encoding cost
From: |
Han-Wen Nienhuys |
Subject: |
Re: GUILE 2/3 and string encoding cost |
Date: |
Fri, 24 Jan 2020 18:20:08 +0100 |
On Fri, Jan 24, 2020 at 6:09 PM Han-Wen Nienhuys <address@hidden> wrote:
> Both your hunches were correct:
>
> the code below works, but it makes the GC time go from 2s to 5s.
Probably a lot of overhead would go away if we could properly pair up
GC_FREE with GC_MALLOC from libgc, but I can't get this to pass
GUILE's init phase.
I have some other ideas: I think we could instead define a
ly::vector<> that uses a custom allocator. The smob classes could then
define their own operator new, that uses scm_gc_malloc.
It willl have to wait for next week though.
--
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen
- Re: GUILE 2/3 and string encoding cost, (continued)
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, Han-Wen Nienhuys, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, Han-Wen Nienhuys, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, Han-Wen Nienhuys, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, Han-Wen Nienhuys, 2020/01/24
- Re: GUILE 2/3 and string encoding cost,
Han-Wen Nienhuys <=
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, Han-Wen Nienhuys, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24