- 28 Oct, 2020 23 commits
-
-
Andreas Haas authored
The flag has been enabled by default for two version now, so it is time to remove it. R=binji@chromium.org Bug: v8:9921 Change-Id: I833e04a3f9d238e7bcf27e93148c9492776af3c6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2402034Reviewed-by: Ben Smith <binji@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#70838}
-
Andreas Haas authored
This is a reland of 397ddfee The benchmark does not expect the counter anymore, so we can reland the CL now. Original change's description: > [wasm] Remove V8.LiftoffCompileMicroSeconds counter > > The counter gets created but isn't used anywhere. > > R=clemensb@chromium.org > > Bug: v8:10933 > Change-Id: I480e601f8118475a3ce750ba97fdae6780342d49 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2497166 > Reviewed-by: Clemens Backes <clemensb@chromium.org> > Commit-Queue: Andreas Haas <ahaas@chromium.org> > Cr-Commit-Position: refs/heads/master@{#70756} Bug: v8:10933 Change-Id: I74c490916efa8ddf80491097fe358865d3bfab2c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2498697 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#70837}
-
Dan Elphick authored
This replaces kBytecodeToBuiltinsMapping (an array with currently 549 32-bit integers = 2196 bytes) with kWideBytecodeToBuiltinsMapping which is an array of uint8_t with only 183 values. The new array contains just the mappings from wide handlers to builtins but only once since the mapping is the same for extra wide handlers. (No mapping array is required for normal handlers since they map 1:1). This reduces d8's binary size by 2008 bytes on x64. As a result Interpreter::GetBytecodeHandler will be slightly slower than before, but its only use in non-test code is in Runtime_DebugBreakOnBytecode which does not need to be fast. Bug: v8:11066 Change-Id: Iafc28fba2d1b62c1d49ceabe731d8b52a82dd2fd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2502291 Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#70836}
-
Clemens Backes authored
Within "ExecuteCompilationUnits", we now have separate events for baseline compilation and top-tier compilation. But there is still a larger chunk that is not reflected in the default "v8.wasm" category yet: wrapper compilation. This CL adds a trace event for that. R=ahaas@chromium.org Change-Id: I0e74b8f5f95f7a6d674582f2d386cc58d4ad547a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2502344Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#70835}
-
Mythri A authored
This is a reland of d7ece57e with a fix to failures on NumFuzz. Original change's description: > [turboprop] Add a slot for optimization marker in feedback vector > > Optimization marker and the optimized code used to share the same slot > in the feedback vector as they were mutually exclusive. With turboprop > we would want to mark the function for tier up to Turbofan while holding > the optimized code for Turboprop. So this cl uses the existing padding > field to hold the optimization marker instead. > > As a driveby, removes unused JSFunction::ClearOptimizedCodeSlot function > and fixes a minor bug in Runtime_GetOptimizationStatus. > > Bug: v8:9684 > Change-Id: I18c551a69648a0837d16c5453d023c0b295b1521 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2467836 > Commit-Queue: Mythri Alle <mythria@chromium.org> > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > Cr-Commit-Position: refs/heads/master@{#70789} Bug: v8:9684 Change-Id: Ie6aa3c061a852bb047b5921e4e747d43505568e3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2502871 Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#70834}
-
Andreas Haas authored
The value of a node was accessed without prior HasValue check. With WebAssembly this node is not guaranteed to be a value. R=mslekova@chromium.org Change-Id: I62170183f3940a04b0550dfbb78cb49d2f5d7f72 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2504250Reviewed-by: Maya Lekova <mslekova@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#70833}
-
Clemens Backes authored
The current tracing (in the "v8.wasm" category) has no indication about the compilation tiers, which makes it hard to see when baseline compilation finished and how long top tier compilation takes. The disabled-by-default "v8.wasm.detailed" category on the other hand is much too detailed for bigger modules, such that we run into a tracing buffer overflow pretty quickly, and lose subsequent events. This CL adds general trace events for baseline compilation and top tier compilation, which are not per-unit but per-thread. Hence their number is much lower than the number of events in "v8.wasm.detailed". Because the events for baseline compilation and top tier compilation have different colors, it's pretty easy to see whether baseline compilation or top-tier compilation happens. R=ahaas@chromium.org Change-Id: Ic581a335f74018681fa552d14b81c48217b5a80c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2502337Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#70832}
-
Zhi An Ng authored
We made array-concat run faster in https://crrev.com/c/2504853. Bug: v8:7783 Change-Id: Iabefb58f92e24ffa4e0589a7c8b9e2b3e12c6e47 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2504859 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by: Santiago Aboy Solanes <solanes@chromium.org> Cr-Commit-Position: refs/heads/master@{#70831}
-
Jakob Gruber authored
.. if --enable-embedded-constant-pool (ppc-only) is not set. In this case, the field simply doesn't exist, so we shouldn't read from it, and definitely not write to it. Tbr: leszeks@chromium.org Bug: v8:11036 Change-Id: I8b2cf8cdd084f29060377790c882850bd9ec43c5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2504255Reviewed-by: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#70830}
-
Ulan Degenbaev authored
This calls Heap::CollectAllAvailableGarbage() in the heap snapshot generator. Bug: chromium:1113467 Change-Id: Ia7f58893a36f11f80f1bffafcea0e73f5ec49901 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2456687 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#70829}
-
Zhi An Ng authored
The immediate might not be 2 bytes from start of instruction, because the opcode is leb encoded. Bug: chromium:1143053 Change-Id: I3c514e771419470ce34e02d4faa24e9e59676aa6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2504852Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#70828}
-
Jakob Gruber authored
.. and add a --text-is-readable flag to support non-readable .text sections. This splits the embedded blob hash into two dedicated hashes for data and code sections. The main benefit is that we can now keep at least a partial hash even with non-readable .text sections. The second part of this CL adds a --text-is-readable runtime flag to support such platforms (with non-readable .text). It currently doesn't do much; setting it enables a few additional DCHECKs, disables the constant pool on x64, and and disables verification of the embedded blob's *code* hash. Bug: v8:10707 Change-Id: Ib91ed8b50b50f2cd81677f62920bea6fb92af453 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2504251Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#70827}
-
Etienne Pierre-doray authored
Currently MockPlatformForUnmapper has shorter lifetime than the isolate that uses it. This leads to use-after-free races in concurrent tasks that fetch the mock platform just before it is freed. This CL ensures that MockPlatformForUnmapper is valid throughout the whole lifetime of the isolate Change-Id: I94a658bf7eb70d924a19522dab09744f21782972 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2502809Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#70826}
-
Zhi An Ng authored
This test creates an array that is 500000 elements long. Calling assertEquals on this with another array is really slow, especially on simulator runs. Most of this array is empty, only the first few elements and last few elements contain meaningful items, so we check those specific indices. On a local run this test goes from ~250s (--jitless) or ~111s to <1s. out/arm64.build/d8 --test test/mjsunit/mjsunit.js test/mjsunit/array-concat.js --random-seed=1 --nohard-abort --testing-d8-test-runner [--jitless] (using --jitless makes the test even slower) Bug: v8:7783 Change-Id: I660d3a9f1b3fe3afaa58fce28f493641059ba226 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2504853 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#70825}
-
Michael Lippautz authored
Bug: chromium:1056170 Change-Id: I6512792cc088f1ffaf1d6f3e367db02a1f2c8277 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2504511 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#70824}
-
Zhao Jiazhong authored
When switching buffers, the last_call_pc_ should be adjusted like pc_, because the buffer's start address is changed. Besides, add a missing BlockTrampolinePoolScope. Change-Id: Iee6d9795a256e041bb2dbf7d8ca63f346a248539 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2504855Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/master@{#70823}
-
Jakob Gruber authored
The embedded metadata section is the off-heap equivalent to an on-heap Code object's metadata section. It contains no executable data, thus .rodata is the natural home for it. Another motivation is that some platforms do not grant read permissions on the .text section. Embedded blob stats before: EmbeddedData: Total size: 1322944 Data size: 25952 Code size: 1296992 And after: EmbeddedData: Total size: 1323372 Data size: 121452 Code size: 1201920 (Slight size increase due to additional padding.) Bug: v8:11036,v8:10707 Change-Id: Ib6b54a7e947966c7bd2fcc1e7e44c85e352f0063 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2502334Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#70822}
-
Clemens Backes authored
This CL extracts some functionality from inspector-test.cc to be reused by the inspector fuzzer. It also puts all functions in the v8::internal namespace, and adds separate functions in v8::internal to be called by ::main such that we have direct access to the full namespace there. R=szuend@chromium.org Bug: chromium:1142437 Change-Id: I671317822bdc1c721334469811893affcc460f8f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2501847Reviewed-by: Simon Zünd <szuend@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#70821}
-
Zhi An Ng authored
This is a reland of df34fb95 Original change's description: > [wasm-simd] Add more test cases for load lane > > Test load lane using memarg offset immediate, and also test all > supported alignments. > > Bug: v8:10975 > Change-Id: Iac7e9f7e335bd86528a8723b04df97a17d7a7f66 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2500928 > Commit-Queue: Zhi An Ng <zhin@chromium.org> > Reviewed-by: Bill Budge <bbudge@chromium.org> > Cr-Commit-Position: refs/heads/master@{#70816} TBR=bbudge@chromium.org Bug: v8:10975 Change-Id: I286776b351ecd3c78d56bec20c02a3ba283213df Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2504851Reviewed-by: Zhi An Ng <zhin@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#70820}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/929bcdb..eef4a9f Rolling v8/third_party/aemu-linux-x64: q6rFFTDSZ6MexUJ2yo5-IHfI0g1sohftVPqHt-TwJtYC..Cde6_Nup5XVxJODi7chcAAfy5-gsuGDvdepMA2nkfKMC Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/4f6c1bb..daba508 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/77cd4b4..dfa44da Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/cf34aa6..f9b4a22 TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I9fedef0e20e60e45d1c119c09e5208eb8d3fc4c6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2504930Reviewed-by: 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/master@{#70819}
-
Zhi An Ng authored
Prototype i8x16, i16x8, i32x4, i64x2 sign select on x64 and interpreter. Bug: v8:10983 Change-Id: I7d6f39a2cb4c2aefe31daac782978fe8b363dd1a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2486235 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Reviewed-by: Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#70818}
-
Zhi An Ng authored
This reverts commit df34fb95. Reason for revert: Broke msvc compile https://ci.chromium.org/p/v8/builders/ci/V8%20Win64%20-%20msvc/15566 Original change's description: > [wasm-simd] Add more test cases for load lane > > Test load lane using memarg offset immediate, and also test all > supported alignments. > > Bug: v8:10975 > Change-Id: Iac7e9f7e335bd86528a8723b04df97a17d7a7f66 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2500928 > Commit-Queue: Zhi An Ng <zhin@chromium.org> > Reviewed-by: Bill Budge <bbudge@chromium.org> > Cr-Commit-Position: refs/heads/master@{#70816} TBR=bbudge@chromium.org,zhin@chromium.org Change-Id: Ia80d167846dac99070e6e9d280dd4ea53455af30 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:10975 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2504850Reviewed-by: Zhi An Ng <zhin@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#70817}
-
Zhi An Ng authored
Test load lane using memarg offset immediate, and also test all supported alignments. Bug: v8:10975 Change-Id: Iac7e9f7e335bd86528a8723b04df97a17d7a7f66 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2500928 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by: Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#70816}
-
- 27 Oct, 2020 17 commits
-
-
Zhi An Ng authored
SSE instructions which access 16 bytes of data from the memory requires aligned access. So we force these instructions to be registers, since we don't have the correct memory alignment yet. Bug: v8:9198 Change-Id: I0f654efb95da26b1adc27022747ff45c4d6c5d04 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2500934Reviewed-by: Bill Budge <bbudge@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#70815}
-
Zhi An Ng authored
This is a follow up change to https://crrev.com/c/2499294. SSE instructions require memory operands to be 16-byte aligned, which we cannot guarantee yet. So we force the operands to be registers in the instruction selector. AVX instructiosn (VEX-encoded) support unaligned memory operands, but can have performance reductions if it crosses cache lines. For simplicity we also force the operands to be registers. In the codegen we can remove the case where the operand is not a register, and also for SSE assert that dst == src. Bug: v8:9198 Change-Id: Ibee33896dc9cc4e97d792c5b7bdf5e66ce34de9c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2500924Reviewed-by: Bill Budge <bbudge@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#70814}
-
Zhi An Ng authored
pshufb is a SSSE3 feature and so requires the scope before using. Change-Id: I42cf252079ba9aa9b09c2197a0e20b90ebc27b5d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2500927Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#70813}
-
Ng Zhi An authored
Bug: v8:11038 Change-Id: I21dc1bd048aa4d4d7068f7eba403a531a84849e1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2501968Reviewed-by: Bill Budge <bbudge@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#70812}
-
Ng Zhi An authored
And remove all ifdefs guarding the tests. Bug: v8:11038 Change-Id: I91487a4bd60b6f2e327d1c2348289e446d6e93d1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2501967Reviewed-by: Bill Budge <bbudge@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#70811}
-
Zhi An Ng authored
This is a reland of dde93768 Original change's description: > Add int64_t min and max to value helpers for test > > And also fix up a truncate float to int test that was using > int list as input instead of a float list. > > Change-Id: I544e38b2d212f8d11dfb5758db4fe6b283acae0d > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2419654 > Reviewed-by: Clemens Backes <clemensb@chromium.org> > Commit-Queue: Zhi An Ng <zhin@chromium.org> > Cr-Commit-Position: refs/heads/master@{#70774} Change-Id: Id196ea40eaf616d784d644346b912f1561fd97a0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2500926Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#70810}
-
Milad Fa authored
The displacement for vlbr and vstbr is a 12-bit unsigned integer. If a greater offset is passed we must fall back to using lrvg and strvg. Change-Id: I34107b82960a4d4de99fbf8b9324b13d9a455e67 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2504190Reviewed-by: Junliang Yan <junyan@redhat.com> Reviewed-by: Joran Siu <joransiu@ca.ibm.com> Commit-Queue: Milad Fa <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/master@{#70809}
-
Nicolas Dubus authored
- Created status enum with statuses kStarted, kAlreadyStarted and kErrorTooManyProfilers, returning when StartProfiling is invoked - Tests spin up one profiler, check kStarted returned; spin up another with same name, check kAlreadyStarted returned; Spin up 99 more profilers (100 total), check each returning kStarted, and one more, expecting 101st to return kErrorTooManyProfilers R=acomminos@fb.com, petermarshall@chromium.org, ulan@chromium.org Change-Id: I64e2e6396775f90f9f49f75331a075a47efa7fca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2486240Reviewed-by: Peter Marshall <petermarshall@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#70808}
-
Milad Fa authored
Port 965916c7 Original Commit Message: The actual number of double regs available on arm depends on the current CPU. In some cases, we care about the max count of double regs (e.g. around Save/RestoreFPRegs which always reserves spaces for the max); in others, we care about the actual count. Use DwVfpRegister::kNumRegisters to fetch the max (= 32). Use DwVfpRegister::SupportedRegisterCount() for the actual count (16 or 32). R=jgruber@chromium.org, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com BUG= LOG=N Change-Id: I55ef4a14b4a7676d9773f57ea66149a069c70448 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2502810Reviewed-by: Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Fa <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/master@{#70807}
-
Camillo Bruni authored
Add simple log file test with processor.mjs, mostly focusing on parsing the log file correctly. Change-Id: Ie8db569b65ecd526ef4474a64d4019f00707d159 Bug: v8:10668 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2484515 Commit-Queue: Dan Elphick <delphick@chromium.org> Auto-Submit: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Dan Elphick <delphick@chromium.org> Cr-Commit-Position: refs/heads/master@{#70806}
-
Bill Budge authored
- Adds a method to tell V8 that the process is cross-origin-isolated under COOP+COEP. In this case, SharedArrayBuffer can be enabled. Bug: chromium:923807 Change-Id: I729093665a50d2b3667c028e05b42d21d76b12d3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2502448Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Commit-Queue: Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#70805}
-
Michael Lippautz authored
Wrapper nodes are merged into their corresponding C++ object nodes when the reference between C++ and JS object has a wrapper class id set. Instead of iterating all global handles and checking for those with class ids, the new algorithm discovers them while iterating C++ objects. Note: Additional wrapper nodes, e.g., those from isolated worlds in Blink are not merged. Bug: chromium:1056170 Change-Id: I6dff8992e41d7a1a2c3b99a115a53df6b6fbb64c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2499661 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/master@{#70804}
-
Mythri Alle authored
This reverts commit d7ece57e. Reason for revert: failures on NumFuzz https://ci.chromium.org/p/v8/builders/ci/V8%20NumFuzz%20-%20debug/11818? Original change's description: > [turboprop] Add a slot for optimization marker in feedback vector > > Optimization marker and the optimized code used to share the same slot > in the feedback vector as they were mutually exclusive. With turboprop > we would want to mark the function for tier up to Turbofan while holding > the optimized code for Turboprop. So this cl uses the existing padding > field to hold the optimization marker instead. > > As a driveby, removes unused JSFunction::ClearOptimizedCodeSlot function > and fixes a minor bug in Runtime_GetOptimizationStatus. > > Bug: v8:9684 > Change-Id: I18c551a69648a0837d16c5453d023c0b295b1521 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2467836 > Commit-Queue: Mythri Alle <mythria@chromium.org> > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > Cr-Commit-Position: refs/heads/master@{#70789} TBR=rmcilroy@chromium.org,mythria@chromium.org,jgruber@chromium.org Change-Id: Ia9894fef713a522b9c3d349bef4abcde3e1e1832 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:9684 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2502870Reviewed-by: Mythri Alle <mythria@chromium.org> Commit-Queue: Mythri Alle <mythria@chromium.org> Cr-Commit-Position: refs/heads/master@{#70803}
-
Shu-yu Guo authored
Change-Id: I7c288f4e0c1dbc9600be2ccd69faecc4d38de17e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2500413Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/master@{#70802}
-
Michael Lippautz authored
cppgc must support the same feature set as the existing unified heap system, which requires support for wrapper-specific handling (drop on Scavenge, merge in snapshot). Replace JSMember by TracedReference to support IsRootForNonTracingGC() optimizations out of the box. cppgc support for wrapper/wrappable pairs will be added as followup. Change-Id: I3c6eff2b8dce5b71b04b2bd75182eb8672079a64 Bug: chromium:1056170 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2498685 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Omer Katz <omerkatz@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#70801}
-
Leszek Swirski authored
Add an initializer to the Serializer::allocation_size_ field so that the array is value-initialized to zero. Change-Id: I3bd9ecae63d9083e41cce4fbbfedc36ff5f0f741 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2502868 Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#70800}
-
Camillo Bruni authored
- Remove ic-processor.html since it's been fully integrated in the system-analyzer - Use new tools/system-analyzer/processor.mjs for command line ic-processor - Update tools landing page - Partially fix dependencies on web specific components in helper.mjs Bug: v8:10644 Change-Id: I0c99ff7c7859684e53aa3ab22489b1a8242e1a6e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2498606Reviewed-by: Marja Hölttä <marja@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#70799}
-