Skip to content

V
V8
Switch branch/tag
  1. 09 Mar, 2012 1 commit
  3. 23 Feb, 2012 1 commit
  5. 07 Feb, 2012 1 commit
  7. 31 Jan, 2012 1 commit
  9. 27 Jan, 2012 2 commits
  11. 24 Jan, 2012 1 commit
  13. 20 Jan, 2012 1 commit
  15. 17 Jan, 2012 2 commits
  17. 16 Jan, 2012 2 commits
  19. 13 Jan, 2012 1 commit
  21. 09 Nov, 2011 2 commits
  23. 10 Oct, 2011 1 commit
  25. 29 Sep, 2011 1 commit
  27. 19 Sep, 2011 1 commit
  29. 31 Aug, 2011 1 commit
  31. 17 Aug, 2011 1 commit
  33. 21 Jul, 2011 3 commits
  35. 20 Jul, 2011 1 commit
    • whesse@chromium.org's avatar
      fix -Wunused-but-set-variable for gcc-4.6 on x64 · 47e03a00
      whesse@chromium.org authored 
      * src/third_party/valgrind/valgrind.h: Update from upstream valgrind
  r11899, so as to get around some unused value warnings.  Also adds
  support for darwin.

  This version of valgrind.h differs from the original in that all
  instances of "unsigned long long int" have been replaced with
  "uint64_t", as the former is not allowed in ISO C++ 89.

  See https://bugs.kde.org/show_bug.cgi?id=211926 for the upstream bug
  report.

* src/x64/cpu-x64.cc:
* src/builtins.cc:
* src/conversions-inl.h:
* src/debug.cc:
* src/frames.cc:
* src/full-codegen.cc:
* src/jsregexp.cc:
* src/objects.cc:
* src/parser.cc:
* src/platform-linux.cc:
* src/x64/code-stubs-x64.cc:
* src/x64/deoptimizer-x64.cc:
* src/x64/full-codegen-x64.cc:
* src/x64/lithium-codegen-x64.cc:
* src/x64/regexp-macro-assembler-x64.cc:
* src/x64/stub-cache-x64.cc: Remove a number of assigned but
  unreferenced variables.

* SConstruct (CCTEST_EXTRA_FLAGS): Punt on -Wunused-but-set-variable for
  the test suite.

BUG=1291
TEST=A build and tools/test.py passes.

Review URL: http://codereview.chromium.org/7400023

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8688 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      47e03a00
  37. 13 Jul, 2011 1 commit
  39. 11 Jul, 2011 1 commit
  41. 05 Jul, 2011 1 commit
  43. 10 Jun, 2011 3 commits
  45. 07 Jun, 2011 1 commit
  47. 02 Jun, 2011 1 commit
  49. 01 Jun, 2011 2 commits
  51. 06 May, 2011 1 commit
  53. 03 May, 2011 1 commit
    • sgjesse@chromium.org's avatar
      ARM: Changed the handling of compiletime CPU feature detection · 01707c71
      sgjesse@chromium.org authored 
      Always use CpuFeaturesImpliedByCompiler() when selecting CPU features. This checks both for CAN_USE_ARMV7_INSTRUCTIONS and CAN_USE_VFP_INSTRUCTIONS and for GCC preprocessor symbols. This will support using the CAN_USE_XXX for a simulator build used for generating a snapshot followed by a crosscompile using -march= and -mfpu= for selecting the (minimal) target device CPU features. The snapshot will use instructions based on the CAN_USE_XXX whereas the target will at least use features based on both CAN_USE_XXX and -march= and -mfpu=, but will try runtime CPU feature detection a well looking for somethis better.

Remove the compiler based CPU feature detection from the OS::CpuFeaturesImpliedByPlatform() as it did not belong there. Also was already in the CpuFeaturesImpliedByCompiler().

Add the variable 'v8_can_use_vfp_instructions' to the GYP file which can be used to turn on CAN_USE_VFP_INSTRUCTIONS when building V8. I did not add any -mfpu= cflags for this, as there are several options here (e.g. vfp and neon).

R=erik.corry@gmail.com, karlklose@chromium.org

BUG=none
TEST=none

Review URL: http://codereview.chromium.org//6904164

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7754 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      01707c71
  55. 29 Apr, 2011 2 commits
  57. 14 Apr, 2011 1 commit
  59. 12 Apr, 2011 1 commit