1. 14 Nov, 2018 1 commit
  2. 12 Nov, 2018 1 commit
  3. 04 Sep, 2018 1 commit
  4. 27 Aug, 2018 1 commit
  5. 23 Jul, 2018 1 commit
  6. 04 Jul, 2018 1 commit
  7. 21 Jun, 2018 1 commit
  8. 05 Jun, 2018 1 commit
  9. 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
  10. 02 Dec, 2017 1 commit
    • Mathias Bynens's avatar
      Normalize casing of hexadecimal digits · 822be9b2
      Mathias Bynens authored
      This patch normalizes the casing of hexadecimal digits in escape
      sequences of the form `\xNN` and integer literals of the form
      `0xNNNN`.
      
      Previously, the V8 code base used an inconsistent mixture of uppercase
      and lowercase.
      
      Google’s C++ style guide uses uppercase in its examples:
      https://google.github.io/styleguide/cppguide.html#Non-ASCII_Characters
      
      Moreover, uppercase letters more clearly stand out from the lowercase
      `x` (or `u`) characters at the start, as well as lowercase letters
      elsewhere in strings.
      
      BUG=v8:7109
      TBR=marja@chromium.org,titzer@chromium.org,mtrofin@chromium.org,mstarzinger@chromium.org,rossberg@chromium.org,yangguo@chromium.org,mlippautz@chromium.org
      NOPRESUBMIT=true
      
      Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: I790e21c25d96ad5d95c8229724eb45d2aa9e22d6
      Reviewed-on: https://chromium-review.googlesource.com/804294
      Commit-Queue: Mathias Bynens <mathias@chromium.org>
      Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49810}
      822be9b2
  11. 17 Nov, 2017 1 commit
  12. 14 Nov, 2017 1 commit
  13. 18 Oct, 2017 1 commit
  14. 13 Oct, 2017 1 commit
  15. 26 Sep, 2017 1 commit
  16. 21 Sep, 2017 1 commit
  17. 11 Sep, 2017 1 commit
  18. 14 Aug, 2017 1 commit
  19. 25 Jul, 2017 1 commit
  20. 18 Jul, 2017 1 commit
  21. 29 Jun, 2017 1 commit
  22. 22 Mar, 2017 1 commit
  23. 18 Jan, 2017 1 commit
  24. 13 Jan, 2017 1 commit
  25. 17 Oct, 2016 1 commit
  26. 25 Jul, 2016 1 commit
  27. 24 Jun, 2016 1 commit
  28. 15 Jun, 2016 1 commit
  29. 20 Apr, 2016 1 commit
  30. 04 Apr, 2016 1 commit
  31. 01 Apr, 2016 1 commit
  32. 25 Mar, 2016 1 commit
    • adamk's avatar
      Remove --harmony-regexps flag · 06403470
      adamk authored
      It's been on since M49. Also moved tests from harmony -> es6,
      one of which was merged with another test of the same name.
      
      While moving stuff over to regexp.js, I also noticed that there
      were unused calls to %FunctionSetName and %SetNativeFlag (those
      calls are already handled by InstallGetter()).
      
      Review URL: https://codereview.chromium.org/1838563003
      
      Cr-Commit-Position: refs/heads/master@{#35076}
      06403470
  33. 15 Mar, 2016 1 commit
  34. 09 Mar, 2016 1 commit
    • yangguo's avatar
      [regexp] fix bogus assertion in CharacterRange constructor. · d1f68f77
      yangguo authored
      The CharacterRange constructor checks the input for validity. However,
      CharacterRange::Singleton also uses the constructor and may have
      kEndMarker as input, causing the check to fail.
      
      The solution is to move the check to CharacterRange::Range and
      consistently use it across the code base.
      
      R=jkummerow@chromium.org
      BUG=chromium:593282
      LOG=N
      
      Review URL: https://codereview.chromium.org/1776013003
      
      Cr-Commit-Position: refs/heads/master@{#34626}
      d1f68f77
  35. 27 Jan, 2016 1 commit
  36. 21 Jan, 2016 3 commits
  37. 11 Jan, 2016 2 commits