1. 20 Nov, 2020 1 commit
  2. 24 Jul, 2020 1 commit
  3. 01 Apr, 2020 1 commit
  4. 28 Feb, 2020 1 commit
  5. 24 Feb, 2020 1 commit
  6. 21 Feb, 2020 2 commits
  7. 12 Sep, 2019 1 commit
  8. 19 Jul, 2019 1 commit
  9. 19 Jun, 2019 1 commit
  10. 17 Jun, 2019 1 commit
    • Seth Brenith's avatar
      [torque] Stricter object field verification, part 2 · 15ea19db
      Seth Brenith authored
      This change removes the special case in the Torque compiler for types
      that descend from JSObject: they will no longer get implicit
      "| Undefined" appended to their types for verification purposes. It
      removes any additional custom verification steps in objects-debug that
      are made redundant by that change.
      
      In order to do so safely, I categorized all cases where we were
      implicitly adding "| Undefined" to the field type, as follows:
      
      1. Classes that aren't using the generated verifier function (we should
         probably revisit these, but for now we at least know they're safe):
         - JSGlobalObject
         - JSFinalizationGroup
         - JSFinalizationGroupCleanupIterator
      
      2. Classes where the existing verifier is already at least as strict as
         what we would get after removing the implicit "| Undefined":
         - JSDate
         - JSPromise
         - JSRegExp
         - JSRegExpStringIterator
         - WasmMemoryObject
         - JSWeakRef
         - JSStringIterator
         - WasmExceptionObject
         - JSListFormat (fixed in part 1)
         - JSPluralRules (fixed in part 1)
         - JSRelativeTimeFormat (fixed in part 1)
         - JSSegmenter (fixed in part 1)
         - JSArrayBufferView (fixed in part 1)
         - JSTypedArray (fixed in part 1)
      
      3. Classes where, to the best of my knowledge based on code inspection,
         we already initialize the object correctly to pass the new stricter
         generated verifier:
         - JSFunction
         - JSArrayIterator
         - JSMessageObject
         - JSBoundFunction
         - JSAsyncFromSyncIterator
         - WasmModuleObject
         - JSAsyncFunctionObject
      
      4. Classes that needed some adjustment to their initialization order to
         avoid exposing uninitialized state to the GC:
         - JSArray (only in Factory::NewJSArray; Runtime_NewArray and
                    CodeStubAssembler::AllocateJSArray already behave fine)
         - WasmTableObject
         - JSDateTimeFormat
         - JSNumberFormat
         - JSCollator
         - JSV8BreakIterator
         - JSLocale
         - JSSegmentIterator
         - JSModuleNamespace
      
      5. Classes that had incorrect type definitions in Torque:
         - WasmGlobalObject (category 4 after correction)
      
      6. Classes that weren't fully initialized due to bugs:
         - JSGeneratorObject
         - JSAsyncGeneratorObject
      
      Bug: v8:9311
      Change-Id: I99ab303d3352423f50a3d0abb6eb0c9b463e7552
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1654980
      Commit-Queue: Seth Brenith <seth.brenith@microsoft.com>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Reviewed-by: 's avatarSigurd Schneider <sigurds@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#62228}
      15ea19db
  11. 23 May, 2019 1 commit
  12. 07 Feb, 2019 1 commit
  13. 17 Dec, 2018 1 commit
  14. 27 Nov, 2018 1 commit
  15. 01 Nov, 2018 1 commit
  16. 24 Oct, 2018 2 commits
  17. 23 Oct, 2018 1 commit
  18. 22 Oct, 2018 1 commit
  19. 19 Oct, 2018 1 commit
    • Frank Tang's avatar
      [Intl] Remove some unneeded code fom intl. · b8b7fe39
      Frank Tang authored
      Remove the file src/objects/intl-objects-inl.h
      Remove Intl functions:
      TypeFromInt(), TypeFromSmi(), IsObjectOfType(), AvailableLocalesOf()
      CreateNumberFormat() and Handle<String> version of CreateICULocale
      Also remove StringToICUService() inside
      src/objects/intl-objects.cc
      
      Bug: v8:5751
      Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
      Change-Id: Ifbd7ce162e04b8563c09e3ee5d99c55c6ad7bf7a
      Reviewed-on: https://chromium-review.googlesource.com/c/1290116
      Commit-Queue: Frank Tang <ftang@chromium.org>
      Reviewed-by: 's avatarSathya Gunasekaran <gsathya@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#56831}
      b8b7fe39
  20. 18 Oct, 2018 1 commit
  21. 16 Oct, 2018 1 commit
    • Sathya Gunasekaran's avatar
      [Intl] Port ResolveLocale · 9e984162
      Sathya Gunasekaran authored
      - Add a new Intl::ResolveLocale method and uses it in all the intl objects.
      - Fix CanonicalizeLocaleList to call out to HasProperty as per spec.
      - Add calls to CanonicalizeLocaleList where it was previously missing.
      - Change CanonicalizeLocaleListJS calls to CanonicalizeLocaleList now
        that we have migrated ResolveLocale.
      
      Bug: v8:5751
      Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
      Change-Id: I4249d2045c1556f18d570b00f7c92cbc3fa52077
      Reviewed-on: https://chromium-review.googlesource.com/c/1270255Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
      Reviewed-by: 's avatarFrank Tang <ftang@chromium.org>
      Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#56660}
      9e984162
  22. 04 Oct, 2018 1 commit
  23. 29 Sep, 2018 1 commit
  24. 17 Sep, 2018 1 commit
  25. 15 Sep, 2018 1 commit
  26. 05 Sep, 2018 3 commits