Clarify that only tcmalloc_minimal is supported on Windows.
diff --git a/INSTALL b/INSTALL
index b6bc08e..f9a6a11 100644
--- a/INSTALL
+++ b/INSTALL
@@ -301,12 +301,14 @@
 
 ** Windows  (MSVC, Cygwin, and MinGW):
 
-   Work on Windows is rather preliminary: we haven't found a good way
-   to get stack traces in release mode on windows (that is, when FPO
-   is enabled), so the heap profiling may not be reliable in that
-   case.  Also, heap-checking and CPU profiling do not yet work at
-   all.  But as in other ports, the basic tcmalloc library
-   functionality, overriding malloc and new and such (and even
+   Work on Windows is rather preliminary: only tcmalloc_minimal is
+   supported.
+
+   We haven't found a good way to get stack traces in release mode on
+   windows (that is, when FPO is enabled), so the heap profiling may
+   not be reliable in that case.  Also, heap-checking and CPU profiling
+   do not yet work at all.  But as in other ports, the basic tcmalloc
+   library functionality, overriding malloc and new and such (and even
    windows-specific functions like _aligned_malloc!), is working fine,
    at least with VC++ 7.1 (Visual Studio 2003) through VC++ 10.0,
    in both debug and release modes.  See README.windows for
diff --git a/README_windows.txt b/README_windows.txt
index f74ee05..7bba122 100644
--- a/README_windows.txt
+++ b/README_windows.txt
@@ -1,7 +1,8 @@
 --- COMPILING

 

-This project has begun being ported to Windows.  A working solution

-file exists in this directory:

+This project has begun being ported to Windows, only tcmalloc_minimal

+is supported at this time.  A working solution file exists in this

+directory:

     gperftools.sln

 

 You can load this solution file into VC++ 7.1 (Visual Studio 2003) or

@@ -63,11 +64,12 @@
 

 --- THE HEAP-PROFILER

 

-The heap-profiler has had a preliminary port to Windows.  It has not

-been well tested, and probably does not work at all when Frame Pointer

-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.

+The heap-profiler has had a preliminary port to Windows but does not

+build on Windows by default.  It has not been well tested, and

+probably does not work at all when Frame Pointer 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.

 

 

 --- WIN64