cpu-x87.cc 1.49 KB
Newer Older
danno@chromium.org's avatar
danno@chromium.org committed
1 2 3 4 5 6 7
// Copyright 2011 the V8 project authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

// CPU specific code for ia32 independent of OS goes here.

#ifdef __GNUC__
8
#include "src/third_party/valgrind/valgrind.h"
danno@chromium.org's avatar
danno@chromium.org committed
9 10 11 12
#endif

#if V8_TARGET_ARCH_X87

13
#include "src/assembler.h"
14
#include "src/macro-assembler.h"
danno@chromium.org's avatar
danno@chromium.org committed
15 16 17 18

namespace v8 {
namespace internal {

19
void CpuFeatures::FlushICache(void* start, size_t size) {
danno@chromium.org's avatar
danno@chromium.org committed
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
  // 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
}

40 41
}  // namespace internal
}  // namespace v8
danno@chromium.org's avatar
danno@chromium.org committed
42 43

#endif  // V8_TARGET_ARCH_X87