- 13 May, 2020 3 commits
-
-
Yolanda Chen authored
[regalloc] Do not spill uses that are constrained to move to register in backwards spilling heuristics For uses that are moved to registers, they are not beneficial for backwards spilling as it will introduce memory loads from stack to register. Bug: chromium:1066869, chromium:1063831 Change-Id: I562d22336b6607a8f7286fc65dbf5b95a941a130 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2172052Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Yolanda Chen <yolanda.chen@intel.com> Cr-Commit-Position: refs/heads/master@{#67765}
-
Tobias Tebbi authored
Bug: v8:7793, v8:10475 Change-Id: I3c528d07e8d3192d7110ebc81e9e89f79a7c735d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196132Reviewed-by:
Nico Hartmann <nicohartmann@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#67764}
-
Zhou, Zhiguo authored
Bug: v8:9909 Change-Id: I1bd17d6a1a6f32e9076d80c91be2743868ecad2b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2171475Reviewed-by:
Zhi An Ng <zhin@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Zhiguo Zhou <zhiguo.zhou@intel.com> Cr-Commit-Position: refs/heads/master@{#67763}
-
- 12 May, 2020 37 commits
-
-
Ng Zhi An authored
Bug: v8:10180 Change-Id: I4c1d18c71d1514a561c37fb9ae821617de949d87 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2194175Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#67762}
-
Shu-yu Guo authored
This reverts commit c25352f3. Reason for revert: Causing raytrace timeouts on TSAN: https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20TSAN%20-%20concurrent%20marking/13089 https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20TSAN%20-%20concurrent%20marking/13090 https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20TSAN%20-%20concurrent%20marking/13091 Original change's description: > Reland "[heap] Remove sweeping state in incremental marking" > > This is a reland of 7f29c48e > > After fixing TSAN failures in https://crrev.com/c/2192661 and https://crrev.com/c/2193712, this CL and be relanded without changes. > > Original change's description: > > [heap] Remove sweeping state in incremental marking > > > > Remove the SWEEPING state from incremental marking. Sweeping is now > > always completed when starting incremental marking. Before this change > > there needed to be a safepoint each for starting marking and completing > > sweeping. Now both happens within a single safepoint. > > > > Bug: v8:10315 > > Change-Id: Iad2835554865f2de24376372affe9a98992d1fa0 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2190419 > > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > > Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#67678} > > Bug: v8:10315 > Change-Id: Ic949d125e72c4d17fd427d08d4b6f9056721eee9 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196182 > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#67741} TBR=ulan@chromium.org,dinfuehr@chromium.org Change-Id: Ie529fd3bef13a28301f22876758d731e466d3939 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:10315 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2197457Reviewed-by:
Shu-yu Guo <syg@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/master@{#67761}
-
Frank Tang authored
Bug: v8:9934 Change-Id: I8e4c0bb647913b703c01fd0d11329fba254e5350 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2195491Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#67760}
-
Thibaud Michaud authored
The recent changes to support multi-value calls should also apply to indirect calls, so this bailout can be removed. R=ahaas@chromium.org Bug: v8:10408 Change-Id: Ia1b2e49caa6f308a4d2f30712a132c7e072df9f9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196350Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#67759}
-
Shu-yu Guo authored
This reverts commit e473d232. Reason for revert: Checking if build infra is fixed Original change's description: > Whitespace change to trigger bots > > Some bots turned red. Might be an infra failure. Let's see if this CL > makes it disappear. > > Tbr: machenbach@chromium.org > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Change-Id: I269257184cfca5423fb2c52ae8cfc1ad696002e9 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196352 > Reviewed-by: Clemens Backes <clemensb@chromium.org> > Commit-Queue: Clemens Backes <clemensb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#67757} TBR=clemensb@chromium.org Change-Id: Ibe1d2725cc2bd621a3243b8930b43f8ec732420b No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2197254Reviewed-by:
-
Clemens Backes authored
Some bots turned red. Might be an infra failure. Let's see if this CL makes it disappear. Tbr: machenbach@chromium.org No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: I269257184cfca5423fb2c52ae8cfc1ad696002e9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196352Reviewed-by:
-
Clemens Backes authored
Liftoff code generated for debugging has an extended function prologue which checks the "hook on function entry" flag on the isolate. Because of this, code positions between standard Liftoff code and Liftoff code for debugging do not match up. When (lazily) generating debug side tables, we always generate them for debugging-flavored Liftoff code. The issue that this CL fixes happened when we tried to inspect non-debug Liftoff code, and lazily generated the debug side table for that code. As noted above, source positions would not match up in that case, and we get DCHECK failures (or crashes in release builds) when inspecting the code. This issue was uncovered as part of the multi-threaded debugging effort, but because of the similarity in the stack trace, it might also fix the other issues linked below. We will get test coverage as soon as we add multi-threaded debugging tests (which are in development, but are still hitting other issues). R=thibaudm@chromium.org Bug: v8:10359, chromium:1071757, chromium:1079328, chromium:1072839 Change-Id: Ic0c14e635dc2a0b84ac86ceb6650288202dafedc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196349 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
-
Manos Koukoutos authored
Changes: - Don't use UNIMPLEMENTED where it can be run. - Implement OpcodeLength for gc types. - Remove unreachable code. - Request the correct feature 'gc' for the respective opcodes and types. Bug: 1079337, 1079450, 1081529, 1081011, 1080444 Change-Id: Ib081139ca805c6f5471a372f862638a3606254b1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196302 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by:
-
Clemens Backes authored
This is a reland of 902f48bd, fixed to avoid lock inversion problems detected by TSan. Original change's description: > [wasm][debug] Fix tier down for multiple isolates > > If multiple isolates are using the same module, we need to keep it > tiered down as long as any isolate still has a debugger open. > Also, we cannot short-cut the {NativeModule::TierDown} method, since the > previously triggered tier down might not have finished yet. > For now, each isolate starts an independent tier down (i.e. a full > recompilation). We could optimize this later by skipping functions that > are already tiered down, or are already scheduled for tier down, but we > still need to wait for tier-down to finish on each isolate. > > R=thibaudm@chromium.org > > Bug: v8:10359 > Change-Id: I7ea6a6f5d3977e48718ac5bc94f9831541f6173f > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2190758 > Commit-Queue: Clemens Backes <clemensb@chromium.org> > Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> > Cr-Commit-Position: refs/heads/master@{#67716} Bug: v8:10359 Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_isolates_rel_ng Change-Id: Ie98cf073fc79e5c6991df6d4466de7b560274070 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2194451 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
-
Jakob Gruber authored
Previously implemented directly in InterpreterAssembler::Construct, this will soon also be needed to implement a Construct_WithFeedback builtin. Bug: v8:8888 Change-Id: I01a00914c6554a5b83f414a93d85a15ec02df662 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2193717 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/master@{#67753}
-
Manos Koukoutos authored
Changes: - Implement subtyping for eqref. - (Driveby) Declare more functions as constexpr in ValueType. - Make minor changes needed to handle ref.eq. - Write an elementary test. Bug: v8:7748 Change-Id: I11d54227798ce56de70f3a6f83305b2f80b2f57f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2193715 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Milad Farazmand authored
This reverts commit 9d3cca1c. Reason for revert: Only the test needs to be skipped on s390. Refer to this: https://crrev.com/c/1981505 Original change's description: > s390: [arm] Add missing RELATIVE_CODE_TARGET iteration > > Port b766299d > Port 9592b043 > Port d915b8d6 > > Original Commit Message: > > Code object iteration was missing logic for RELATIVE_CODE_TARGET > reloc entries. Garbage collection could thus miss objects that were > referenced only as targets of pc-relative calls or jumps. > > RELATIVE_CODE_TARGETs are only used on arm, mips, and s390 and only > at mksnapshot-time. > > This exposed another issue in that the interpreter entry trampoline > copy we generate for profiling *did* contain relative calls in > runtime-accessible code. This is a problem, since code space on arm is, > by default, too large to be fully addressable through pc-relative > calls. This CL thus also disables the related > FLAG_interpreted_frames_native_stack feature on arm. > > objects. > > R=jgruber@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com > BUG= > LOG=N > > Change-Id: Ifbcaed98d90a2730f0d6a8a7d32c621dab1ff5b2 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2087693 > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Junliang Yan <jyan@ca.ibm.com> > Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> > Cr-Commit-Position: refs/heads/master@{#66644} TBR=michael_dawson@ca.ibm.com,mlippautz@chromium.org,jyan@ca.ibm.com,jgruber@chromium.org,joransiu@ca.ibm.com,miladfar@ca.ibm.com # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: Id645a9def23d278235ff77f25249d2187e8105ca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196521Reviewed-by:
Milad Farazmand <miladfar@ca.ibm.com> Reviewed-by:
-
Tobias Tebbi authored
- Change the Torque parser to support nested namespaces. All the rest of Torque has already supported them for a long time. - Use nested namespaces in ic-callable.tq and torque-internal.tq. Bug: v8:7793 Change-Id: I869ce21e4a6aeb5951815815cbd4feedfcb312b3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196127 Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
-
Milad Farazmand authored
Port b931af5d R=thibaudm@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: Idb61dd337187a8afd4e3b8705b80dab98eb11fa5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2195796Reviewed-by:
Junliang Yan <jyan@ca.ibm.com> Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#67749}
-
Tobias Tebbi authored
Bug: v8:7793 Change-Id: Id2a93f8ac8c512dbc5cdeb43a97e04d8d6684954 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196130 Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
-
Jakob Kummerow authored
in wasm-compiler.cc. Bug: v8:10506 Change-Id: I056344d64a58a53db46540f958dc4256243e0547 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196342 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
-
Mike Stanton authored
ScriptContextTableRef::lookup() isn't called. BUG=v8:7790 Change-Id: I8a89de2dff7b7e4ef7b37f54a0bd0fcae27d1a1d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196183 Commit-Queue: Michael Stanton <mvstanton@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#67746}
-
Jakob Kummerow authored
Bug: v8:7748 Change-Id: I736aaebb08be1d43662058f0ffde8b877b025017 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2193852Reviewed-by:
-
Omer Katz authored
This CL adds 2 new values to the EmbedderStackState enum with more explicit names. The old values are updated as aliases to the new values and marked as soon to be deprecated. This CL also moves the enum to v8-platform.h so that it can be reused by cppgc. Depracating individual values in an enum is supported by GCC only since version 6. Thus new macros were needed for the deprecation (which delegate to the existing macros when supported). GCC versions older than 6 are still used by the CQ bots. Bug: chromium:1056170 Change-Id: Id1ea73edfbbae282b0d8a3bb103dbbbf8ebd417e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2188971 Commit-Queue: Omer Katz <omerkatz@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#67744}
-
Leszek Swirski authored
This reverts commit 6fba287c. Reason for revert: Not the cause. Original change's description: > Revert "[heap] Refactor Heap::PerformGarbageCollection" > > This reverts commit d0dbee47. > > Reason for revert: Breaks MSVC bot (https://cr-buildbucket.appspot.com/build/8880517266974148704) > > Original change's description: > > [heap] Refactor Heap::PerformGarbageCollection > > > > This ensures that PerformGarbageCollection runs completely within a > > LocalHeap safepoint. External prologues and epilogues that may trigger > > GC and run JS are moved outside. > > > > Bug: v8:10315 > > > > Change-Id: I5c0081f0791ba5d27152c119a2a0d454056656d3 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2190756 > > Commit-Queue: Ulan Degenbaev <ulan@chromium.org> > > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#67736} > > TBR=ulan@chromium.org,mlippautz@chromium.org,dinfuehr@chromium.org > > Change-Id: I62e62d3f4cd50a3e8f0037902f158baef68cb3b1 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: v8:10315 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2195823 > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > Cr-Commit-Position: refs/heads/master@{#67739} TBR=ulan@chromium.org,mlippautz@chromium.org,leszeks@chromium.org,dinfuehr@chromium.org Bug: v8:10315 Change-Id: I8b9046c51fd43ca48066250085f589f6aa81d5f5 # Reland without changes. No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: I8b9046c51fd43ca48066250085f589f6aa81d5f5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196301 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Leszek Swirski authored
This reverts commit 3df36990. Reason for revert: Breaks MSVC bot (https://cr-buildbucket.appspot.com/build/8880517266974148704) Original change's description: > cppgc: Port ObjectStartBitmap > > This ports ObjectStartBitmap from Blink. > > Bug: chromium:1056170 > Change-Id: Ib959d9ac1c5e1e34ffa6418f77956e993c570ffc > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2181331 > Commit-Queue: Anton Bikineev <bikineev@chromium.org> > Reviewed-by: Omer Katz <omerkatz@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#67735} TBR=ulan@chromium.org,mlippautz@chromium.org,bikineev@chromium.org,omerkatz@chromium.org Change-Id: Iaea15b11c0ee7b599fe1f275aded7414bce428ac No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:1056170 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196321Reviewed-by:
-
Dominik Inführ authored
This is a reland of 7f29c48e After fixing TSAN failures in https://crrev.com/c/2192661 and https://crrev.com/c/2193712, this CL and be relanded without changes. Original change's description: > [heap] Remove sweeping state in incremental marking > > Remove the SWEEPING state from incremental marking. Sweeping is now > always completed when starting incremental marking. Before this change > there needed to be a safepoint each for starting marking and completing > sweeping. Now both happens within a single safepoint. > > Bug: v8:10315 > Change-Id: Iad2835554865f2de24376372affe9a98992d1fa0 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2190419 > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#67678} Bug: v8:10315 Change-Id: Ic949d125e72c4d17fd427d08d4b6f9056721eee9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196182Reviewed-by:
-
Thibaud Michaud authored
Multi-value "if" works out of the box in Liftoff. R=ahaas@chromium.org Bug: v8:10408 Change-Id: Ia3666ccd4faaa32f373020a3335a0304823f8881 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196123Reviewed-by:
-
Leszek Swirski authored
This reverts commit d0dbee47. Reason for revert: Breaks MSVC bot (https://cr-buildbucket.appspot.com/build/8880517266974148704) Original change's description: > [heap] Refactor Heap::PerformGarbageCollection > > This ensures that PerformGarbageCollection runs completely within a > LocalHeap safepoint. External prologues and epilogues that may trigger > GC and run JS are moved outside. > > Bug: v8:10315 > > Change-Id: I5c0081f0791ba5d27152c119a2a0d454056656d3 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2190756 > Commit-Queue: Ulan Degenbaev <ulan@chromium.org> > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#67736} TBR=ulan@chromium.org,mlippautz@chromium.org,dinfuehr@chromium.org Change-Id: I62e62d3f4cd50a3e8f0037902f158baef68cb3b1 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:10315 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2195823Reviewed-by:
-
Georg Neis authored
A prototype map can't be deprecated. Bug: v8:7790 Change-Id: I26ef4d9648985417212dcf4df0d47568861e9bc2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196124 Auto-Submit: Georg Neis <neis@chromium.org> Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Commit-Queue: Michael Stanton <mvstanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#67738}
-
Jakob Gruber authored
We don't yet support serialization of optimized code, so whenever the serializer encounters an 'unexpected' Code object, it aborts. Snapshot::ClearReconstructableDataForSerialization does not clear weak links created through compilation dependencies. These links make Code objects reachable even though recompilable data has been cleared from JSFunctions/SFIs/JSRegExps. Forcing a full deopt of the entire isolate is the simple of way of solving this until serialization support for optimized code has been implemented. Bug: v8:10416,v8:10500,v8:10518 Change-Id: Ie1386cc9fa983b435825afa15441df38409bff98 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2196122 Auto-Submit: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Ulan Degenbaev authored
This ensures that PerformGarbageCollection runs completely within a LocalHeap safepoint. External prologues and epilogues that may trigger GC and run JS are moved outside. Bug: v8:10315 Change-Id: I5c0081f0791ba5d27152c119a2a0d454056656d3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2190756 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
-
Anton Bikineev authored
This ports ObjectStartBitmap from Blink. Bug: chromium:1056170 Change-Id: Ib959d9ac1c5e1e34ffa6418f77956e993c570ffc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2181331 Commit-Queue: Anton Bikineev <bikineev@chromium.org> Reviewed-by:
Omer Katz <omerkatz@chromium.org> Reviewed-by:
-
Thibaud Michaud authored
R=clemensb@chromium.org,ahaas@chromium.org Bug: v8:10408 Change-Id: I436416e32d814b08543aa2dffbcf8464ec75923f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2190423 Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by:
-
Jakob Gruber authored
Prior to this CL we still implemented a HasProperty-GetProperty sequence when accessing named captures in GetSubstitution. This was briefly part of the spec (we also threw an exception when the property was not present), but since late 2017 the GetProperty call has been unconditional. See https://tc39.es/ecma262/#sec-getsubstitution. Bug: v8:10513 Change-Id: Id82c06958b0b0feffc6eede580b99ab8676a0dae Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2195821 Auto-Submit: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#67733}
-
Marja Hölttä authored
There's no need for them to be in NativeContext. This CL moves the rest of the Promise-related SFIs. Bug: v8:10482 Change-Id: I7eb926be14bf44fb3cd01cb96b4769eff1c2911b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2190752 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#67732}
-
Georg Neis authored
R=dinfuehr@chromium.org Bug: v8:10315 Change-Id: I595bc76907c9f0f437d460916aec804b55895376 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2195822Reviewed-by:
-
Pan, Tao authored
Add inlined bytecode size to candidate print, both bytecode size and inlined bytecode size decide whether candidate to be inlined. Change-Id: I6d659bb59819b0e9daad5289f47f329aa3ce9f7e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2191631Reviewed-by:
-
Ulan Degenbaev authored
Change-Id: I3d5d856d86deb283173c7b6f0f302e3c4e4b67fb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2190755 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
-
Dominik Inführ authored
Map::bit_field needs to be set with relaxed store. The concurrent marker accesses the has_prototype_slot bit in Map::bit_field to calculate header size. Bug: v8:10315 Change-Id: Ie7ebb9316b8c703adfddf10df25949b872ce0c8d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2194012Reviewed-by:
-
Ulan Degenbaev authored
This changes "v8[.gc],devtools.timeline" to "devtools.timeline,v8[.gc" in some of the GC trace events because perfetto requires all categories to be predefined. Change-Id: I0e9a91c826f4e620f4946a1a96713aa2b45da26f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2193591 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#67727}
-
Milad Farazmand authored
As discussed under https://crrev.com/c/1981505, Test requires an executable CODE_SPACE and is thus incompatible with jitless mode. Change-Id: Icddad50a3484f0cfc5fb4abd7175058d50bc06d3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2193911Reviewed-by:
-
