mimalloc

History

daan eee7c40da5 updates to run valgrind on test-api		2022-10-29 11:43:09 -07:00
..
CMakeLists.txt	initial progress on valgrind integration	2022-10-28 19:54:56 -07:00
main-override-static.c	nicer heap walk test	2022-04-09 14:08:27 -07:00
main-override.c	introduces netbsd's reallocarr overriding.	2021-12-01 22:43:13 +00:00
main-override.cpp	further fixes to allow statically linking mimalloc in DLL modules (issue #508 )	2022-01-10 16:07:22 -08:00
main.c	remove lock code from atomics (as it is unused)	2019-06-24 17:54:41 -07:00
readme.md	update documentation	2019-11-21 16:09:34 -08:00
test-api-fill.c	fix test macros	2022-04-19 10:49:39 -07:00
test-api.c	updates to run valgrind on test-api	2022-10-29 11:43:09 -07:00
test-stress.c	add zero parameter to primitive allocation to improve codegen for calloc etc	2022-04-19 18:32:35 -07:00
test-wrong.c	updates to run valgrind on test-api	2022-10-29 11:43:09 -07:00
testhelper.h	fix test macros	2022-04-19 10:49:39 -07:00

readme.md

Testing allocators is difficult as bugs may only surface after particular allocation patterns. The main approach to testing mimalloc is therefore to have extensive internal invariant checking (see page_is_valid in page.c for example), which is enabled in debug mode with -DMI_DEBUG_FULL=ON. The main testing strategy is then to run mimalloc-bench using full invariant checking to catch any potential problems over a wide range of intensive allocation benchmarks and programs.

However, this does not test well for the entire API surface and this is tested with test-api.c when using make test (from out/debug etc). (This is not complete yet, please add to it.)

The main.c and main-override.c are there to test if building and overriding from a local install works and therefore these build a separate test/CMakeLists.txt.