- 02 Aug, 2022 2 commits
-
-
Nico Hartmann authored
This reverts commit 872b7faa. Reason for revert: Somewhat speculative revert because of https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux%20-%20gc%20stress/39673/overview (reverting locally resolved the issue for me) Original change's description: > Fix Context PromiseHook behaviour with debugger enabled > > This is a solution for https://github.com/nodejs/node/issues/43148. > > Due to differences in behaviour between code with and without the debugger enabled, some promise lifecycle events were being missed and some extra ones were being added. This change resolves this and verifies the event sequence is consistent between code with and without the debugger. > > Change-Id: I3dabf1dceb14233226b1752083d659f1c2f97966 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3779922 > Reviewed-by: Victor Gomes <victorgomes@chromium.org> > Commit-Queue: Camillo Bruni <cbruni@chromium.org> > Reviewed-by: Camillo Bruni <cbruni@chromium.org> > Cr-Commit-Position: refs/heads/main@{#82132} Change-Id: I3e05adead5d8033906055e0741854da68aade2ac No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3804859 Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Owners-Override: Nico Hartmann <nicohartmann@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/main@{#82136}
-
Stephen Belanger authored
This is a solution for https://github.com/nodejs/node/issues/43148. Due to differences in behaviour between code with and without the debugger enabled, some promise lifecycle events were being missed and some extra ones were being added. This change resolves this and verifies the event sequence is consistent between code with and without the debugger. Change-Id: I3dabf1dceb14233226b1752083d659f1c2f97966 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3779922Reviewed-by:
Victor Gomes <victorgomes@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#82132}
-
- 27 Jul, 2022 1 commit
-
-
Fanchen Kong authored
This change fixes two issues with VTune JIT Profiling API. 1. Update way of setting flag "--no-compact-code-space" to avoid changing flags after initialization v8. 2. Fix a crash from visiting uninitialized ptr. Change-Id: I4878ffd554ce53630db961fe09b49e081b0091bf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3787321Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Fanchen Kong <fanchen.kong@intel.com> Cr-Commit-Position: refs/heads/main@{#82003}
-
- 22 Jul, 2022 1 commit
-
-
Suraj Sharma authored
All ETW Events are controlled by v8_enable_system_instrumentation. This flag is turned off when perfetto is enabled since traces events flowing through TRACE_EVENT macros can't be intercepted by Recorder. Since, stack walking Events don't use TRACE_EVENT it can be turned back on, when using perfetto. Hence, creating a separate Build Flag for emitting stack walking event until the recorder is ported. Bug: v8:11043 Change-Id: I6cdb81400780e54fddf6d6e2476cad29c60483d2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3704465Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Suraj Sharma <surshar@microsoft.com> Cr-Commit-Position: refs/heads/main@{#81879}
-
- 20 Jul, 2022 2 commits
-
-
Andreas Haas authored
Tasks may contain Globals, which have to get destroyed before isolate shutdown. R=cbruni@chromium.org Bug: chromium:1345081 Change-Id: I915baafd870c7bb8475b19736878179d8a22ca5a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3770108 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#81840}
-
Andreas Haas authored
This reverts commit 9981f2e5. Reason for revert: This CL landed by accident, we decided back then to land a different CL. Original change's description: > [d8] quit() should not dispose the isolate > > R=cbruni@chromium.org > > Bug: chromium:1338150 > Change-Id: I5e5f8ede942dd37112766812a3c84a356f0b6ca9 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3714355 > Reviewed-by: Camillo Bruni <cbruni@chromium.org> > Commit-Queue: Andreas Haas <ahaas@chromium.org> > Cr-Commit-Position: refs/heads/main@{#81827} Bug: chromium:1338150 Change-Id: Ib058d90a0c09e7cc65bdecee20580dd9e1f184d9 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3773776 Commit-Queue: Clemens Backes <clemensb@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Auto-Submit: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#81838}
-
- 19 Jul, 2022 1 commit
-
-
Andreas Haas authored
R=cbruni@chromium.org Bug: chromium:1338150 Change-Id: I5e5f8ede942dd37112766812a3c84a356f0b6ca9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3714355Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#81827}
-
- 18 Jul, 2022 1 commit
-
-
Samuel Groß authored
The sandbox crash filter must be installed after the sandbox has been initialized, which now happens during V8::Initialize. Bug: v8:10391 Change-Id: I0103e32f091843415aaff4ec1c9bd93603244144 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/+/3769689Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Auto-Submit: Samuel Groß <saelo@chromium.org> Cr-Commit-Position: refs/heads/main@{#81771}
-
- 15 Jul, 2022 1 commit
-
-
Samuel Groß authored
As sandboxed pointers are now default-enabled when the sandbox is enabled, it is no longer possible to deactivate the sandbox at runtime. This CL therefore removes all the logic that was required to support a sandbox that could be disabled at runtime, moves the initialization of the sandbox into V8::Initialize, and deprecates V8::InitializeSandbox. This change also makes the sandbox initialization deterministic if FLAG_random_seed is supplied. Bug: v8:10391 Change-Id: Ibd49f7c251b7c58c642f18a551ecc2c391740970 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/+/3762583Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Samuel Groß <saelo@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#81746}
-
- 11 Jul, 2022 1 commit
-
-
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:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#81634}
-
- 06 Jul, 2022 1 commit
-
-
Joyee Cheung authored
When the failed access callback is configured but it doesn't throw, we should return instead of expecting an exception, otherwise it would crash because there isn't one. This patch also adds --throw-on-failed-access-check and --noop-on-failed-access-check in d8 to mimic the behavior of the failed access check callback in chromium. Bug: chromium:1339722 Change-Id: Ie1db9d2fb364c6f8259eb9b8d81a21071c280a80 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3737305 Commit-Queue: Joyee Cheung <joyee@igalia.com> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#81557}
-
- 05 Jul, 2022 1 commit
-
-
Maya Lekova authored
This CL fixes a performance regression by conditionally compiling an expensive instance check only in debug mode. Bug: chromium:1329463 Change-Id: I2cceb7c06fa6db967923047a4dee63a93a0b72a2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3743385 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Auto-Submit: Maya Lekova <mslekova@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#81519}
-
- 24 Jun, 2022 1 commit
-
-
Shu-yu Guo authored
Replace MutexGuards with ParkedMutexGuards where GC might happen. Change-Id: Ie782ca01962bd522870d3f82327aefd89095b165 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3720729 Auto-Submit: Shu-yu Guo <syg@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#81360}
-
- 22 Jun, 2022 1 commit
-
-
Shu-yu Guo authored
Add ParkedScopes in d8 where it blocks. Change-Id: I369fbdb361b4e357ff6ceef53fbf52f543979438 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3704903Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Shu-yu Guo <syg@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#81314}
-
- 15 Jun, 2022 1 commit
-
-
Clemens Backes authored
This CL explicitly disables the --freeze-flags-after-init flag for cases where we modify flags after initialization. This is only tests, fuzzers, and special options to d8, thus not security relevant. These should be the last blockers for enabling the flag globally. R=cbruni@chromium.org Bug: v8:12887 Change-Id: I1d8a03dcc20e524d30c967f6fe15f6401de77612 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3706619Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#81179}
-
- 10 Jun, 2022 1 commit
-
-
Joyee Cheung authored
Adds Module::GetStalledTopLevelAwaitMessage() API which searches for modules that have no pending async dependencies but have not yet resolved. An embedder may call this API when they are about to exit to check if TLA evaluation has stalled and provide a better error message. Change-Id: I3b88802f70cc84c973551f13d73ef3e3d06f4027 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2341765 Commit-Queue: Joyee Cheung <joyee@igalia.com> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#81080}
-
- 08 Jun, 2022 2 commits
-
-
Leszek Swirski authored
Anyone using CopyablePersistentTraits should be using v8::Global, so deprecate it and fix the uses in V8. Bug: v8:12915 Change-Id: I25e6f2a03e070db9e9af9bbd9ea8cbc0f838c5ac Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3669254Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#81001}
-
Samuel Groß authored
If enabled, a signal handler is installed which intercepts memory access violations (e.g. SIGSEGV) and checks whether they occurred inside the sandbox address space, in which case the process is terminated cleanly as this does not represent a (security) issue with the sandbox. However, if the access violation occurred outside the sandbox, the access violation is forwarded to the original signal handler. The filter can be enabled in d8 by specifying --enable-sandbox-crash-filter. Bug: v8:12878 Change-Id: If9d76267e90ee79ee81ab793d7774afed6226b7c 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/+/3688408Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Samuel Groß <saelo@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#80999}
-
- 03 Jun, 2022 1 commit
-
-
Clemens Backes authored
Extend the effect of --freeze-flags-after-init to also protect updates of individual flags instead of only the API. For this, we wrap each flag in a {FlagValue} class which implicitly converts to the value of the flag. Some cases still require the explicit {value()} accessor though. That accessor is {constexpr}, in contrast to the implicit conversion, because otherwise clang emits a lot of warnings about dead code within "if (FLAG...)" scopes. R=cbruni@chromium.org Bug: v8:12887 Change-Id: I87d3457e49ceb317d34d6a21cf09c520d4171eb5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3683321Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Patrick Thier <pthier@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/main@{#80938}
-
- 31 May, 2022 3 commits
-
-
Marja Hölttä authored
This makes the following use cases produce a visible error: - deserializing invalid data w/ d8 [previously broken] - error in the script embedded in the web snapshot - d8 can't read web snapshot files Bug: v8:11525,v8:12820 Change-Id: I40a993194f9992a40c877261ebf9882e018b669b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3672415Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#80852}
-
Maya Lekova authored
Bug: chromium:1329234 Change-Id: I59f171d3e2ab0c07f79f631971b1695b9f706600 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3677294Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/main@{#80850}
-
Marja Hölttä authored
This reverts commit ff84cd04. Reason for revert: This CL had a commit from another branch which was supposed to land as a part of that CL ( https://chromium-review.googlesource.com/c/v8/v8/+/3672415/1 ), not this one. Going to reland a cleaned up version. Original change's description: > [rab/gsab] Fix ObjectSerializer > > Without this fix, the byte length for GSABs is probably serialized > wrong. A failing test is omitted since it would be pretty involved > (currently this code path is only hit with --stress-snapshot). > > Bug: v8:11111 > Change-Id: If7df98263cec9f82766c2fa6ba095b98b53a6fde > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3657431 > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Commit-Queue: Marja Hölttä <marja@chromium.org> > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Reviewed-by: Shu-yu Guo <syg@chromium.org> > Cr-Commit-Position: refs/heads/main@{#80780} Bug: v8:11111 Change-Id: I5fc3384484f6a8d2d6e40a404da0bf04167abc1d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3678838 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#80845}
-
- 27 May, 2022 1 commit
-
-
Marja Hölttä authored
Without this fix, the byte length for GSABs is probably serialized wrong. A failing test is omitted since it would be pretty involved (currently this code path is only hit with --stress-snapshot). Bug: v8:11111 Change-Id: If7df98263cec9f82766c2fa6ba095b98b53a6fde Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3657431Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#80780}
-
- 25 May, 2022 1 commit
-
-
Maya Lekova authored
The generated code checks if the receiver is a JS_API_OBJECT and if the receiver requires an access check, and if not it lowers the call to an API call. We also add compilation dependencies on the protector cell to deopt if our invariants change. (Note - the actual invalidation of these cells will be implemented in a follow up CL) Bug: v8:11321 Change-Id: I15722f1e5fac7176e292da4a35186e4609636aba Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2719563 Commit-Queue: Maya Lekova <mslekova@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/main@{#80748}
-
- 18 May, 2022 1 commit
-
-
gengjiawen authored
on latest MSVC, build will fail due to error C1017 log: https://github.com/bnoordhuis/v8-cmake/runs/6473602404 Change-Id: Ida6a4f1cbace68cbfc5aa7d4df2e7829fc755a55 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3653496Reviewed-by:
Clemens Backes <clemensb@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#80614}
-
- 13 May, 2022 1 commit
-
-
Samuel Groß authored
This is more consistent with similar features, for example V8_ENABLE_WEBASSEMBLY or V8_ENABLE_MAGLEV. Drive-by: remove V8_SANDBOX_IS_AVAILABLE as it's no longer needed. Bug: v8:10391 Change-Id: I8658c5b0c331a4c73892737083b2c2f9b8f84056 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/+/3647355 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Samuel Groß <saelo@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#80530}
-
- 11 May, 2022 1 commit
-
-
Clemens Backes authored
BS for "backing store", obviously. R=ahaas@chromium.org Bug: v8:12425 Change-Id: I310ba8e34e8ca2c7b7bdeec5f1bc184330fbaf28 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3641175Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#80477}
-
- 09 May, 2022 1 commit
-
-
Camillo Bruni authored
In preparation of renaming i::CodeEventDispatcher to i::Logger Bug: v8:12795, chromium:1316443 Change-Id: I28e129130852d41cf5e464e083bc27cff97a0fff Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3623543Reviewed-by:
Andreas Haas <ahaas@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#80427}
-
- 03 May, 2022 3 commits
-
-
Marja Hölttä authored
Bug: v8:11525 Change-Id: Ifd24e32dac905d47af233fa01b93206ee9ebdb8c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3623739 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#80342}
-
Danil Somsikov authored
Distinguish untrusted clients in v8 inspector and disable Profiler, HeapProfiler and Schema CDP domains for them. Bug: chromium:1313437 Change-Id: I7544c64acb4bc368392ba5f6a87ed62176828304 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3616517Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Danil Somsikov <dsv@chromium.org> Cr-Commit-Position: refs/heads/main@{#80340}
-
Camillo Bruni authored
To be consistent with the all the other tiers and avoid confusion, we rename --opt to ---turbofan, and --always-opt to --always-turbofan. Change-Id: Ie23dc8282b3fb4cf2fbf73b6c3d5264de5d09718 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3610431Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Jakob Linke <jgruber@chromium.org> Cr-Commit-Position: refs/heads/main@{#80336}
-
- 02 May, 2022 1 commit
-
-
Marja Hölttä authored
Bug: v8:11525 Change-Id: Ifec7ff76b5407d61f339d298a6f2eabbe77b7731 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3613398Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#80294}
-
- 27 Apr, 2022 2 commits
-
-
Camillo Bruni authored
Change-Id: Ib94979f4cf7f52a1544f2b3c0d51c0266a4fa14c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3586985Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#80223}
-
Camillo Bruni authored
Bug: v8:12795, chromium:1316443 Change-Id: I0ecaf8ebbf1a83d0d5b305fd014bc5a765c0d2f5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3610446Reviewed-by:
Victor Gomes <victorgomes@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#80222}
-
- 26 Apr, 2022 1 commit
-
-
Andreas Haas authored
Drive-by change: fix stray "//". R=clemensb@chromium.org Change-Id: I614bbc545ab8cd803f0c64f04e01fa55c4c2ec7b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3605610Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#80182}
-
- 25 Apr, 2022 1 commit
-
-
Andreas Haas authored
Additionally this CL adds some #if V8_ENABLE_WEBASSEMBLY that were missing. Change-Id: I7c840ebfa800ad62f0b6f075c997bd1989a007e2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3596169Reviewed-by:
Victor Gomes <victorgomes@chromium.org> Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#80151}
-
- 22 Apr, 2022 1 commit
-
-
legendecas authored
As per https://tc39.es/ecma262/#sec-hostimportmoduledynamically defined, referencingScriptOrModule in HostImportModuleDynamically can be a Script Record, a Module Record, or null. So to https://tc39.es/proposal-shadowrealm/#sec-shadowrealmimportvalue, the HostImportModuleDynamicallyCallback is been invoked with a `null` resource_name. This may not be considered a breaking change as the parameter resource_name is defined as Local<Value>. Updates d8's DoHostImportModuleDynamically to handle null resource_name, and resolve the dynamically imported specifier relative to the executing script's origin. In this way, we have to set ModuleEmbedderData.origin even if the JavaScript source to be evaluated is Script. Also, a ModuleEmbedderData is created for each ShadowRealm to separate their module maps from the initiator context's. Bug: v8:11989 Change-Id: If70fb140657da4f2dd92eedfcc4515211602aa46 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3522883Reviewed-by:
Shu-yu Guo <syg@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Commit-Queue: Chengzhong Wu <legendecas@gmail.com> Cr-Commit-Position: refs/heads/main@{#80118}
-
- 13 Apr, 2022 1 commit
-
-
Jakob Kummerow authored
This makes the installation sequence of WebAssembly.Tag slightly shorter, slightly faster, slightly cleaner in corner-case semantics, and slightly better documented. To allow testing this code, Isolate::InstallConditionalFeatures is exposed as d8.test.installConditionalFeatures(). Fixed: chromium:1314616 Change-Id: I44285e398b8797e0e7d2d8c782cecec3ba68a503 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3582382 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#79956}
-
- 07 Apr, 2022 2 commits
-
-
Camillo Bruni authored
- Always return a MaybeLocal<String> - Don't crash on long filenames Bug: chromium:1311923 Change-Id: I96e10337ceb32aeafafe0b73c78651a1ac38fb9f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3576122Reviewed-by:
Maya Lekova <mslekova@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#79859}
-
jameslahm authored
This is a follow up CL for https://crrev.com/c/3538284. Tests credited to https://crrev.com/c/3468352. - Add unicode filename path test. - Convert ansi encoded filename argv to utf8 encoded on windows. Because the ansi encoded filename argv may lose some information for unicode filename, and we need to use GetCommandLineW to get the actual unicode filename argument. And we convert it to utf8 encoded to be consistent with subsequent processing. - Use REPLACEMENT CHARACTER to replace the characters which cannot be encoded with sys.stdout.encoding in progress.py. This CL should be **reverted** if new unicode filenames cause problems. Bug: v8:12541 Change-Id: Ic5c5ae342b3a5b11c3119452af03c9165d429ed7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3568926Reviewed-by:
Clemens Backes <clemensb@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: 王澳 <wangao.james@bytedance.com> Cr-Commit-Position: refs/heads/main@{#79850}
-