- 13 Jul, 2022 7 commits
-
-
Victor Gomes authored
Bug: v8:7700 Change-Id: I49c13eb2f251b8d547826928da479fa1186a11fd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3757894 Auto-Submit: Victor Gomes <victorgomes@chromium.org> Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#81682}
-
Leszek Swirski authored
We don't even need any new IR nodes for it. Bug: v8:7700 Change-Id: I8c2844f9bc6d21b09799395f817831685be21df7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3757883Reviewed-by: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#81681}
-
Camillo authored
This is a reland of commit c4301c04: - Fix thin string in string-compare.js with low gc interval Original change: - Rename TryBuildCompareOperationBranch to TryBuildCompareOperation - Add CheckedInternalizedString conversion Node that checks for string inputs and extracts internalised Strings from ThinStrings - Add BranchIfReferenceCompare Node - Add runtime functions to create internalised and thin Strings - Add deopt check to test/mjsunit/maglev/int32-branch.js Bug: v8:7700 Change-Id: I9221253f6bbeef12297419495c6eaf5096e06278 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755152Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#81680}
-
Marja Hölttä authored
In this part: join, toLocaleString Bug: v8:11111 Change-Id: I66ba85c33aae61a86e162352adb2d4bcf0dbac12 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3757333Reviewed-by: Shu-yu Guo <syg@chromium.org> Auto-Submit: Marja Hölttä <marja@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#81679}
-
Marja Hölttä authored
In this part: Array.from Bug: v8:11111 Change-Id: I266126e5b6bf217b49bb87b3a744443f5a5c1b2f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755137Reviewed-by: Shu-yu Guo <syg@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Auto-Submit: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#81678}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/ad70f68..78234e5 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: Ib3a6f9fcaa6cd837c18356186bad1d8ea5e9da43 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3758705 Bot-Commit: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#81677}
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/1dee059..8e95834 Rolling v8/third_party/fuchsia-sdk/sdk: version:8.20220711.1.1..version:8.20220712.1.1 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: If36aaf2dbd8456a21ec40fe901deef46090e5c74 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3760003 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#81676}
-
- 12 Jul, 2022 24 commits
-
-
Shu-yu Guo authored
Bug: v8:13066, v8:11111 Cq-Include-Trybots: luci.v8.try:v8_win_rel_ng,v8_win_dbg_ng Change-Id: I8066e04d713ba357e816ebaef04ef45518723d35 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3759235 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/main@{#81675}
-
Adam Klein authored
Bug: v8:13066 Change-Id: I01fe9b665a47a8780c820c32c74513b2361ece34 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3759229 Auto-Submit: Adam Klein <adamk@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#81674}
-
Jose Dapena Paz authored
If a tracing session starts after a script load has happened, then it is not emitted, so the source information is not visible in ETW. This is because we keep track of the loads already emitted, and we try to launch traces even when recording is not happening. To prevent this problem, this CS keeps track of when recording is happening. So, when it starts, it will emit all the already generated code immediately. This will add some overhead on tracing session start if system instrumentation is enabled, but this is better than not having instrumentation for previous symbols. There is still one problem: for each active isolate, it calls for replaying the event recording in an asynchronous task. So, for any JS task that is already running when tracing start, symbols will not be available. This makes this change less useful as, for a batch task or any long JS code that is already running when tracing start, we will not get symbols yet. Only after the foreground task runner runs the task to emit the ETW events we will get the symbols resolved in the trace. An specific approach was required for d8 interactive shell. As, when showing prompt, it is not processing the task runner queue, and it is only processed when the next script is launched, it first checks if it needs to generate ETW symbols information before running the script. Bug: v8:12932 Change-Id: I8b056c69cee0350f921a01c87beb9f2d51e10583 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3705541Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: José Dapena Paz <jdapena@igalia.com> Cr-Commit-Position: refs/heads/main@{#81673}
-
Frank Tang authored
Change temporal::ToTemporalTime to use default argument value Fix negative float division bug in BalanceTime Also implement: DifferenceTemporalPlainDate, DifferenceTemporalPlainYearMonth and DifferenceTemporalPlainTime Spec Text: https://tc39.es/proposal-temporal/#sec-temporal.plaintime.prototype.until https://tc39.es/proposal-temporal/#sec-temporal.plaintime.prototype.since https://tc39.es/proposal-temporal/#sec-temporal.plaindate.prototype.until https://tc39.es/proposal-temporal/#sec-temporal.plaindate.prototype.since https://tc39.es/proposal-temporal/#sec-temporal.plainyearmonth.prototype.until https://tc39.es/proposal-temporal/#sec-temporal.plainyearmonth.prototype.since https://tc39.es/proposal-temporal/#sec-temporal-differencetemporalplaindate https://tc39.es/proposal-temporal/#sec-temporal-differencetemporalplaintime https://tc39.es/proposal-temporal/#sec-temporal-differencetemporalplainyearmonth Bug: v8:11544 Change-Id: Ic717c69f4e399bc0ed4aaaaff4578cb329223205 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3741000 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/main@{#81672}
-
Shu-yu Guo authored
Bug: v8:11111 Change-Id: I5174d1ef9225d603850aa25e65484fe9ee06317a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3750323 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#81671}
-
Matthias Liedtke authored
This adds a new type 'none' as part of the WASM GC MVP. The type can only be used in combination with a nullable reference, e.g. 'ref.null none'. A 'nullref' is implicitly convertible to any nullable reference type. Bug: v8:7748 Change-Id: Ic5ab6cc27094b3c9103ce3584452daa34633612f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755136 Auto-Submit: Matthias Liedtke <mliedtke@google.com> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#81670}
-
Andy Wingo authored
Bug: v8:12868 Change-Id: I93595dfc168b6e4702b67bdd7355a1f7c18caa46 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3757332Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Andy Wingo <wingo@igalia.com> Cr-Commit-Position: refs/heads/main@{#81669}
-
Nikolaos Papaspyrou authored
ReadOnlySpaceObjectIterator did not iterate through objects, because of a bug in the initialization of `cur_addr_` and `cur_end_`. This CL also merges methods `Next` and `FromCurrentPage`. Change-Id: Id56bff279216c7a5982d984d80b649bd0c915959 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3758225Reviewed-by: Omer Katz <omerkatz@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> Cr-Commit-Position: refs/heads/main@{#81668}
-
Milad Fa authored
This patch fixes machine detection on nodejs where the build pipeline may not use gn and as a result certain macros will not get set. More details can be found in this comment: https://github.com/nodejs/node-v8/issues/223#issuecomment-1180505313 Change-Id: I0cbfc736b28bc130acbdc2cf2e27bbf687be463c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3757944Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/main@{#81667}
-
Andy Wingo authored
Bug: v8:12868 Change-Id: I714fffec248114a7ff61479f122a7df538e8e8d5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755140 Commit-Queue: Andy Wingo <wingo@igalia.com> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#81666}
-
Shu-yu Guo authored
The fast path of Array#toSpliced currently does not correctly initialize the elements range in the copy's FixedArray elements that will hold the inserted items. A GC can occur between the initial allocation of the elements before the inserted items are copied into it, which will fail heap verification. This CL also refactors CSA's FillFixedArrayWithSmiZero method to support only zeroing a portion of a FixedArray instead of the entire thing. Bug: v8:13035 Change-Id: I1bdb77d3b27f682620b45caa5a9c10ea0072a6ad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3750321Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#81665}
-
Leszek Swirski authored
Add a CreateFunctionContext implementation (which calls the same builtin used by Sparkplug), and fix our deopt checkpoints to include the context as a pseudo-register, so that Push/PopContext work with deopts. Bug: v8:7700 Change-Id: Ia3efd105683f6922181b9f4c7db0bac6a3a5fcec Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3757683Reviewed-by: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#81664}
-
Andreas Haas authored
The wasm instance got pushed three times in the lazy-compile builtin: 1) as part of the parameters; 2) as a parameter for the runtime function; 3) to load the jump table address after the runtime function; The third push can be avoided by loading the jump table address after all parameters get loaded from the stack again. R=clemensb@chromium.org Bug: v8:13049, v8:12926 Change-Id: I6117cfbbabc6250bf40732b6921c0e629fd85fa6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755138Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#81663}
-
Clemens Backes authored
If we detect out-of-order sections, we should not enter the individual decoding functions, because they might make assumptions that are not true in the error case. In this case, a DCHECK was firing if we call {DecodeFunctionSection} twice. R=ahaas@chromium.org Bug: chromium:1342274 Change-Id: I3d9d8c8c604aeeb92b9766f07d4b5464f4c8d72c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755112 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#81662}
-
Danylo Boiko authored
Bug: v8:12783 Change-Id: I718ba43c63d8010f9a512e6bd47ea58fbb4970ce Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3756142 Commit-Queue: Danylo Boiko <danielboyko02@gmail.com> Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/main@{#81661}
-
Patrick Thier authored
With the flag --always-use-forwarding-table we could end up turning a String into a ThinString that had a forwarding index set. This could happen when a String with a forwarding index is externalized. Bug: chromium:1337469 Change-Id: Iea05586f61e2b78d83d04d5d2e94c4dca2892c1f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3735164Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Patrick Thier <pthier@chromium.org> Cr-Commit-Position: refs/heads/main@{#81660}
-
ishell@chromium.org authored
... in order to prepare for smoother rollout via the finch flag. Bug: v8:12054, chromium:1343515 Change-Id: I24f51b73daa35c8de6967e8eb088dd3bee95fc4f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755120Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#81659}
-
Marja Hölttä authored
Bug: chromium:1338838 Change-Id: I1b8c54b460d272b19a4faa180a491e725bee4b79 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3726147Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#81658}
-
Marja Hölttä authored
In this part: splice, flat, flatMap Bug: v8:11111 Change-Id: Ide06c1137c6b4def70d09d479cfbedfb2d7c8450 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755106Reviewed-by: Shu-yu Guo <syg@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#81657}
-
Richard Wang authored
Mac builder added per https://chromium-review.googlesource.com/c/v8/v8/+/3755921/comments/dc378d70_002b4107 Bump the re-client version to match the same one chromium is currently using: https://source.chromium.org/chromium/chromium/src/+/main:DEPS;l=265;drc=11428e8ebaf6a78020d442da479b5b0daa0dffb5 The older version of re-client 0.40.0.40ff5a5 will not work when attempting to use it in a recipe targeting mac The version bump has been tested successfully with V8 Official Linux64 (reclient) https://ci.chromium.org/raw/build/logs.chromium.org/v8/led/richardwa_google.com/dd361303d10e4d506bd31e16ca73bdef6183e622f55493f90d9c152195c5c4fc/+/build.proto?server=chromium-swarm.appspot.com and V8 Linux64 - builder (reclient) https://ci.chromium.org/raw/build/logs.chromium.org/v8/led/richardwa_google.com/758cd57ad9ee572bcfe339a2435eb82e1028e72bf74a7b57cabfd616ffad1e28/+/build.proto?server=chromium-swarm.appspot.com Bug: b:238283947 Change-Id: I88e306f930c030173813b591e63a363da2d47cf1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3752430Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Richard Wang <richardwa@google.com> Cr-Commit-Position: refs/heads/main@{#81656}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/0b8f9f6..ad70f68 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I962a4a1199600207f3fbb6c7403acda9f0a8f340 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755216 Bot-Commit: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#81655}
-
v8-ci-autoroll-builder authored
Rolling v8/buildtools/linux64: git_revision:03ce92df5f9875bd9929b564be4b612713569aa9..git_revision:9ef321772ecc161937db69acb346397e0ccc484d Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/1601b3e..d22bf60 Rolling v8/third_party/fuchsia-sdk/sdk: version:8.20220710.3.1..version:8.20220711.1.1 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I0c21f66a912363189a438b6f764c46c4b306cb14 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755215 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#81654}
-
Luis Fernando Pardo Sixtos authored
Removing dead code. Change-Id: Ib477003cddb02441304efcb0400d511d235d07e4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3756381Reviewed-by: Shu-yu Guo <syg@chromium.org> Commit-Queue: Luis Fernando Pardo Sixtos <lpardosixtos@microsoft.com> Cr-Commit-Position: refs/heads/main@{#81653}
-
Frank Tang authored
This is a reland of commit a10194cf Original change's description: > [Temporal] Add add/subtract to Duration > > Also implement AOs: ToRelativeTemporalObject, AddDuration, AddDurationToOrSubtractDurationFromDuration, > ParseTemporalRelativeToString, DefaultTemporalLargestUnit, > DifferenceZonedDateTime > > Spec Text: > https://tc39.es/proposal-temporal/#sec-temporal.duration.prototype.add > https://tc39.es/proposal-temporal/#sec-temporal.duration.prototype.subtract > https://tc39.es/proposal-temporal/#sec-temporal-adddurationtoorsubtractdurationfromduration > https://tc39.es/proposal-temporal/#sec-temporal-addduration > https://tc39.es/proposal-temporal/#sec-temporal-torelativetemporalobject > https://tc39.es/proposal-temporal/#sec-temporal-parsetemporalrelativetostring > https://tc39.es/proposal-temporal/#sec-temporal-defaulttemporallargestunit > https://tc39.es/proposal-temporal/#sec-temporal-differencezoneddatetime > > Bug: v8:11544 > Change-Id: Id2eff50d7f810042e1b7c53c49a09f9e489d5460 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3699301 > Commit-Queue: Frank Tang <ftang@chromium.org> > Reviewed-by: Adam Klein <adamk@chromium.org> > Cr-Commit-Position: refs/heads/main@{#81650} Bug: v8:11544 Change-Id: I4bf8055bc328e28cd40a4eaa282d125d69c47e96 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3756745Reviewed-by: Adam Klein <adamk@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/main@{#81652}
-
- 11 Jul, 2022 9 commits
-
-
Frank Tang authored
This reverts commit a10194cf. Reason for revert: Merge conflict break build Original change's description: > [Temporal] Add add/subtract to Duration > > Also implement AOs: ToRelativeTemporalObject, AddDuration, AddDurationToOrSubtractDurationFromDuration, > ParseTemporalRelativeToString, DefaultTemporalLargestUnit, > DifferenceZonedDateTime > > Spec Text: > https://tc39.es/proposal-temporal/#sec-temporal.duration.prototype.add > https://tc39.es/proposal-temporal/#sec-temporal.duration.prototype.subtract > https://tc39.es/proposal-temporal/#sec-temporal-adddurationtoorsubtractdurationfromduration > https://tc39.es/proposal-temporal/#sec-temporal-addduration > https://tc39.es/proposal-temporal/#sec-temporal-torelativetemporalobject > https://tc39.es/proposal-temporal/#sec-temporal-parsetemporalrelativetostring > https://tc39.es/proposal-temporal/#sec-temporal-defaulttemporallargestunit > https://tc39.es/proposal-temporal/#sec-temporal-differencezoneddatetime > > Bug: v8:11544 > Change-Id: Id2eff50d7f810042e1b7c53c49a09f9e489d5460 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3699301 > Commit-Queue: Frank Tang <ftang@chromium.org> > Reviewed-by: Adam Klein <adamk@chromium.org> > Cr-Commit-Position: refs/heads/main@{#81650} Bug: v8:11544 Change-Id: Ia40c6f47d7cf6255b0ad6f2f70571b79c7e2d7af No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3756742 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Adam Klein <adamk@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/main@{#81651}
-
Frank Tang authored
Also implement AOs: ToRelativeTemporalObject, AddDuration, AddDurationToOrSubtractDurationFromDuration, ParseTemporalRelativeToString, DefaultTemporalLargestUnit, DifferenceZonedDateTime Spec Text: https://tc39.es/proposal-temporal/#sec-temporal.duration.prototype.add https://tc39.es/proposal-temporal/#sec-temporal.duration.prototype.subtract https://tc39.es/proposal-temporal/#sec-temporal-adddurationtoorsubtractdurationfromduration https://tc39.es/proposal-temporal/#sec-temporal-addduration https://tc39.es/proposal-temporal/#sec-temporal-torelativetemporalobject https://tc39.es/proposal-temporal/#sec-temporal-parsetemporalrelativetostring https://tc39.es/proposal-temporal/#sec-temporal-defaulttemporallargestunit https://tc39.es/proposal-temporal/#sec-temporal-differencezoneddatetime Bug: v8:11544 Change-Id: Id2eff50d7f810042e1b7c53c49a09f9e489d5460 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3699301 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/main@{#81650}
-
Frank Tang authored
Also change InterpretISODateTimeOffset parameter type. Add AOs: ToTemporalDateTimeRoundingIncrement Spec Text: https://tc39.es/proposal-temporal/#sec-temporal.zoneddatetime.prototype.round https://tc39.es/proposal-temporal/#sec-temporal.plaindatetime.prototype.round https://tc39.es/proposal-temporal/#sec-temporal-totemporaldatetimeroundingincrement Bug: v8:11544 Change-Id: I1a74ed165b3643467d8d894fd16fd59217ba8063 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3749374Reviewed-by: Adam Klein <adamk@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/main@{#81649}
-
Anton Bikineev authored
With pointer compression enabled the compiler may not inline some Member functions on some platforms, because Member stores and loads become slightly more expensive. Inlining is however important with pointer compression - it allows to further optimize the code by eliminating the global load. Bug: chromium:1325007 Change-Id: Ia37d223e78853a8218e0b2732a3f08aa58929000 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3756141Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Anton Bikineev <bikineev@chromium.org> Cr-Commit-Position: refs/heads/main@{#81648}
-
Maksim Sadym authored
1. Add `toISOString` to `v8::Date`. 2. Switch serialization to `ISOString`. Bug: v8:13043 Change-Id: I8a852f4a4a46bb3b8e5d52ef3cdffde7a408b403 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3749203 Auto-Submit: Maksim Sadym <sadym@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#81647}
-
Leon Bettscheider authored
This CL is part of an effort to enable concurrent marking in MinorMC. For this purpose we plan to reuse the IncrementalMarking class which already implements a part of the concurrent marking code for MajorMC. IncrementalMarking internally uses the MarkingWorklists class. This CL adapts the stop-the-world marking implementation of MinorMC to use the MarkingWorklists class. Bug: v8:13012 Change-Id: I3c4eb33142f2630e89aa3771b6065b9f82dc0847 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3747862Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Omer Katz <omerkatz@chromium.org> Commit-Queue: Leon Bettscheider <bettscheider@google.com> Cr-Commit-Position: refs/heads/main@{#81646}
-
Leszek Swirski authored
Bytecode generation already emits a manual runtime call for CreateFunctionContext in the case where the slot count exceeds the maximum, so we don't need to check for this case in Sparkplug. Change-Id: I228bc710c5093f7c752dc7bda7912e3af1547371 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755118 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#81645}
-
Joyee Cheung authored
Previously SnapshotCreator demanded a blob to be created before it can be destructed in debug build, this patch removes the DCHECK so that the embedder can choose not to create the blob when e.g. the snapshot building isn't successful due to errors. Change-Id: I72939be1e0d79b257b9761f48a72e45325a1f6d8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3716682Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Joyee Cheung <joyee@igalia.com> Cr-Commit-Position: refs/heads/main@{#81644}
-
Samuel Groß authored
There seem to be some issues with sandboxed external references in the serializer which cause the --stress-snapshot mode to fail. This CL changes the serializer to serialize external pointers that are unsandboxed (currently all of them) as "regular" external references, not "sandboxed" ones. This should fix the issues on the bots. Bug: v8:10391 Change-Id: I2f889e1d0aa9c5958d4f4337e114423b650c1bb2 Cq-Include-Trybots: luci.v8.try:v8_linux64_heap_sandbox_dbg_ng,v8_linux_arm64_sim_heap_sandbox_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755148Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Samuel Groß <saelo@chromium.org> Cr-Commit-Position: refs/heads/main@{#81643}
-