[PATCH] Change internal allocator in sanitizer tools

[Alexey Samsonov]

  > Probably the mapping needs to be per-tool/platform.
  Well, the problem here is that mapping should be a compile-time constant. I would try to stick with common-for-all-tools per-platform mapping for as long as possible.

  > Actually I was perfectly fine with malloc/free for Go tsan.
  Ok, did it this way.

  > I am also concerned about memory consumption/performance for apps that use the internal allocator a lot (e.g. lots of synchronization). You use single global mutex...
  Yes. How can I measure it? Do you think that current impl. may be significantly worse than libc malloc you used previously?

http://llvm-reviews.chandlerc.com/D671