mimalloc

History

daan 983c96a238 Merge branch 'dev' into dev-exp		2019-07-04 14:46:53 -07:00
..
CMakeLists.txt	initial checkin	2019-06-19 16:26:12 -07:00
main-override.c	add check to see if we truly override the system malloc	2019-06-27 13:34:50 -07:00
main-override.cpp	for windows dynamic override, add standard api override and stop patching new/delete (for now)	2019-07-04 09:29:33 -07:00
main.c	remove lock code from atomics (as it is unused)	2019-06-24 17:54:41 -07:00
main.cpp	initial checkin	2019-06-19 16:26:12 -07:00
readme.md	Add initial testing file, test target, and readme about testing, issue #10 , pr #57	2019-06-27 13:36:19 -07:00
test-api.c	Initial commit of separate memory region layer and improved large OS pages support, see 'memory.c'	2019-07-02 07:23:24 -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_CHECK_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.