diff options
| author | Jason Evans <jasone@canonware.com> | 2017-04-21 18:00:36 (GMT) |
|---|---|---|
| committer | Jason Evans <jasone@canonware.com> | 2017-04-21 21:34:35 (GMT) |
| commit | 3823effe126ec602c438b02eb70d4c258a2f0e3f (patch) | |
| tree | 11d3627895df246d4553ab733fd3a3f2050fa900 /README | |
| parent | b2a8453a3fa653dc71f82ac9df64b012917f6b8c (diff) | |
| download | jemalloc-3823effe126ec602c438b02eb70d4c258a2f0e3f.zip jemalloc-3823effe126ec602c438b02eb70d4c258a2f0e3f.tar.gz jemalloc-3823effe126ec602c438b02eb70d4c258a2f0e3f.tar.bz2 | |
Remove --enable-ivsalloc.
Continue to use ivsalloc() when --enable-debug is specified (and add
assertions to guard against 0 size), but stop providing a documented
explicit semantics-changing band-aid to dodge undefined behavior in
sallocx() and malloc_usable_size(). ivsalloc() remains compiled in,
unlike when #211 restored --enable-ivsalloc, and if
JEMALLOC_FORCE_IVSALLOC is defined during compilation, sallocx() and
malloc_usable_size() will still use ivsalloc().
This partially resolves #580.
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions