1. 06 Jun, 2018 2 commits
  2. 16 May, 2018 1 commit
  3. 14 May, 2018 1 commit
    • Pierre Langlois's avatar
      [turbofan][wasm] Fix --trace-turbo with compiling a WASM function. · 7927d646
      Pierre Langlois authored
      The --trace-turbo flag would cause a crash when compiling a WASM_FUNCTION. It
      was caused by assuming the OptimizedCompilationInfo had a SharedFunctionInfo
      attached if the code isn't a stub and wasm functions are not considered as such.
      
      In order to test this, we've added a new flag to specify were to dump JSON
      files: --trace-turbo-path. This is used to make sure we do not leave lots of
      files behind in the top-level directory. It should be useful as standalone
      feature too.
      
      
      Change-Id: Ia9442638d28100bea45a8683fb233803cc5393f2
      Reviewed-on: https://chromium-review.googlesource.com/1030555
      Commit-Queue: Jaroslav Sevcik <jarin@chromium.org>
      Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53153}
      7927d646
  4. 09 May, 2018 1 commit
  5. 07 May, 2018 1 commit
    • Clemens Hammacher's avatar
      [trap-handler] Add missing newlines · ec1bf81b
      Clemens Hammacher authored
      If trap handlers cannot be installed, we printed two lines to stdout
      and stderr, both not terminated by a newline. This CL adds a newline to
      one output and uses the FATAL macro for the other, highlighting the
      error better and showing the location where it happens.
      
      R=eholk@chromium.org
      
      Bug: v8:7570
      Change-Id: Ic24f48f92b87528e0fd5889badf2c90d765e451a
      Reviewed-on: https://chromium-review.googlesource.com/1047606Reviewed-by: 's avatarEric Holk <eholk@chromium.org>
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53043}
      ec1bf81b
  6. 04 May, 2018 1 commit
    • Eric Holk (eholk)'s avatar
      [wasm] Refactor trap handlers to make way for Windows support · bb60967e
      Eric Holk (eholk) authored
      In preparing for adding trap-based bounds checking to Windows, this
      change refactors the code to separate the platform-specific portions
      from that which can be shared between platforms.
      
      Internally, we've renamed `RegisterDefaultSignalHandler` to
      `RegisterDefaultTrapHandler` to more accurately represent the
      difference in terminology between Linux (signals) and Windows
      (exceptions). The external API is left the same so as not to break
      downstream clients.
      
      This CL is primarily to make room for Windows support. Future CLs
      will begin adding support for Windows.
      
      This is a reincarnation of https://crrev.com/c/626558.
      
      Bug: v8:6743
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng
      Change-Id: Iaa8bfd68c14cd1d17933b12c24cb8dd5ee8a21d6
      Reviewed-on: https://chromium-review.googlesource.com/998829
      Commit-Queue: Eric Holk <eholk@chromium.org>
      Reviewed-by: 's avatarBrad Nelson <bradnelson@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53006}
      bb60967e
  7. 30 Apr, 2018 2 commits
  8. 27 Apr, 2018 1 commit
  9. 16 Apr, 2018 1 commit
  10. 14 Apr, 2018 1 commit
    • Jakob Kummerow's avatar
      [ubsan] Change Address typedef to uintptr_t · 2459046c
      Jakob Kummerow authored
      The "Address" type is V8's general-purpose type for manipulating memory
      addresses. Per the C++ spec, pointer arithmetic and pointer comparisons
      are undefined behavior except within the same array; since we generally
      don't operate within a C++ array, our general-purpose type shouldn't be
      a pointer type.
      
      Bug: v8:3770
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
      Change-Id: Ib96016c24a0f18bcdba916dabd83e3f24a1b5779
      Reviewed-on: https://chromium-review.googlesource.com/988657
      Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
      Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#52601}
      2459046c
  11. 06 Apr, 2018 1 commit
  12. 30 Mar, 2018 1 commit
  13. 26 Mar, 2018 1 commit
  14. 23 Mar, 2018 1 commit
  15. 22 Mar, 2018 1 commit
  16. 20 Mar, 2018 1 commit
  17. 16 Mar, 2018 1 commit
  18. 15 Mar, 2018 2 commits
  19. 03 Mar, 2018 1 commit
  20. 01 Mar, 2018 2 commits
  21. 28 Feb, 2018 1 commit
    • Andreas Haas's avatar
      [cleanup] Deprecate EnsureEventLoopInitialized · 9bacf523
      Andreas Haas authored
      Due to a recent refactoring the function EnsureEventLoopInitialized on
      the default platform became obsolete. It does not contain a single line
      of code. With this CL we prepare the removal of this function from the
      V8 platform API.
      
      R=rmcilroy@chromium.org
      
      Bug: v8:7310
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng;master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: If4d54cd989f8df2f40b322be3b67bb8a482398d0
      Reviewed-on: https://chromium-review.googlesource.com/934221
      Commit-Queue: Andreas Haas <ahaas@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#51635}
      9bacf523
  22. 21 Feb, 2018 1 commit
  23. 16 Feb, 2018 2 commits
  24. 10 Feb, 2018 1 commit
    • Adam Klein's avatar
      [d8] Always pass filename through NormalizePath for dynamic imports · a36354c2
      Adam Klein authored
      d8's fragile path manipulation code requires that backslashes are
      replaced with slashes before further processing. NormalizePath() is
      the function that does this, and it's called in almost all the
      required cases. But because of Clusterfuzz runs tests with
      an absolute URL on the commandline, there was one case that
      slipped through. This patch closes that gap.
      
      No test added since this only reproduces under Clusterfuzz, not
      in running mjsunit tests.
      
      Bug: chromium:784012
      Change-Id: Ie699e93ff1acb79edfe25ce59d576e9f7bd8c022
      Reviewed-on: https://chromium-review.googlesource.com/912325Reviewed-by: 's avatarSathya Gunasekaran <gsathya@chromium.org>
      Commit-Queue: Adam Klein <adamk@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#51224}
      a36354c2
  25. 30 Jan, 2018 1 commit
  26. 18 Jan, 2018 1 commit
  27. 16 Jan, 2018 1 commit
  28. 09 Jan, 2018 1 commit
    • Andreas Haas's avatar
      [d8] Run the message loop in the same RealmScope as the script · 1016e625
      Andreas Haas authored
      In d8 a script is executed in a RealmScope. However, all micro task
      which are created by the script are not executed within the RealmScope
      at the moment. With this CL I move the execution of the micro task into
      the RealmScope.
      
      I thought about creating a new RealmScope for the micro tasks, but
      (1) It did not fix the crashing repro;
      (2) It seems wrong that the micro tasks are executed in a different
          realm than the script;
      
      Therefore I just moved the execution of the micro tasks into the
      RealmScope of the script.
      
      Thereby I moved the execution tasks also into the Context::Scope of the
      script. The problem is that the Context::Scope surrounds the RealmScope,
      and when I to open the RealmScope before the Context::Scope, not even
      the execution of the script works anymore.
      
      R=yangguo@chromium.org
      
      Bug: chromium:797846
      Change-Id: If152af282beec8f0b0564dcc9682fee8588e142c
      Reviewed-on: https://chromium-review.googlesource.com/856497Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Commit-Queue: Andreas Haas <ahaas@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#50442}
      1016e625
  29. 02 Jan, 2018 1 commit
  30. 21 Dec, 2017 1 commit
  31. 15 Dec, 2017 2 commits
  32. 13 Dec, 2017 1 commit
  33. 10 Dec, 2017 1 commit
  34. 08 Dec, 2017 1 commit