- 12 Jul, 2022 13 commits
-
-
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:
-
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:
-
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 27 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:
-
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:
-
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:
-
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:
-
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:
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:
-
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:
-
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 authored
For Smi values. Bug: v8:7700 Change-Id: I903ef8aae818d64c3800206022c421c97e21a6f8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755143Reviewed-by:
-
Camillo authored
Change-Id: I462af434a695a09c9b65b11759e01aace463b414 No-Try: True Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755147 Auto-Submit: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#81641}
-
Leszek Swirski authored
Change StoreField to StoreTaggedField, which, similar to the move of LoadField to LoadTaggedField, operates on an offset and not a full Smi handler. Then, add support for stores to a property array by emitting a LoadTaggedField of the property array. As a drive-by, fix support for const fields and HeapObject fields with a class field type. Bug: v8:7700 Change-Id: Iff1fec35b82d3999ff273b069e9935166f43b98f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3752802 Commit-Queue: Igor Sheludko <ishell@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Thibaud Michaud authored
Suspender.{returnPromiseOnSuspend,suspendOnReturnedPromise} are not tied to a specific suspender anymore, so move them to WebAssembly.{returnPRomiseOnSuspend,suspendOnReturnedPromise}. With this change, the suspender property is not needed anymore on the function data. Convert it to a boolean flag that just indicates whether a function uses the JS Promise Integration API. R=ahaas@chromium.org Bug: v8:12191 Change-Id: I1b6d8e3190ebf5049dbc7eedee448999cf077509 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3748660Reviewed-by: -
Leszek Swirski authored
The comment was right but the actual condition wasn't. We should check whether the value is _not_ loadable. Bug: v8:7700 Change-Id: I1c721a56da5860c73c8179406abb1d3a8b9d08f6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755111 Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Marja Hölttä authored
Bug: v8:11111 Change-Id: I4e96e5440b7cfc61758a595dfdcf534c00a24358 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755109Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#81637}
-
Samuel Groß authored
This CL does the following: - It enables (i.e. allocates and initializes) the per-Isolate ExternalPointerTable when the sandbox is enabled. - It refactors the list of external pointer tags to mark them as "sandboxed" or "unsandboxed". An unsandboxed external pointer has a null tag. - It changes V8_SANDBOXED_EXTERNAL_POINTERS to now essentially just enable sandboxing for all available tags. - It modifies all low-level external pointer accessors to perform the ExternalPointerLookup only if the tag is non-zero and otherwise treat the slot as containing a raw pointer. This now allows rolling out external pointer sandboxing incrementally (separately for each external pointer type), which will in turn allow for more precise performance measurements of the impact of the sandbox. Note: when an external pointer tag is now marked as sandboxed (and V8_SANDBOXED_EXTERNAL_POINTERS is not enabled), the underlying slots are still 64-bits in size. This simplifies the implementation as we would otherwise need to deal with variably-sized external pointer slots. Local benchmarking suggests that the benefits from 32-bit external pointer slots are insignificant on typical benchmarks, so this should be ok. Drive-by: rename kExternalPointerSize to kExternalPointerSlotSize to make it more clear what it refers to (the on-heap storage size). Also delete CodeStubAssembler::InitializeExternalPointerField as it is not currently used and the implementation is fairly inefficient. Bug: v8:10391 Change-Id: I7c38729c7e9048d737a1a8ced84749f5b1f7feab 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/+/3736447Reviewed-by:
-
Leszek Swirski authored
Run Maglev on the Linux64 bots -- eventually we'll want to move it to the extra variant, but for now the flag is x64-only. Bug: v8:7700, v8:12727 Change-Id: I8b8329720ac96ab1655aef9e210a52092f81cc91 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3752979 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Pedro Falcato authored
Previously, the d8 prompt was printed without flushing stdout. This relies on the platform's libc to flush stdout when reading from stdin. This behavior is not portable and breaks the prompt on some platforms. Change-Id: Ieddf7ec5a6eab15796e69742bb4c9546ceb54c37 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3752006Reviewed-by:
Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#81634}
-
Thibaud Michaud authored
This CL is the first step towards the 'static API': https://github.com/WebAssembly/js-promise-integration/pull/1/files The limitation of the previous API is that the stack-switching wrappers are tied to a particular suspender. Since a suspender cannot be re-entered until the corresponding computation has completed, this prevents creating multiple concurrent instances of the same export. Multiple APIs have been proposed and are still under discussion to solve that, but the core idea is the same: the suspender should become a runtime argument of the export and the import. This CL implements that. For now, the suspender is still explicit everywhere: it is created in JS and passed to the export, and forwarded to the JS import. Eventually, the suspender may be completely hidden from JS: it would be materialized by the export wrapper, and "swallowed" by the import wrapper, as proposed in the PR above. R=ahaas@chromium.org Bug: v8:12191 Change-Id: Ic425a3fd920c7ad03874c636cd835d31c0e04994 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3748655Reviewed-by:
-
Leszek Swirski authored
Change-Id: I87d9d9a86edfed6112cdc5c7576e85bd5ae5f047 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3755141Reviewed-by:
-
legendecas authored
Print script's host_defined_options and source_mapping_url in DebugPrint. Change-Id: Ibd0b50e23f4d6f40eb4efbc6c4f384de24c401c6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3751943Reviewed-by:
-
Omer Katz authored
SynchronizePageAccess is used to synchronize between page initialization and reads from that page. It was not used for main thread reads because it was assumed that all pages are initialized on the main thread. With concurrent allocations, pages may be concurrently initialized, thus requiring a fence for main threads reads as well. Bug: v8:13041 Change-Id: I93e5162243ef5458579f239b131094d7171e8615 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3752804Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/main@{#81630}
-
Marja Hölttä authored
In this part: slice Bug: v8:11111 Change-Id: I66236039454ba50899a7c600b9a3df5fb5f7fc6f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3749582Reviewed-by:
-
Michael Achenbach authored
No-Try: true Bug: v8:7700 Change-Id: I66288693034bd501fece756916d0ef9a31e45e07 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3752798Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/b8e09c1..0b8f9f6 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/8bd72d6..0ca99b7 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: Ie77aaa20bbe44ba38a2a9b4e30e19363e3f6a02d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3754186 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@{#81627}
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/fuchsia-sdk/sdk: version:8.20220709.2.1..version:8.20220710.3.1 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I1bea8266d8505addc527c37d6228e11b908ea321 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3754185 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@{#81626}
-
Lu Yahan authored
Change-Id: I9cc2df6108b08aacf0b017f85128a9475022cedf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3754286 Auto-Submit: Yahan Lu <yahan@iscas.ac.cn> Commit-Queue: ji qiu <qiuji@iscas.ac.cn> Reviewed-by:
ji qiu <qiuji@iscas.ac.cn> Commit-Queue: Yahan Lu <yahan@iscas.ac.cn> Cr-Commit-Position: refs/heads/main@{#81625}
-
