sglang_v0.5.2/pytorch_2.8.0/third_party/mimalloc/test
hailin c8e8c1e9ff . 2025-09-20 16:09:34 +08:00
..
CMakeLists.txt . 2025-09-20 16:09:34 +08:00
main-override-dep.cpp . 2025-09-20 16:09:34 +08:00
main-override-dep.h . 2025-09-20 16:09:34 +08:00
main-override-static.c . 2025-09-20 16:09:34 +08:00
main-override.c . 2025-09-20 16:09:34 +08:00
main-override.cpp . 2025-09-20 16:09:34 +08:00
main.c . 2025-09-20 16:09:34 +08:00
readme.md . 2025-09-20 16:09:34 +08:00
test-api-fill.c . 2025-09-20 16:09:34 +08:00
test-api.c . 2025-09-20 16:09:34 +08:00
test-stress.c . 2025-09-20 16:09:34 +08:00
test-wrong.c . 2025-09-20 16:09:34 +08:00
testhelper.h . 2025-09-20 16:09:34 +08: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.