1. 16 Oct, 2019 1 commit
  2. 11 Oct, 2019 1 commit
  3. 10 Oct, 2019 1 commit
  4. 09 Oct, 2019 1 commit
  5. 07 Oct, 2019 1 commit
  6. 26 Sep, 2019 1 commit
  7. 18 Sep, 2019 1 commit
  8. 28 Aug, 2019 1 commit
  9. 26 Aug, 2019 1 commit
  10. 05 Aug, 2019 1 commit
  11. 12 Jul, 2019 1 commit
  12. 26 Jun, 2019 1 commit
  13. 17 Jun, 2019 1 commit
  14. 31 May, 2019 1 commit
  15. 24 May, 2019 1 commit
  16. 23 May, 2019 2 commits
  17. 22 May, 2019 1 commit
  18. 21 May, 2019 1 commit
  19. 20 May, 2019 4 commits
  20. 17 May, 2019 3 commits
  21. 16 May, 2019 3 commits
  22. 10 May, 2019 1 commit
  23. 08 May, 2019 1 commit
  24. 29 Apr, 2019 1 commit
    • Clemens Hammacher's avatar
      [cleanup] Use Vector::begin instead of Vector::start · 4b0f9c85
      Clemens Hammacher authored
      Our {Vector} template provides both {start} and {begin} methods. They
      return exactly the same value. Since the {begin} method is needed for
      iteration, and is also what standard containers provide, this CL
      switches all uses of the {start} method to use {begin} instead.
      
      Patchset 1 was auto-generated by using this clang AST matcher:
          callExpr(
              callee(
                cxxMethodDecl(
                  hasName("start"),
                  ofClass(hasName("v8::internal::Vector")))
              ),
              argumentCountIs(0))
      
      Patchset 2 was created by running clang-format. Patchset 3 then
      removes the now unused {Vector::start} method.
      
      R=jkummerow@chromium.org
      TBR=mstarzinger@chromium.org,yangguo@chromium.org,verwaest@chromium.org
      
      Bug: v8:9183
      Change-Id: Id9f01c92870872556e2bb3f6d5667463b0e3e5c6
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1587381Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61081}
      4b0f9c85
  25. 12 Apr, 2019 1 commit
    • Benedikt Meurer's avatar
      [debug] Forcibly instantiate lazy accessor pairs when setting break points. · 3a7ce5de
      Benedikt Meurer authored
      Previously we had some kind of self-healing when calling lazy accessor
      pairs via InvokeApiFunction(), but we also have other paths for calling
      into FunctionTemplateInfos directly, which didn't do this check. Since
      we already walk the heap when installing the DebugBreakTrampoline, and
      compile all uncompiled functions, we can also just forcibly instantiate
      all the lazy accessor pairs at that time and not have to worry about the
      break-at-entry later.
      
      Bug: v8:178, v8:7596, v8:8834
      Cq-Include-Trybots: luci.chromium.try:linux-blink-rel
      Change-Id: I514392cf328fc8ed0b80ad19009f32e20ff850b8
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1565890Reviewed-by: 's avatarToon Verwaest <verwaest@chromium.org>
      Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
      Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#60813}
      3a7ce5de
  26. 11 Apr, 2019 1 commit
  27. 27 Feb, 2019 1 commit
  28. 19 Feb, 2019 1 commit
  29. 15 Feb, 2019 1 commit
  30. 14 Feb, 2019 1 commit
  31. 01 Feb, 2019 1 commit
  32. 25 Jan, 2019 1 commit
    • Mythri's avatar
      Defer inferring language mode as far as possible · 592aeefa
      Mythri authored
      Inferring the language mode involves iterating the stack to find the
      closure. This is an expensive operation and should be done only when
      required. This cl changes the implementation to infer the language
      mode only when we can't defer it any further. Currently, we infer the
      language mode when throwing an exception or when passing this
      information to PropertyCallbackArguments.
      
      This cl also changes the language mode parameter to SetProperty
      related methods to Maybe<ShouldThrow>. We only use the language mode to
      decide if we need to throw and using ShouldThrow instead of language
      mode simplifies the code by avoiding conversions from Maybe<ShouldThrow>
      to Maybe<LanguageMode> and vice-versa.
      
      Bug: v8:8580, chromium:923820, chromium:925289
      Change-Id: I72497497f62fe0d86fcecd57b06b3183b7531f7b
      Reviewed-on: https://chromium-review.googlesource.com/c/1425912
      Commit-Queue: Mythri Alle <mythria@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Reviewed-by: 's avatarToon Verwaest <verwaest@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#59094}
      592aeefa