From eef8ca1041f2d90fa8361108a8c49b122714f743 Mon Sep 17 00:00:00 2001 From: Daan Date: Mon, 24 Apr 2023 11:29:05 -0700 Subject: [PATCH] update readme --- readme.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/readme.md b/readme.md index f50a0e8e..6f908ab9 100644 --- a/readme.md +++ b/readme.md @@ -402,18 +402,15 @@ on large programs that include other 3rd party components. There are four requirements to make the overriding work robustly: 1. Use the C-runtime library as a DLL (using the `/MD` or `/MDd` switch). - 2. Link your program explicitly with `mimalloc-override.dll` library. To ensure the `mimalloc-override.dll` is loaded at run-time it is easiest to insert some call to the mimalloc API in the `main` function, like `mi_version()` (or use the `/INCLUDE:mi_version` switch on the linker). See the `mimalloc-override-test` project for an example on how to use this. - 3. The `mimalloc-redirect.dll` (or `mimalloc-redirect32.dll`) must be put in the same folder as the main `mimalloc-override.dll` at runtime (as it is a dependency of that DLL). The redirection DLL ensures that all calls to the C runtime malloc API get redirected to mimalloc functions (which reside in `mimalloc-override.dll`). - 4. Ensure the `mimalloc-override.dll` comes as early as possible in the import list of the final executable (so it can intercept all potential allocations).