On 12/05/2013 10:59 AM, Oleg Endo wrote:
On Thu, 2013-12-05 at 10:45 -0500, Jason Merrill wrote:
A simple workaround would be to disable poisoning of malloc/realloc on
OS X (or when the build machine uses libc++, if that's easy to detect).
Whether libc++ uses malloc/realloc/free in some implementation in a
header file or not is an implementation detail. It could use it today
and stop doing so tomorrow ;)
Yep, which is why I described my suggestion as a workaround. :)
But having the poisoning disabled when building with clang doesn't seem
like a significant problem even if it becomes unnecessary, since any
misuse will still show up when building stage 2 and on other platforms.
Maybe a configure option to disable the poisoning would be better in
this case?
That seems unlikely to help users.
Jason
