update documentation
This commit is contained in:
parent
0a708fec7d
commit
bb6afb7efd
@ -1009,28 +1009,31 @@ or via environment variables.
|
|||||||
- `MIMALLOC_SHOW_STATS=1`: show statistics when the program terminates.
|
- `MIMALLOC_SHOW_STATS=1`: show statistics when the program terminates.
|
||||||
- `MIMALLOC_VERBOSE=1`: show verbose messages.
|
- `MIMALLOC_VERBOSE=1`: show verbose messages.
|
||||||
- `MIMALLOC_SHOW_ERRORS=1`: show error and warning messages.
|
- `MIMALLOC_SHOW_ERRORS=1`: show error and warning messages.
|
||||||
- `MIMALLOC_PAGE_RESET=1`: reset (or purge) OS pages when not in use. This can reduce
|
- `MIMALLOC_PAGE_RESET=0`: by default, mimalloc will reset (or purge) OS pages when not in use to signal to the OS
|
||||||
memory fragmentation in long running (server) programs. If performance is impacted,
|
that the underlying physical memory can be reused. This can reduce memory fragmentation in long running (server)
|
||||||
`MIMALLOC_RESET_DELAY=`_msecs_ can be set higher (100ms by default) to make the page
|
programs. By setting it to `0` no such page resets will be done which can improve performance for programs that are not long
|
||||||
reset occur less frequently.
|
running. As an alternative, the `MIMALLOC_RESET_DELAY=`<msecs> can be set higher (100ms by default) to make the page
|
||||||
- `MIMALLOC_LARGE_OS_PAGES=1`: use large OS pages when available; for some workloads this can significantly
|
reset occur less frequently instead of turning it off completely.
|
||||||
|
- `MIMALLOC_LARGE_OS_PAGES=1`: use large OS pages (2MiB) when available; for some workloads this can significantly
|
||||||
improve performance. Use `MIMALLOC_VERBOSE` to check if the large OS pages are enabled -- usually one needs
|
improve performance. Use `MIMALLOC_VERBOSE` to check if the large OS pages are enabled -- usually one needs
|
||||||
to explicitly allow large OS pages (as on [Windows][windows-huge] and [Linux][linux-huge]). However, sometimes
|
to explicitly allow large OS pages (as on [Windows][windows-huge] and [Linux][linux-huge]). However, sometimes
|
||||||
the OS is very slow to reserve contiguous physical memory for large OS pages so use with care on systems that
|
the OS is very slow to reserve contiguous physical memory for large OS pages so use with care on systems that
|
||||||
can have fragmented memory (for that reason, we generally recommend to use `MIMALLOC_RESERVE_HUGE_OS_PAGES` instead when possible).
|
can have fragmented memory (for that reason, we generally recommend to use `MIMALLOC_RESERVE_HUGE_OS_PAGES` instead when possible).
|
||||||
- `MIMALLOC_EAGER_REGION_COMMIT=1`: on Windows, commit large (256MiB) regions eagerly. On Windows, these regions
|
- `MIMALLOC_RESERVE_HUGE_OS_PAGES=N`: where N is the number of 1GiB _huge_ OS pages. This reserves the huge pages at
|
||||||
show in the working set even though usually just a small part is committed to physical memory. This is why it
|
startup and sometimes this can give a large (latency) performance improvement on big workloads.
|
||||||
turned off by default on Windows as it looks not good in the task manager. However, in reality it is always better
|
Usually it is better to not use
|
||||||
to turn it on as it improves performance and has no other drawbacks.
|
|
||||||
- `MIMALLOC_RESERVE_HUGE_OS_PAGES=N`: where N is the number of 1GiB huge OS pages. This reserves the huge pages at
|
|
||||||
startup and can give quite a performance improvement on long running workloads. Usually it is better to not use
|
|
||||||
`MIMALLOC_LARGE_OS_PAGES` in combination with this setting. Just like large OS pages, use with care as reserving
|
`MIMALLOC_LARGE_OS_PAGES` in combination with this setting. Just like large OS pages, use with care as reserving
|
||||||
contiguous physical memory can take a long time when memory is fragmented.
|
contiguous physical memory can take a long time when memory is fragmented (but reserving the huge pages is done at
|
||||||
|
startup only once).
|
||||||
Note that we usually need to explicitly enable huge OS pages (as on [Windows][windows-huge] and [Linux][linux-huge])). With huge OS pages, it may be beneficial to set the setting
|
Note that we usually need to explicitly enable huge OS pages (as on [Windows][windows-huge] and [Linux][linux-huge])). With huge OS pages, it may be beneficial to set the setting
|
||||||
`MIMALLOC_EAGER_COMMIT_DELAY=N` (with usually `N` as 1) to delay the initial `N` segments
|
`MIMALLOC_EAGER_COMMIT_DELAY=N` (`N` is 1 by default) to delay the initial `N` segments (of 4MiB)
|
||||||
of a thread to not allocate in the huge OS pages; this prevents threads that are short lived
|
of a thread to not allocate in the huge OS pages; this prevents threads that are short lived
|
||||||
and allocate just a little to take up space in the huge OS page area (which cannot be reset).
|
and allocate just a little to take up space in the huge OS page area (which cannot be reset).
|
||||||
|
|
||||||
|
Use caution when using `fork` in combination with either large or huge OS pages: on a fork, the OS uses copy-on-write
|
||||||
|
for all pages in the original process including the huge OS pages. When any memory is now written in that area, the
|
||||||
|
OS will copy the entire 1GiB huge page (or 2MiB large page) which can cause the memory usage to grow in big increments.
|
||||||
|
|
||||||
[linux-huge]: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/tuning_and_optimizing_red_hat_enterprise_linux_for_oracle_9i_and_10g_databases/sect-oracle_9i_and_10g_tuning_guide-large_memory_optimization_big_pages_and_huge_pages-configuring_huge_pages_in_red_hat_enterprise_linux_4_or_5
|
[linux-huge]: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/tuning_and_optimizing_red_hat_enterprise_linux_for_oracle_9i_and_10g_databases/sect-oracle_9i_and_10g_tuning_guide-large_memory_optimization_big_pages_and_huge_pages-configuring_huge_pages_in_red_hat_enterprise_linux_4_or_5
|
||||||
[windows-huge]: https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows?view=sql-server-2017
|
[windows-huge]: https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows?view=sql-server-2017
|
||||||
|
|
||||||
@ -1074,14 +1077,18 @@ resolved to the _mimalloc_ library.
|
|||||||
Note that certain security restrictions may apply when doing this from
|
Note that certain security restrictions may apply when doing this from
|
||||||
the [shell](https://stackoverflow.com/questions/43941322/dyld-insert-libraries-ignored-when-calling-application-through-bash).
|
the [shell](https://stackoverflow.com/questions/43941322/dyld-insert-libraries-ignored-when-calling-application-through-bash).
|
||||||
|
|
||||||
Note: unfortunately, at this time, dynamic overriding on macOS seems broken but it is actively worked on to fix this
|
(Note: macOS support for dynamic overriding is recent, please report any issues.)
|
||||||
(see issue [`#50`](https://github.com/microsoft/mimalloc/issues/50)).
|
|
||||||
|
|
||||||
### Windows
|
### Windows
|
||||||
|
|
||||||
Overriding on Windows is robust but requires that you link your program explicitly with
|
Overriding on Windows is robust and has the
|
||||||
|
particular advantage to be able to redirect all malloc/free calls that go through
|
||||||
|
the (dynamic) C runtime allocator, including those from other DLL's or libraries.
|
||||||
|
|
||||||
|
The overriding on Windows requires that you link your program explicitly with
|
||||||
the mimalloc DLL and use the C-runtime library as a DLL (using the `/MD` or `/MDd` switch).
|
the mimalloc DLL and use the C-runtime library as a DLL (using the `/MD` or `/MDd` switch).
|
||||||
Moreover, you need to ensure the `mimalloc-redirect.dll` (or `mimalloc-redirect32.dll`) is available
|
Also, the `mimalloc-redirect.dll` (or `mimalloc-redirect32.dll`) must be available
|
||||||
in the same folder as the main `mimalloc-override.dll` at runtime (as it is a dependency).
|
in the same folder as the main `mimalloc-override.dll` at runtime (as it is a dependency).
|
||||||
The redirection DLL ensures that all calls to the C runtime malloc API get redirected to
|
The redirection DLL ensures that all calls to the C runtime malloc API get redirected to
|
||||||
mimalloc (in `mimalloc-override.dll`).
|
mimalloc (in `mimalloc-override.dll`).
|
||||||
@ -1090,14 +1097,15 @@ To ensure the mimalloc DLL is loaded at run-time it is easiest to insert some
|
|||||||
call to the mimalloc API in the `main` function, like `mi_version()`
|
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
|
(or use the `/INCLUDE:mi_version` switch on the linker). See the `mimalloc-override-test` project
|
||||||
for an example on how to use this. For best performance on Windows with C++, it
|
for an example on how to use this. For best performance on Windows with C++, it
|
||||||
is highly recommended to also override the `new`/`delete` operations (by including
|
is also recommended to also override the `new`/`delete` operations (by including
|
||||||
[`mimalloc-new-delete.h`](https://github.com/microsoft/mimalloc/blob/master/include/mimalloc-new-delete.h) a single(!) source file in your project).
|
[`mimalloc-new-delete.h`](https://github.com/microsoft/mimalloc/blob/master/include/mimalloc-new-delete.h) a single(!) source file in your project).
|
||||||
|
|
||||||
The environment variable `MIMALLOC_DISABLE_REDIRECT=1` can be used to disable dynamic
|
The environment variable `MIMALLOC_DISABLE_REDIRECT=1` can be used to disable dynamic
|
||||||
overriding at run-time. Use `MIMALLOC_VERBOSE=1` to check if mimalloc was successfully redirected.
|
overriding at run-time. Use `MIMALLOC_VERBOSE=1` to check if mimalloc was successfully redirected.
|
||||||
|
|
||||||
(Note: in principle, it is possible to patch existing executables
|
(Note: in principle, it is possible to even patch existing executables without any recompilation
|
||||||
that are linked with the dynamic C runtime (`ucrtbase.dll`) by just putting the `mimalloc-override.dll` into the import table (and putting `mimalloc-redirect.dll` in the same folder)
|
if they are linked with the dynamic C runtime (`ucrtbase.dll`) -- just put the `mimalloc-override.dll`
|
||||||
|
into the import table (and put `mimalloc-redirect.dll` in the same folder)
|
||||||
Such patching can be done for example with [CFF Explorer](https://ntcore.com/?page_id=388)).
|
Such patching can be done for example with [CFF Explorer](https://ntcore.com/?page_id=388)).
|
||||||
|
|
||||||
|
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
@ -107,11 +107,11 @@ $(document).ready(function(){initNavTree('environment.html','');});
|
|||||||
<li><code>MIMALLOC_SHOW_STATS=1</code>: show statistics when the program terminates.</li>
|
<li><code>MIMALLOC_SHOW_STATS=1</code>: show statistics when the program terminates.</li>
|
||||||
<li><code>MIMALLOC_VERBOSE=1</code>: show verbose messages.</li>
|
<li><code>MIMALLOC_VERBOSE=1</code>: show verbose messages.</li>
|
||||||
<li><code>MIMALLOC_SHOW_ERRORS=1</code>: show error and warning messages.</li>
|
<li><code>MIMALLOC_SHOW_ERRORS=1</code>: show error and warning messages.</li>
|
||||||
<li><code>MIMALLOC_PAGE_RESET=1</code>: reset (or purge) OS pages when not in use. This can reduce memory fragmentation in long running (server) programs. If performance is impacted, <code>MIMALLOC_RESET_DELAY=</code>_msecs_ can be set higher (100ms by default) to make the page reset occur less frequently.</li>
|
<li><code>MIMALLOC_PAGE_RESET=0</code>: by default, mimalloc will reset (or purge) OS pages when not in use to signal to the OS that the underlying physical memory can be reused. This can reduce memory fragmentation in long running (server) programs. By setting it to <code>0</code> no such page resets will be done which can improve performance for programs that are not long running. As an alternative, the <code>MIMALLOC_RESET_DELAY=</code><msecs> can be set higher (100ms by default) to make the page reset occur less frequently instead of turning it off completely.</li>
|
||||||
<li><code>MIMALLOC_LARGE_OS_PAGES=1</code>: use large OS pages when available; for some workloads this can significantly improve performance. Use <code>MIMALLOC_VERBOSE</code> to check if the large OS pages are enabled – usually one needs to explicitly allow large OS pages (as on <a href="https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows?view=sql-server-2017">Windows</a> and <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/tuning_and_optimizing_red_hat_enterprise_linux_for_oracle_9i_and_10g_databases/sect-oracle_9i_and_10g_tuning_guide-large_memory_optimization_big_pages_and_huge_pages-configuring_huge_pages_in_red_hat_enterprise_linux_4_or_5">Linux</a>). However, sometimes the OS is very slow to reserve contiguous physical memory for large OS pages so use with care on systems that can have fragmented memory (for that reason, we generally recommend to use <code>MIMALLOC_RESERVE_HUGE_OS_PAGES</code> instead when possible).</li>
|
<li><code>MIMALLOC_LARGE_OS_PAGES=1</code>: use large OS pages (2MiB) when available; for some workloads this can significantly improve performance. Use <code>MIMALLOC_VERBOSE</code> to check if the large OS pages are enabled – usually one needs to explicitly allow large OS pages (as on <a href="https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows?view=sql-server-2017">Windows</a> and <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/tuning_and_optimizing_red_hat_enterprise_linux_for_oracle_9i_and_10g_databases/sect-oracle_9i_and_10g_tuning_guide-large_memory_optimization_big_pages_and_huge_pages-configuring_huge_pages_in_red_hat_enterprise_linux_4_or_5">Linux</a>). However, sometimes the OS is very slow to reserve contiguous physical memory for large OS pages so use with care on systems that can have fragmented memory (for that reason, we generally recommend to use <code>MIMALLOC_RESERVE_HUGE_OS_PAGES</code> instead when possible).</li>
|
||||||
<li><code>MIMALLOC_EAGER_REGION_COMMIT=1</code>: on Windows, commit large (256MiB) regions eagerly. On Windows, these regions show in the working set even though usually just a small part is committed to physical memory. This is why it turned off by default on Windows as it looks not good in the task manager. However, in reality it is always better to turn it on as it improves performance and has no other drawbacks.</li>
|
<li><code>MIMALLOC_RESERVE_HUGE_OS_PAGES=N</code>: where N is the number of 1GiB <em>huge</em> OS pages. This reserves the huge pages at startup and sometimes this can give a large (latency) performance improvement on big workloads. Usually it is better to not use <code>MIMALLOC_LARGE_OS_PAGES</code> in combination with this setting. Just like large OS pages, use with care as reserving contiguous physical memory can take a long time when memory is fragmented (but reserving the huge pages is done at startup only once). Note that we usually need to explicitly enable huge OS pages (as on <a href="https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows?view=sql-server-2017">Windows</a> and <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/tuning_and_optimizing_red_hat_enterprise_linux_for_oracle_9i_and_10g_databases/sect-oracle_9i_and_10g_tuning_guide-large_memory_optimization_big_pages_and_huge_pages-configuring_huge_pages_in_red_hat_enterprise_linux_4_or_5">Linux</a>)). With huge OS pages, it may be beneficial to set the setting <code>MIMALLOC_EAGER_COMMIT_DELAY=N</code> (<code>N</code> is 1 by default) to delay the initial <code>N</code> segments (of 4MiB) of a thread to not allocate in the huge OS pages; this prevents threads that are short lived and allocate just a little to take up space in the huge OS page area (which cannot be reset).</li>
|
||||||
<li><code>MIMALLOC_RESERVE_HUGE_OS_PAGES=N</code>: where N is the number of 1GiB huge OS pages. This reserves the huge pages at startup and can give quite a performance improvement on long running workloads. Usually it is better to not use <code>MIMALLOC_LARGE_OS_PAGES</code> in combination with this setting. Just like large OS pages, use with care as reserving contiguous physical memory can take a long time when memory is fragmented. Note that we usually need to explicitly enable huge OS pages (as on <a href="https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows?view=sql-server-2017">Windows</a> and <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/tuning_and_optimizing_red_hat_enterprise_linux_for_oracle_9i_and_10g_databases/sect-oracle_9i_and_10g_tuning_guide-large_memory_optimization_big_pages_and_huge_pages-configuring_huge_pages_in_red_hat_enterprise_linux_4_or_5">Linux</a>)). With huge OS pages, it may be beneficial to set the setting <code>MIMALLOC_EAGER_COMMIT_DELAY=N</code> (with usually <code>N</code> as 1) to delay the initial <code>N</code> segments of a thread to not allocate in the huge OS pages; this prevents threads that are short lived and allocate just a little to take up space in the huge OS page area (which cannot be reset). </li>
|
|
||||||
</ul>
|
</ul>
|
||||||
|
<p>Use caution when using <code>fork</code> in combination with either large or huge OS pages: on a fork, the OS uses copy-on-write for all pages in the original process including the huge OS pages. When any memory is now written in that area, the OS will copy the entire 1GiB huge page (or 2MiB large page) which can cause the memory usage to grow in big increments. </p>
|
||||||
</div></div><!-- PageDoc -->
|
</div></div><!-- PageDoc -->
|
||||||
</div><!-- contents -->
|
</div><!-- contents -->
|
||||||
</div><!-- doc-content -->
|
</div><!-- doc-content -->
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
@ -146,7 +146,7 @@ Macros</h2></td></tr>
|
|||||||
</table>
|
</table>
|
||||||
<a name="details" id="details"></a><h2 class="groupheader">Detailed Description</h2>
|
<a name="details" id="details"></a><h2 class="groupheader">Detailed Description</h2>
|
||||||
<p>Typed allocation macros. </p>
|
<p>Typed allocation macros. </p>
|
||||||
<h2 class="groupheader">Macro Definition Documentation</h2>
|
<p>For example: </p><div class="fragment"><div class="line"><span class="keywordtype">int</span>* p = <a class="code" href="group__typed.html#ga0619a62c5fd886f1016030abe91f0557">mi_malloc_tp</a>(<span class="keywordtype">int</span>)</div></div><!-- fragment --> <h2 class="groupheader">Macro Definition Documentation</h2>
|
||||||
<a id="gae80c47c9d4cab10961fff1a8ac98fc07"></a>
|
<a id="gae80c47c9d4cab10961fff1a8ac98fc07"></a>
|
||||||
<h2 class="memtitle"><span class="permalink"><a href="#gae80c47c9d4cab10961fff1a8ac98fc07">◆ </a></span>mi_calloc_tp</h2>
|
<h2 class="memtitle"><span class="permalink"><a href="#gae80c47c9d4cab10961fff1a8ac98fc07">◆ </a></span>mi_calloc_tp</h2>
|
||||||
|
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
@ -127,7 +127,9 @@ $(document).ready(function(){initNavTree('index.html','');});
|
|||||||
<li><a class="el" href="group__heap.html">Heap Allocation</a></li>
|
<li><a class="el" href="group__heap.html">Heap Allocation</a></li>
|
||||||
<li><a class="el" href="group__typed.html">Typed Macros</a></li>
|
<li><a class="el" href="group__typed.html">Typed Macros</a></li>
|
||||||
<li><a class="el" href="group__analysis.html">Heap Introspection</a></li>
|
<li><a class="el" href="group__analysis.html">Heap Introspection</a></li>
|
||||||
<li><a class="el" href="group__options.html">Runtime Options</a> </li>
|
<li><a class="el" href="group__options.html">Runtime Options</a></li>
|
||||||
|
<li><a class="el" href="group__posix.html">Posix</a></li>
|
||||||
|
<li><a class="el" href="group__cpp.html">C++ wrappers</a> </li>
|
||||||
</ul>
|
</ul>
|
||||||
</div></div><!-- PageDoc -->
|
</div></div><!-- PageDoc -->
|
||||||
</div><!-- contents -->
|
</div><!-- contents -->
|
||||||
|
File diff suppressed because one or more lines are too long
@ -36,15 +36,15 @@
|
|||||||
inkscape:pageopacity="0.0"
|
inkscape:pageopacity="0.0"
|
||||||
inkscape:pageshadow="2"
|
inkscape:pageshadow="2"
|
||||||
inkscape:zoom="23.706667"
|
inkscape:zoom="23.706667"
|
||||||
inkscape:cx="34.419045"
|
inkscape:cx="24.864771"
|
||||||
inkscape:cy="35.79485"
|
inkscape:cy="35.79485"
|
||||||
inkscape:document-units="mm"
|
inkscape:document-units="mm"
|
||||||
inkscape:current-layer="layer1"
|
inkscape:current-layer="layer1"
|
||||||
showgrid="false"
|
showgrid="false"
|
||||||
inkscape:window-width="3840"
|
inkscape:window-width="3840"
|
||||||
inkscape:window-height="2160"
|
inkscape:window-height="2050"
|
||||||
inkscape:window-x="0"
|
inkscape:window-x="-12"
|
||||||
inkscape:window-y="0"
|
inkscape:window-y="-12"
|
||||||
inkscape:window-maximized="1"
|
inkscape:window-maximized="1"
|
||||||
inkscape:snap-object-midpoints="false"
|
inkscape:snap-object-midpoints="false"
|
||||||
inkscape:snap-bbox="false"
|
inkscape:snap-bbox="false"
|
||||||
@ -126,17 +126,15 @@
|
|||||||
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:2.28797817px;font-family:RoutedGothicEx;-inkscape-font-specification:'RoutedGothicEx, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-feature-settings:normal;text-align:start;writing-mode:lr-tb;text-anchor:start;stroke-width:0.28599727"
|
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:2.28797817px;font-family:RoutedGothicEx;-inkscape-font-specification:'RoutedGothicEx, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-feature-settings:normal;text-align:start;writing-mode:lr-tb;text-anchor:start;stroke-width:0.28599727"
|
||||||
id="path6525" />
|
id="path6525" />
|
||||||
</g>
|
</g>
|
||||||
<text
|
<g
|
||||||
xml:space="preserve"
|
aria-label="m"
|
||||||
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:6.3694315px;line-height:1.25;font-family:RoutedGothicEx;-inkscape-font-specification:'RoutedGothicEx, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-feature-settings:normal;text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.15923578"
|
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:6.3694315px;line-height:1.25;font-family:RoutedGothicEx;-inkscape-font-specification:'RoutedGothicEx, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-feature-settings:normal;text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.15923578"
|
||||||
x="1.6752419"
|
id="text848">
|
||||||
y="293.17081"
|
<path
|
||||||
id="text848"><tspan
|
d="m 2.3718985,293.17081 c 0.080862,0 0.1492836,-0.0249 0.211485,-0.0871 0.055981,-0.056 0.087082,-0.1244 0.087082,-0.21148 v -1.95313 c 0.037321,-0.0622 0.087082,-0.13062 0.1430634,-0.19282 0.049761,-0.0622 0.1368433,-0.1244 0.2488059,-0.19283 0.1119627,-0.0622 0.2301455,-0.0995 0.3545485,-0.0995 0.1119626,0 0.2177051,0.0498 0.3110074,0.14929 0.087082,0.0995 0.1368432,0.23014 0.1368432,0.39808 v 1.89093 c 0,0.0871 0.024881,0.1555 0.087082,0.21148 0.055981,0.0622 0.124403,0.0871 0.211485,0.0871 0.080862,0 0.1492836,-0.0249 0.2114851,-0.0871 0.055981,-0.056 0.087082,-0.1244 0.087082,-0.21148 v -1.89093 -0.0622 c 0.018661,-0.0311 0.043541,-0.0622 0.068422,-0.0995 0.024881,-0.0373 0.062201,-0.0746 0.1119626,-0.1244 0.049761,-0.0498 0.099522,-0.0933 0.1492836,-0.13063 0.049761,-0.0373 0.1181828,-0.0684 0.1928246,-0.0933 0.074642,-0.0249 0.1492835,-0.0373 0.2239253,-0.0373 0.1119626,0 0.2177052,0.0498 0.3110074,0.14929 0.087082,0.0995 0.1368432,0.23014 0.1368432,0.39808 v 1.89093 c 0,0.0871 0.024881,0.1555 0.087082,0.21148 0.055981,0.0622 0.124403,0.0871 0.211485,0.0871 0.080862,0 0.1492836,-0.0249 0.2114851,-0.0871 0.055981,-0.056 0.087082,-0.1244 0.087082,-0.21148 v -1.89093 c 0,-0.31722 -0.1057425,-0.58469 -0.3047872,-0.80861 -0.2052649,-0.22393 -0.4540708,-0.33589 -0.7401976,-0.33589 -0.2052649,0 -0.3918693,0.0435 -0.5535932,0.11818 -0.1617238,0.0746 -0.3047872,0.17416 -0.4291902,0.29857 -0.211485,-0.27369 -0.4789514,-0.41675 -0.8086192,-0.41675 -0.2861268,0 -0.5411529,0.0809 -0.7650782,0.23636 -0.024881,-0.0498 -0.062202,-0.0933 -0.1119627,-0.13062 -0.049761,-0.0373 -0.1057425,-0.056 -0.167944,-0.056 -0.087082,0 -0.1555037,0.0311 -0.211485,0.0871 -0.062202,0.0622 -0.087082,0.13062 -0.087082,0.21149 v 2.6871 c 0,0.0871 0.024881,0.1555 0.087082,0.21148 0.055981,0.0622 0.1244029,0.0871 0.211485,0.0871 z"
|
||||||
y="293.17081"
|
style="stroke-width:0.15923578"
|
||||||
x="1.6752419"
|
id="path834" />
|
||||||
sodipodi:role="line"
|
</g>
|
||||||
id="tspan872"
|
|
||||||
style="stroke-width:0.15923578">m</tspan></text>
|
|
||||||
<g
|
<g
|
||||||
id="g28"
|
id="g28"
|
||||||
transform="translate(-0.23995531,0.02790178)">
|
transform="translate(-0.23995531,0.02790178)">
|
||||||
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 18 KiB |
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
@ -116,12 +116,13 @@ $(document).ready(function(){initNavTree('overrides.html','');});
|
|||||||
<li><code>env DYLD_FORCE_FLAT_NAMESPACE=1 DYLD_INSERT_LIBRARIES=/usr/lib/libmimalloc.dylib myprogram</code></li>
|
<li><code>env DYLD_FORCE_FLAT_NAMESPACE=1 DYLD_INSERT_LIBRARIES=/usr/lib/libmimalloc.dylib myprogram</code></li>
|
||||||
</ul>
|
</ul>
|
||||||
<p>Note that certain security restrictions may apply when doing this from the <a href="https://stackoverflow.com/questions/43941322/dyld-insert-libraries-ignored-when-calling-application-through-bash">shell</a>.</p>
|
<p>Note that certain security restrictions may apply when doing this from the <a href="https://stackoverflow.com/questions/43941322/dyld-insert-libraries-ignored-when-calling-application-through-bash">shell</a>.</p>
|
||||||
<p>Note: unfortunately, at this time, dynamic overriding on macOS seems broken but it is actively worked on to fix this (see issue <a href="https://github.com/microsoft/mimalloc/issues/50"><code>#50</code></a>).</p>
|
<p>(Note: macOS support for dynamic overriding is recent, please report any issues.)</p>
|
||||||
<h3>Windows</h3>
|
<h3>Windows</h3>
|
||||||
<p>Overriding on Windows is robust but requires that you link your program explicitly with the mimalloc DLL and use the C-runtime library as a DLL (using the <code>/MD</code> or <code>/MDd</code> switch). Moreover, you need to ensure the <code>mimalloc-redirect.dll</code> (or <code>mimalloc-redirect32.dll</code>) is available in the same folder as the main <code>mimalloc-override.dll</code> at runtime (as it is a dependency). The redirection DLL ensures that all calls to the C runtime malloc API get redirected to mimalloc (in <code>mimalloc-override.dll</code>).</p>
|
<p>Overriding on Windows is robust and has the particular advantage to be able to redirect all malloc/free calls that go through the (dynamic) C runtime allocator, including those from other DLL's or libraries.</p>
|
||||||
<p>To ensure the mimalloc DLL is loaded at run-time it is easiest to insert some call to the mimalloc API in the <code>main</code> function, like <code>mi_version()</code> (or use the <code>/INCLUDE:mi_version</code> switch on the linker). See the <code>mimalloc-override-test</code> project for an example on how to use this. For best performance on Windows with C++, it is highly recommended to also override the <code>new</code>/<code>delete</code> operations (by including <a href="https://github.com/microsoft/mimalloc/blob/master/include/mimalloc-new-delete.h"><code>mimalloc-new-delete.h</code></a> a single(!) source file in your project).</p>
|
<p>The overriding on Windows requires that you link your program explicitly with the mimalloc DLL and use the C-runtime library as a DLL (using the <code>/MD</code> or <code>/MDd</code> switch). Also, the <code>mimalloc-redirect.dll</code> (or <code>mimalloc-redirect32.dll</code>) must be available in the same folder as the main <code>mimalloc-override.dll</code> at runtime (as it is a dependency). The redirection DLL ensures that all calls to the C runtime malloc API get redirected to mimalloc (in <code>mimalloc-override.dll</code>).</p>
|
||||||
|
<p>To ensure the mimalloc DLL is loaded at run-time it is easiest to insert some call to the mimalloc API in the <code>main</code> function, like <code>mi_version()</code> (or use the <code>/INCLUDE:mi_version</code> switch on the linker). See the <code>mimalloc-override-test</code> project for an example on how to use this. For best performance on Windows with C++, it is also recommended to also override the <code>new</code>/<code>delete</code> operations (by including <a href="https://github.com/microsoft/mimalloc/blob/master/include/mimalloc-new-delete.h"><code>mimalloc-new-delete.h</code></a> a single(!) source file in your project).</p>
|
||||||
<p>The environment variable <code>MIMALLOC_DISABLE_REDIRECT=1</code> can be used to disable dynamic overriding at run-time. Use <code>MIMALLOC_VERBOSE=1</code> to check if mimalloc was successfully redirected.</p>
|
<p>The environment variable <code>MIMALLOC_DISABLE_REDIRECT=1</code> can be used to disable dynamic overriding at run-time. Use <code>MIMALLOC_VERBOSE=1</code> to check if mimalloc was successfully redirected.</p>
|
||||||
<p>(Note: in principle, it is possible to patch existing executables that are linked with the dynamic C runtime (<code>ucrtbase.dll</code>) by just putting the <code>mimalloc-override.dll</code> into the import table (and putting <code>mimalloc-redirect.dll</code> in the same folder) Such patching can be done for example with <a href="https://ntcore.com/?page_id=388">CFF Explorer</a>).</p>
|
<p>(Note: in principle, it is possible to even patch existing executables without any recompilation if they are linked with the dynamic C runtime (<code>ucrtbase.dll</code>) – just put the <code>mimalloc-override.dll</code> into the import table (and put <code>mimalloc-redirect.dll</code> in the same folder) Such patching can be done for example with <a href="https://ntcore.com/?page_id=388">CFF Explorer</a>).</p>
|
||||||
<h2>Static override</h2>
|
<h2>Static override</h2>
|
||||||
<p>On Unix systems, you can also statically link with <em>mimalloc</em> to override the standard malloc interface. The recommended way is to link the final program with the <em>mimalloc</em> single object file (<code>mimalloc-override.o</code>). We use an object file instead of a library file as linkers give preference to that over archives to resolve symbols. To ensure that the standard malloc interface resolves to the <em>mimalloc</em> library, link it as the first object file. For example:</p>
|
<p>On Unix systems, you can also statically link with <em>mimalloc</em> to override the standard malloc interface. The recommended way is to link the final program with the <em>mimalloc</em> single object file (<code>mimalloc-override.o</code>). We use an object file instead of a library file as linkers give preference to that over archives to resolve symbols. To ensure that the standard malloc interface resolves to the <em>mimalloc</em> library, link it as the first object file. For example:</p>
|
||||||
<div class="fragment"><div class="line">gcc -o myprogram mimalloc-<span class="keyword">override</span>.o myfile1.c ...</div></div><!-- fragment --><h2>List of Overrides:</h2>
|
<div class="fragment"><div class="line">gcc -o myprogram mimalloc-<span class="keyword">override</span>.o myfile1.c ...</div></div><!-- fragment --><h2>List of Overrides:</h2>
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
@ -37,7 +37,7 @@
|
|||||||
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
<td id="projectlogo"><img alt="Logo" src="mimalloc-logo.svg"/></td>
|
||||||
<td id="projectalign" style="padding-left: 0.5em;">
|
<td id="projectalign" style="padding-left: 0.5em;">
|
||||||
<div id="projectname">mi-malloc
|
<div id="projectname">mi-malloc
|
||||||
 <span id="projectnumber">1.4</span>
|
 <span id="projectnumber">1.6</span>
|
||||||
</div>
|
</div>
|
||||||
</td>
|
</td>
|
||||||
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
<td> <div id="MSearchBox" class="MSearchBoxInactive">
|
||||||
|
Loading…
Reference in New Issue
Block a user