On Thursday, December 01, 2011 4:23:11 pm David Schultz wrote:
On Thu, Dec 01, 2011, George Liaskos wrote:
Hello
One example is Google's tcmalloc [1], is this behaviour intended?
[1] http://code.google.com/p/google-
perftools/source/browse/trunk/src/maybe_threads.cc
This code uses
On Thu, Dec 01, 2011 at 04:23:11PM -0500, David Schultz wrote:
On Thu, Dec 01, 2011, George Liaskos wrote:
Hello
One example is Google's tcmalloc [1], is this behaviour intended?
[1]
http://code.google.com/p/google-perftools/source/browse/trunk/src/maybe_threads.cc
This code
Hello
One example is Google's tcmalloc [1], is this behaviour intended?
[1]
http://code.google.com/p/google-perftools/source/browse/trunk/src/maybe_threads.cc
Regards,
George
___
freebsd-current@freebsd.org mailing list
On Thu, Dec 01, 2011, George Liaskos wrote:
Hello
One example is Google's tcmalloc [1], is this behaviour intended?
[1]
http://code.google.com/p/google-perftools/source/browse/trunk/src/maybe_threads.cc
This code uses an unportable workaround for a bug that I believe
was fixed in