Simplified CPU/CpuFeatures a bit.

src/x64/cpu-x64.cc

 // Copyright 2012 the V8 project authors. All rights reserved.
 // Redistribution and use in source and binary forms, with or without
 // modification, are permitted provided that the following conditions are
 // met:
 //
 //     * Redistributions of source code must retain the above copyright
 //       notice, this list of conditions and the following disclaimer.
 //     * Redistributions in binary form must reproduce the above
 //       copyright notice, this list of conditions and the following
 //       disclaimer in the documentation and/or other materials provided
@@ skipping 23 matching lines @@
 #include "v8.h"
 
 #if V8_TARGET_ARCH_X64
 
 #include "cpu.h"
 #include "macro-assembler.h"
 
 namespace v8 {
 namespace internal {
 
-void CPU::SetUp() {
-  CpuFeatures::Probe();
-}
-
-
-bool CPU::SupportsCrankshaft() {
-  return true;  // Yay!
-}
-
-
 void CPU::FlushICache(void* start, size_t size) {
   // No need to flush the instruction cache on Intel. On Intel instruction
   // cache flushing is only necessary when multiple cores running the same
   // code simultaneously. V8 (and JavaScript) is single threaded and when code
   // is patched on an intel CPU the core performing the patching will have its
   // own instruction cache updated automatically.
 
   // If flushing of the instruction cache becomes necessary Windows has the
   // API function FlushInstructionCache.
 
   // By default, valgrind only checks the stack for writes that might need to
   // invalidate already cached translated code.  This leads to random
   // instability when code patches or moves are sometimes unnoticed.  One
   // solution is to run valgrind with --smc-check=all, but this comes at a big
   // performance cost.  We can notify valgrind to invalidate its cache.
 #ifdef VALGRIND_DISCARD_TRANSLATIONS
   unsigned res = VALGRIND_DISCARD_TRANSLATIONS(start, size);
   USE(res);
 #endif
 }
 
 } }  // namespace v8::internal
 
 #endif  // V8_TARGET_ARCH_X64