Installation Issues

[Chk5679]

Hello everyone!,

I am having trouble getting mimalloc-bench to install. When i run the script to install i get a lot of errors like as follows and I'm not sure how to deal with these:

mimalloc-bench/extern/lp/Source/bmalloc/libpas/src/libpas/thingy_heap.c:78:49: error: too few arguments to function call, expected 3, have 2
    return (void*)try_allocate_primitive(size, 1).begin;
                  ~~~~~~~~~~~~~~~~~~~~~~        ^

mimalloc-bench/extern/lp/Source/bmalloc/libpas/src/libpas/thingy_heap.c:67:5: note: 'try_allocate_primitive' declared here
    try_allocate_primitive,
    ^

mimalloc-bench/extern/lp/Source/bmalloc/libpas/src/libpas/thingy_heap.c:83:76: error: too few arguments to function call, expected 3, have 2
    return (void*)pas_allocation_result_zero(try_allocate_primitive(size, 1), size).begin;

[Mohamk1234]

I am having the same issue. Did you find a solution to this, or do you know why this is happening?

[Chk5679]

Hey, the only solution i found was to not install the allocator that caused these problems. I was doing some benchmarks with jemalloc and a changed impl so i removed 2 or 3 other allocators that caused these problems. Overall i have to say tho that mimalloc bench suite was not that pleasent to work with Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Mohammad Khakhariawala ***@***.***> Sent: Thursday, May 2, 2024 5:09:15 AM To: daanx/mimalloc-bench ***@***.***> Cc: ConstantinH ***@***.***>; Author ***@***.***> Subject: Re: [daanx/mimalloc-bench] Installation Issues (Issue #204) I am having the same issue. Did you find a solution to this, or do you know why this is happening? — Reply to this email directly, view it on GitHub<#204 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATRPPTVFBLQFHU2CRW5TV3DZAGU5XAVCNFSM6AAAAABESSV5IWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBZGQ2TCOJVGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[jvoisin]

The issues you're having is because some of the allocators we're being don't compile anymore against recent compilers. It has nothing to do with mimalloc-bench, nor is there anything we can do about it.

[derSteFfi]

well, technically, we can stay up to date with allocator versions if said allocator is still maintained. If it's unmaintained, we can either drop it (at least deactivate it by default) or supply our own patches to fix compiler errors (which is a lot of more work, ofc). It's a bigger topic, though.