clang/win: Fix most -Wunused-function warnings in Chromium code.

components/browser_watcher/watcher_metrics_provider_win.cc

 // Copyright (c) 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "components/browser_watcher/watcher_metrics_provider_win.h"
 
 #include <limits>
 #include <vector>
 
 #include "base/metrics/sparse_histogram.h"
 #include "base/process/process.h"
 #include "base/strings/string_number_conversions.h"
 #include "base/strings/string_piece.h"
 #include "base/strings/utf_string_conversions.h"
 #include "base/win/registry.h"
 
 namespace browser_watcher {
 
 namespace {
 
-void CompileAsserts() {
-  // Process ID APIs on Windows talk in DWORDs, whereas for string formatting
-  // and parsing, this code uses int. In practice there are no process IDs with
-  // the high bit set on Windows, so there's no danger of overflow if this is
-  // done consistently.
-  static_assert(sizeof(DWORD) == sizeof(int),
-                "process ids are expected to be no larger than int");
-}
+// Process ID APIs on Windows talk in DWORDs, whereas for string formatting
+// and parsing, this code uses int. In practice there are no process IDs with
+// the high bit set on Windows, so there's no danger of overflow if this is
+// done consistently.
+static_assert(sizeof(DWORD) == sizeof(int),
+              "process ids are expected to be no larger than int");
 
 // This function does soft matching on the PID recorded in the key only.
 // Due to PID reuse, the possibility exists that the process that's now live
 // with the given PID is not the same process the data was recorded for.
 // This doesn't matter for the purpose, as eventually the data will be
 // scavenged and reported.
 bool IsDeadProcess(base::StringPiece16 key_or_value_name) {
   // Truncate the input string to the first occurrence of '-', if one exists.
   size_t num_end = key_or_value_name.find(L'-');
   if (num_end != base::StringPiece16::npos)
@@ skipping 193 matching lines @@
   // user account, there's a small race that will double-report the exit codes
   // from both/multiple instances. This ought to be vanishingly rare and will
   // only manifest as low-level "random" noise. To work around this it would be
   // necessary to implement some form of global locking, which is not worth it
   // here.
   RecordExitCodes(registry_path_);
   MaybeRecordExitFunnels(registry_path_, report_exit_funnels_);
 }
 
 }  // namespace browser_watcher