Skip to content

V
V8
Switch branch/tag
  1. 30 Aug, 2017 1 commit
  3. 22 May, 2017 1 commit
  5. 12 May, 2017 1 commit
  7. 24 Jan, 2017 1 commit
  9. 23 Jan, 2017 1 commit
    • ahaas's avatar
      [wasm] Change the constant kV8MaxWasmMemoryPages to a command line flag. · 94266b7d
      ahaas authored 
      The hardcoded constant caused a problem for the wasm fuzzer because
when the maximum memory was allocated in a test case, clusterfuzz ran
out of memory. with the command line flag we can set a lower limit
for the fuzzer.

The flag has the value of the constant as its default value, so that
for everything but the fuzzers nothing should change.

R=titzer@chromium.org
BUG=chromium:676888

Review-Url: https://codereview.chromium.org/2626313003
Cr-Commit-Position: refs/heads/master@{#42599}
      94266b7d
  11. 22 Jun, 2016 1 commit
  13. 03 Sep, 2015 1 commit
  15. 01 Sep, 2015 1 commit
  17. 20 Aug, 2015 1 commit
  19. 01 Jun, 2015 1 commit
  21. 28 Apr, 2015 1 commit
  23. 17 Mar, 2015 1 commit
  25. 19 Feb, 2015 1 commit
  27. 06 Feb, 2015 1 commit
  29. 01 Feb, 2015 1 commit
  31. 31 Jan, 2015 1 commit
  33. 13 Nov, 2014 1 commit
  35. 30 Sep, 2014 1 commit
  37. 08 Aug, 2014 1 commit
  39. 04 Aug, 2014 1 commit
  41. 07 Jul, 2014 1 commit
  43. 30 Jun, 2014 1 commit
  45. 23 Jun, 2014 1 commit
    • rmcilroy@chromium.org's avatar
      [Arm]: Simplify compile-time Arm feature detection. · 7f429e62
      rmcilroy@chromium.org authored 
      Simplify the compile time feature detection on Arm:
 - Define CAN_USE_XXX definitions unconditionally for all target/host
   toolchain combinations
 - Rename arm_test / ARM_TEST to arm_test_noprob / ARM_TEST_NO_FEATURE_PROBE
 - Don't set ARM_TEST_NO_FEATURE_PROBE implicitly on the simulator to make
   make simulator / native more consistent
 - Unify CpuFeatures::PrintTarget for simulator and native builds
 - Remove unecessary CAN_USE_VFP_INSTRUCTIONS definition for android (this is
   the default for arm_fpu=default)
 - Add a CpuFeatures::Probe() before calling CpuFeatures::PrintFeatures() in PrintHelp
    to ensure we have probed features before printing them.

BUG=384474
LOG=N
R=jkummerow@chromium.org

Review URL: https://codereview.chromium.org/340373002

git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21935 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      7f429e62
  47. 20 Jun, 2014 1 commit
  49. 03 Jun, 2014 1 commit
  51. 27 May, 2014 1 commit
  53. 26 May, 2014 2 commits
  55. 16 May, 2014 1 commit
    • yangguo@chromium.org's avatar
      Decouple CpuFeatures from serializer state. · fe243379
      yangguo@chromium.org authored 
      Traditionally, we cross compile a snapshot iff the serializer is enabled.
This will change in the future.

Changes:
 - CpuFeatures probing is done once per process, depending on whether we
   cross compile.
 - CpuFeatures are consolidated into the platform-independent assembler.h
   as much as possible.
 - FLAG_enable_<feature> will only be checked at probing time (already the
   case for ARM).
 - The serializer state is cached by the MacroAssembler.
 - PlatformFeatureScope is no longer necessary.
 - CPUFeature enum values no longer map to CPUID bit fields.

R=svenpanne@chromium.org

Review URL: https://codereview.chromium.org/285233010

git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21347 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      fe243379
  57. 29 Apr, 2014 1 commit
  59. 28 Apr, 2014 1 commit
  61. 17 Apr, 2014 1 commit
  63. 09 Dec, 2013 1 commit
  65. 17 Sep, 2013 1 commit
  67. 16 Sep, 2013 2 commits
  69. 21 Aug, 2013 1 commit
  71. 28 Jun, 2013 1 commit
  73. 16 Apr, 2013 2 commits