mimalloc

History

daan a5071eb510 Merge branch 'dev' into dev-win		2019-08-20 07:50:03 -07:00
..
CMakeLists.txt	more comments	2019-07-23 15:00:13 -07:00
main-override-static.c	add huge and giant stats; increase bins	2019-08-10 20:51:37 -07:00
main-override.c	update test files and overriding	2019-07-23 15:00:13 -07:00
main-override.cpp	merge from 'dev-exp'; add support for MIMALLOC_OVERRIDE environment variable	2019-07-26 12:06:15 -07:00
main.c	remove lock code from atomics (as it is unused)	2019-06-24 17:54:41 -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	fix option_enable call	2019-08-20 07:49:40 -07:00
test-stress.c	use 1GiB huge pages on windows when reserving upfront	2019-08-19 18:16:12 -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.