1. 05 Nov, 2018 1 commit
  2. 01 Nov, 2018 3 commits
  3. 31 Oct, 2018 5 commits
  4. 30 Oct, 2018 1 commit
  5. 23 Oct, 2018 1 commit
  6. 16 Oct, 2018 2 commits
  7. 11 Oct, 2018 1 commit
  8. 08 Oct, 2018 3 commits
  9. 06 Oct, 2018 2 commits
  10. 05 Oct, 2018 2 commits
    • Jungshik Shin's avatar
      Use ICU to validate and canonicalize lang tag · 2abb31a9
      Jungshik Shin authored
      - Get rid of an unnecessary call to uloc_canonicalize in js-locale.
      - Do not use regex, but rely on ICU for the structrural validity check
      with Chrome's ICU or ICU 63 or newer. Otherwise, continue to use regex.
      
      This became possible thanks to a couple of bug fixes in ICU ToT that
      were cherry-picked for Chromium's ICU.
      
      Not yet done is to change js-locale to use CanonicalizeLocale().
      That will make a few more tests pass.
      
      Bug: v8:8135
      Test: test262/intl402/Intl/getCanonicalLocales/*
      Test: test262/intl402/Locale/*
      Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng
      Change-Id: I45c10b298fb041e0b39a4d96309c68a7966f91c2
      Reviewed-on: https://chromium-review.googlesource.com/c/1215223
      Commit-Queue: Jungshik Shin <jshin@chromium.org>
      Reviewed-by: 's avatarSathya Gunasekaran <gsathya@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#56399}
      2abb31a9
    • Frank Tang's avatar
      [Intl] add Intl.Segmenter - part 1 · 4274d2f1
      Frank Tang authored
      Add the JSSegmenter and hook up constructor,
      supportedLocales and resolvedOptions only
      Desgin Doc- https://goo.gl/fgc2Cp
      
      TBR: bmeurer@chromium.org
      Bug: v8:6891
      Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
      Change-Id: Ief25fb31d724c55c43c0fdf3080294fa83486e4f
      Reviewed-on: https://chromium-review.googlesource.com/c/1247362
      Commit-Queue: Frank Tang <ftang@chromium.org>
      Reviewed-by: 's avatarSathya Gunasekaran <gsathya@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#56393}
      4274d2f1
  11. 04 Oct, 2018 1 commit
  12. 03 Oct, 2018 2 commits
  13. 01 Oct, 2018 1 commit
  14. 29 Sep, 2018 1 commit
  15. 26 Sep, 2018 1 commit
  16. 24 Sep, 2018 1 commit
  17. 20 Sep, 2018 1 commit
  18. 14 Sep, 2018 1 commit
    • PhistucK's avatar
      [Intl] Rename dayperiod to dayPeriod · 53de7345
      PhistucK authored
      Previously, DateTimeFormat.prototype.formatToParts returned an object
      with the property key 'dayperiod' which is incorrect as per the spec.
      This patch updates the property key to say 'dayPeriod', making this spec
      compliant.
      
      R=cira@chromium.org
      
      Bug: chromium:865351
      Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
      Change-Id: I37f50797387bc69d5e29d7c2911bc5cc0fad37ac
      Reviewed-on: https://chromium-review.googlesource.com/1145304Reviewed-by: 's avatarSathya Gunasekaran <gsathya@chromium.org>
      Commit-Queue: PhistucK <phistuck@gmail.com>
      Cr-Commit-Position: refs/heads/master@{#55922}
      53de7345
  19. 11 Sep, 2018 3 commits
  20. 06 Sep, 2018 1 commit
    • Simon Zünd's avatar
      [array] Move Array.p.unshift fall-back to Torque · cfe71156
      Simon Zünd authored
      This CL implements a generic baseline version of Array.p.unshift
      in Torque, enabling us to remove the JS fall-back.
      
      The elements-accessor fast-path is still used, but the check whether
      to use it is also moved to Torque.
      
      Support for sparse JSArrays is removed.
      
      Drive-by change: Small refactoring in builtins-array that will
      get extended to other array builtins in a follow-up CL.
      
      R=cbruni@chromium.org, jgruber@chromium.org
      
      Bug: v8:7624
      Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
      Change-Id: I7b23ce15e7b922eb333f61a408050dedec77c95a
      Reviewed-on: https://chromium-review.googlesource.com/1189902
      Commit-Queue: Simon Zünd <szuend@google.com>
      Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#55670}
      cfe71156
  21. 05 Sep, 2018 1 commit
  22. 04 Sep, 2018 1 commit
    • Mike Stanton's avatar
      [builtins] Enable Torque Array.prototype.splice · fd334b32
      Mike Stanton authored
      Before, splice was implemented with a C++ fast path and a
      comprehensive JavaScript version.
      
      This impl. is entirely in Torque with a fastpath for SMI,
      DOUBLE and OBJECT arrays, and a comprehensive slow path.
      The same level of "sparse" array support as given by the
      array.js implementation is included.
      
      This reland addresses several issues:
      
      * Removed "sparse" array support from splice.
      * Addressed ClusterFuzz issue 876443:
        The test and code that uses the fix is in this CL.
        The fix in isolation can be seen here:
        https://chromium-review.googlesource.com/c/v8/v8/+/1199403
      * Removed dead code in elements.cc
      
      BUG=chromium:876443, v8:8131, v8:1956, v8:7221
      
      Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
      Change-Id: I2d4a66c24ba1edabeca34e27e6ff8ee6136ed5f1
      Reviewed-on: https://chromium-review.googlesource.com/1201783
      Commit-Queue: Michael Stanton <mvstanton@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#55610}
      fd334b32
  23. 29 Aug, 2018 2 commits
  24. 28 Aug, 2018 1 commit
  25. 27 Aug, 2018 1 commit
    • Sathya Gunasekaran's avatar
      [Intl] Correctly pass usage option to Collator · 59c03fef
      Sathya Gunasekaran authored
      The spec specifies that search and standard can not be valid values
      for the collation extension keyword. Instead users are expected to use
      the options bag to set the correct usage options.
      
      But, ICU expects the usage option to be set through the collation
      extension value.
      
      In this patch, we set the usage option using the collation extension
      value in ICU. For resolvedOptions, we filter out this extension value
      using ICU to be spec compatible.
      
      Previously, we stored the usage option on the JSCollator instance. But
      this patch changes the logic to just look it up from the icu::Collator
      when required. This saves one word of memory.
      
      This fails a test262 that was incorrectly fixed. A follow on patch
      will fix the test262 test.
      
      Bug: v8:5751
      Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
      Change-Id: I8c66c6286287e686f4cd152fa1301f9d51c38654
      Reviewed-on: https://chromium-review.googlesource.com/1180488Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
      Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#55437}
      59c03fef