Don't try to use the malloc_usable_size portability implementation if we have JEMalloc
authorChristopher Dykes <cdykes@fb.com>
Mon, 2 May 2016 19:22:28 +0000 (12:22 -0700)
committerFacebook Github Bot 3 <facebook-github-bot-3-bot@fb.com>
Mon, 2 May 2016 19:35:19 +0000 (12:35 -0700)
commit8d4965cabcb41ab0ca804298807168d70e5da92b
treec628e233a3e6bb08aeeaafa872542b9d1fc505c5
parenta0a4a68dc876804f283131b5394610c556b67547
Don't try to use the malloc_usable_size portability implementation if we have JEMalloc

Summary:
This is only an issue for the OSS HHVM build on OSX, where we have JEMalloc headers included directly.
In the OSS HHVM build, we define `USE_JEMALLOC` globally if we have JEMalloc, so gate the portability implementation behind that.

Reviewed By: mzlee

Differential Revision: D3237449

fb-gh-sync-id: 07cf9b31114723ffd9f2b29cf449bee0ed8f5703
fbshipit-source-id: 07cf9b31114723ffd9f2b29cf449bee0ed8f5703
folly/portability/Malloc.cpp
folly/portability/Malloc.h