windows: Fix a few things clang complains about.

base/win/sampling_profiler.cc

Index: base/win/sampling_profiler.cc
diff --git a/base/win/sampling_profiler.cc b/base/win/sampling_profiler.cc
index 400eb63927b4a628dcc4ae9cafeddae6b25e9c71..c6b568501d8278fcdddd35b5c81aeeba60d97667 100644
--- a/base/win/sampling_profiler.cc
+++ b/base/win/sampling_profiler.cc
@@ -104,7 +104,7 @@ ProfilerFuncs::ProfilerFuncs()
   }
 }
 
-base::LazyInstance<ProfilerFuncs, base::LeakyLazyInstanceTraits<ProfilerFuncs>>
+base::LazyInstance<ProfilerFuncs, base::LeakyLazyInstanceTraits<ProfilerFuncs> >

[Evan Martin, 2012/01/23 18:19:49]

If the left one compiles already, shouldn't we be adapting Clang to support it
rather than changing the code?

[Nico, 2012/01/23 18:36:03]

In general, I think the upstream philosophy is to grudgingly accept what appears
in MS headers, and to prefer users to update their code to standard c++ instead.
(>> for templates is legal in c++11, but to get that one needs to pass
-std=c++11, which can change program semantics.) That also has the advantage
that it's easier to move code from _win files to shared files.

(It looks like '>>' -> '> >' is required only for the two files in this CL for
all of chrome, as far as I can tell.)

     funcs = LAZY_INSTANCE_INITIALIZER;
 
 }  // namespace