diff options
| author | sgk@chromium.org <sgk@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-25 22:17:26 +0000 |
|---|---|---|
| committer | sgk@chromium.org <sgk@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-25 22:17:26 +0000 |
| commit | 3b1ea24972af975f96f7bdf6040fbc5048ea8b6d (patch) | |
| tree | f3b855b44c1d61d0c2b0fb734dc8125069b862c2 /third_party/tcmalloc/vendor/README.windows | |
| parent | aa1aad14bca48ad0b871b80267241b3a791926f8 (diff) | |
| download | chromium_src-3b1ea24972af975f96f7bdf6040fbc5048ea8b6d.zip chromium_src-3b1ea24972af975f96f7bdf6040fbc5048ea8b6d.tar.gz chromium_src-3b1ea24972af975f96f7bdf6040fbc5048ea8b6d.tar.bz2 | |
Match the vendor branch to the current tcmalloc rev in DEPS.
BUG=27911
TEST=none
Review URL: http://codereview.chromium.org/443010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@33136 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party/tcmalloc/vendor/README.windows')
| -rw-r--r-- | third_party/tcmalloc/vendor/README.windows | 14 |
1 files changed, 0 insertions, 14 deletions
diff --git a/third_party/tcmalloc/vendor/README.windows b/third_party/tcmalloc/vendor/README.windows index 750aa51..2cc607f 100644 --- a/third_party/tcmalloc/vendor/README.windows +++ b/third_party/tcmalloc/vendor/README.windows @@ -51,7 +51,6 @@ Optimization (FPO) is enabled -- that is, in release mode. The other features of perftools, such as the cpu-profiler and leak-checker, have not yet been ported to Windows at all. - NOTE FOR WIN2K USERS: According to reports (http://code.google.com/p/google-perftools/issues/detail?id=127) the stack-tracing necessary for the heap-profiler does not work on @@ -60,19 +59,6 @@ is to add "/D NO_TCMALLOC_SAMPLES=" to your build, to turn off the stack-tracing. You will not be able to use the heap-profiler if you do this. - -NOTE ON _MSIZE and _RECALLOC: The tcmalloc version of _msize returns -the size of the region tcmalloc allocated for you -- which is at least -as many bytes you asked for, but may be more. (btw, these *are* bytes -you own, even if you didn't ask for all of them, so it's correct code -to access all of them if you want.) Unfortunately, the Windows CRT -_recalloc() routine assumes that _msize returns exactly as many bytes -as were requested. As a result, _recalloc() may not zero out new -bytes correctly. IT'S SAFEST NOT TO USE _RECALLOC WITH TCMALLOC. -_recalloc() is a tricky routine to use in any case (it's not safe to -use with realloc, for instance). - - I have little experience with Windows programming, so there may be better ways to set this up than I've done! If you run across any problems, please post to the google-perftools Google Group, or report |