Have component updater send a "wow64=1" parameter, to be able

chrome/browser/component_updater/pnacl/pnacl_component_installer.cc

 // Copyright (c) 2012 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 "chrome/browser/component_updater/pnacl/pnacl_component_installer.h"
 
 #include <string.h>
 
 #include "base/base_paths.h"
 #include "base/bind.h"
@@ skipping 27 matching lines @@
 // However, that would make startup detection even slower (need to check for
 // more than one file!).
 const FilePath::CharType kPnaclCompilerFileName[] =
     FILE_PATH_LITERAL("llc");
 
 // Name of the Pnacl component specified in the manifest.
 const char kPnaclManifestName[] = "PNaCl";
 
 // Name of the Pnacl architecture in the component manifest.
 // NOTE: this is independent of the Omaha query parameter.
-// TODO(jvoung): Will the Omaha query do the right thing for windows
-// on x86-64?  If it doesn't, will we need two separate Omaha queries (ouch)?
 const char* PnaclArch() {
 #if defined(ARCH_CPU_X86_FAMILY)
 #if defined(ARCH_CPU_X86_64)
   return "x86-64";
 #elif defined(OS_WIN)
   bool x86_64 = (base::win::OSInfo::GetInstance()->wow64_status() ==
                  base::win::OSInfo::WOW64_ENABLED);
   return x86_64 ? "x86-64" : "x86-32";
 #else
   return "x86-32";
@@ skipping 236 matching lines @@
   }
 }
 
 }  // namespace
 
 void RegisterPnaclComponent(ComponentUpdateService* cus) {
   BrowserThread::PostTask(
       BrowserThread::FILE, FROM_HERE,
       base::Bind(&StartPnaclUpdateRegistration, cus));
 }