| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[debug][wasm] Fix GDB remote server compilation errors Fix compilation errors and test failures in the GDB remote server stub when enabled through v8_enable_wasm_gdb_remote_debugging. The GDB remote server stub has been broken for a long time due to V8 API changes. This patch addresses multiple issues: - Fix type conversions from internal Isolate* to v8::Isolate* - Update Handle to DirectHandle for WasmInstanceObject and WasmTrustedInstanceData - Fix WasmModuleObject API calls (module() -> native_module()->module()) - Add Zone/AccountingAllocator for more efficient memory management - Update include headers for changed APIs - Fix unit tests to work with current V8 codebase This enables native debuggers like GDB and LLDB to attach to V8 and debug WebAssembly modules when the GDB remote debugging flag is enabled. Bug: 433881953 Change-Id: Ib2d728b0e954d8701076a2ff07e59336794ddf82 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6785387 Reviewed-by: Paolo Severini <paolosev@microsoft.com> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#101856} | 10 个月前 | |
Add DIR_METADATA files to v8. Generate DIR_METADATA files and remove metadata from OWNERS files for v8. R=jkummerow@chromium.org, ochang@chromium.org, yangguo@chromium.org Bug: chromium:1113033 Change-Id: I82cbb62e438d82dbbc408e87120af39fa9da0afa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2476680 Reviewed-by: Adam Klein <adamk@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Auto-Submit: Edward Lesmes <ehmaldonado@chromium.org> Cr-Commit-Position: refs/heads/master@{#70669} | 5 年前 | |
[debug] Add jkummerow as wasm-* per-file OWNER Change-Id: I95254debdd49cb70324e61e33f7682b8cc3be2bf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6305342 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/main@{#98944} | 1 年前 | |
[wasm] Wasm code coverage: Support Liftoff Spec: https://docs.google.com/document/d/1NaD50lRija9DxHfb8X_rRlJ8EriqG_R20GM9E8Xf9ig/edit?pli=1&tab=t.0 This is the 2nd in a series of CLs to add support for WebAssembly code coverage in V8. This CL adds coverage instrumentation to Liftoff-compiled code. Bug: 354020953 Change-Id: Ib370f729fabe012148bd8ea955ff65d6934f8f4f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6541895 Reviewed-by: Jakob Linke <jgruber@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Daniel Lehmann <dlehmann@chromium.org> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Cr-Commit-Position: refs/heads/main@{#100667} | 1 年前 | |
[wasm] Wasm code coverage: Support Liftoff Spec: https://docs.google.com/document/d/1NaD50lRija9DxHfb8X_rRlJ8EriqG_R20GM9E8Xf9ig/edit?pli=1&tab=t.0 This is the 2nd in a series of CLs to add support for WebAssembly code coverage in V8. This CL adds coverage instrumentation to Liftoff-compiled code. Bug: 354020953 Change-Id: Ib370f729fabe012148bd8ea955ff65d6934f8f4f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6541895 Reviewed-by: Jakob Linke <jgruber@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Daniel Lehmann <dlehmann@chromium.org> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Cr-Commit-Position: refs/heads/main@{#100667} | 1 年前 | |
[temporal] Mark all Temporal methods as having no side-effects Followup from https://chromium-review.googlesource.com/c/v8/v8/+/7111926/4 Note that Temporal.Now stuff reads from system time, so it will change behavior, but it seems like Date() is marked as having no side effects so this is as well. Bug: 401065166 Change-Id: I8090d3da8cc95e26a8ae8d9e68e3f6526a6a6964 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7117353 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Manish Goregaokar <manishearth@google.com> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#103525} | 7 个月前 | |
[handles] Migration to direct handles, part 13 This CL migrates a large number of handles to direct handles. The changes are only relevant for builds with v8_enable_direct_handle=true. Affected source directories: api, ast, builtins, codegen, compiler, debug, deoptimizer, execution, heap, ic, init, interpreter, json, maglev, objects, parsing, regexp, runtime, snapshot, strings, temporal, wasm, and in tests. Bug: 42203211 Change-Id: Icb4238ee9082865dae47dce025e529a1c3fdfc48 Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6189992 Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> Reviewed-by: Omer Katz <omerkatz@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#98283} | 1 年前 | |
[runtime] Get rid of more GetIsolate calls Bug: 412408521 Change-Id: I0fbc5ac27c1f7b0304b4120681f534d80a29d08d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6480097 Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Auto-Submit: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#99869} | 1 年前 | |
Reland "[handles] Migration to direct handles, part 12" This is a reland of commit 5fa54d85a10049a55ba2fa02bc05145ddee7d19a Original change's description: > [handles] Migration to direct handles, part 12 > > This CL migrates a large number of handles to direct handles. The > changes are only relevant for builds with v8_enable_direct_handle=true. > > Affected source directories: api, asmjs, ast, builtins, codegen, > compiler, d8, debug, deoptimizer, diagnostics, execution, extensions, > heap, ic, init, interpreter, json, maglev, objects, parsing, profiler, > regexp, runtime, snapshot, strings, wasm, and tests. > > Bug: 42203211 > Change-Id: I2334b3295e5780e8f52d0b13d1545dce29fcf81e > Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6181904 > Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> > Reviewed-by: Omer Katz <omerkatz@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#98240} Bug: 42203211 Change-Id: Ie21acd681c12e7212185d61a19bd858365650204 Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6187462 Reviewed-by: Omer Katz <omerkatz@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Nikolaos Papaspyrou <nikolaos@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/main@{#98249} | 1 年前 | |
[hole] Remove unneeded hole value checks Undo a bunch of work which added by-value hole checks. Originally we wanted to make holes fully unmapped, including their map pointer, so that potential hole values would have to be checked by pointer value rather than map checks. This turned out to be tricky, partially because the optimizing compiler could hoist map reads above hole checks, and partially because the extra hole value checks ended up with performance regressions. In https://crrev.com/c/7156717 we switched to keeping the holes' maps mapped with an unmapped payload after the map (very similar approach to the WasmNull). This means that all those hole checks we added are now unnecessary, since they were already covered by the existing map-based checks. We can also remove the --assert-hole-checked-by-value flag and fuzzing, since this is no longer an invariant we want to preserve. Bug: 434179415 Change-Id: I9399498d89592127e4291b8acffee83a3ba70052 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7206087 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#103982} | 7 个月前 | |
[debug] Put Debugger.setScriptSource behind a feature flag We plan to deprecate and remove the live edit functionality. This CL puts the feature behind a flag that'll cause Debugger.setScriptSource to fail with a ServerError in case the flag is disabled. The CL also updates all affected tests to specifically enable the feature. Drive-by: Make the runtime function go through Debug::SetScriptSource so also the tests in test/debugger honor the flag. R=bmeurer@chromium.org Bug: 434574729 Change-Id: Idd8b57ef67258c4946e66028b3df8427ce89b8da Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6929582 Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/main@{#102348} | 9 个月前 | |
Avoid many HeapObject::GetIsolate calls Replace them by Isolate::Current. This change was created via this script: ag -l -- '->GetIsolate()' src/ | xargs -L1 sed -i -E 's/^(.*) = .*->GetIsolate\(\)/\1 = Isolate::Current()/g' followed by manual changes to undo large parts of the changes in src/inspector and src/d8 (which work on the public API need to be changed differently), and fix remaining issues (adding "i::" prefixes, using "v8::Isolate::GetCurrent()" instead of "i::Isolate::Current()" where needed etc). R=leszeks@chromium.org Bug: 396607238 Change-Id: If56423eb073ba726de7f5aa1b7eb2994d6fa5e4c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6495413 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#100093} | 1 年前 | |
[handles] Migration to direct handles, part 7 This CL migrates a large number of handles to direct handles. The changes are only relevant for builds with v8_enable_direct_handle=true. Affected source directories: api, builtins, numbers, objects, runtime (primarily) and also: codegen, debug, execution, heap, ic, logging, wasm (secondarily). Bug: 42203211 Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg Change-Id: I4c2d7057d4f552fd83bb4cb606b777c7001fbcfe Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6048824 Reviewed-by: Omer Katz <omerkatz@chromium.org> Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#97528} | 1 年前 | |
[handles] Migration to direct handles, part 9 This CL migrates a large number of handles to direct handles. The changes are only relevant for builds with v8_enable_direct_handle=true. Affected source directories: api, builtins, codegen, compiler, d8, debug, deoptimizer, execution, extensions, handles, heap, ic, init, interpreter, json, logging, maglev, objects, parsing, profiler, regexp, runtime, snapshot, wasm. Bug: 42203211 Change-Id: I829596e6b03bd17665906827c313591c065093fa Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6089071 Reviewed-by: Omer Katz <omerkatz@chromium.org> Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#97709} | 1 年前 | |
[handles] Migration to direct handles, part 1 This CL migrates a large number of handles to direct handles. The changes are only relevant for builds with v8_enable_direct_handle=true. Affected source directories: api, builtins, debug, deoptimizer, execution, objects, utils, wasm. Bug: 42203211 Change-Id: Ic8422835c8e4db849084071fb124b03b2bc34f25 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5601391 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Omer Katz <omerkatz@chromium.org> Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> Cr-Commit-Position: refs/heads/main@{#94285} | 2 年前 | |
[isolate] Stronger types for compilation cache table Bug: 434179415, 42202654 Change-Id: I33ae056f499a19874fe9714110e9d29283fe4bb0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6845796 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#101984} | 10 个月前 | |
[debug] Fix crash when pausing in for-of loop header Given a for-of loop: for (const each of subject) { The bytecode generator emits the iterator.next call + done check + assigning to each all into the source position of const each. The pseudo-desugared code looks something like: var tmp; loop { var result = iterator.next(); if (result.done) break; tmp = result.value; PushBlockContext; const each = tmp; // rest of the loop. } This is a problem, as the parser starts the block scope already on the const each. If the scope requires a context we can pause on bytecode that has or has not pushed the block context yet, while the source position looks the same. The recent addition of per-script unique scope IDs lets us fix this problem in the debugger: We can check if the scope ID of the runtime scope matches the parser scope. If not, the context was not pushed yet. The debugger already has a HasContext helper. We extend it to also check for matching scope IDs and then use HasContext where we would read variable values off the context. If the context was not pushed yet, we report them as 'unavailable'. R=leszeks@chromium.org Fixed: 384413079,399002824 Change-Id: Ia2d0008d574e7eaf6c06b640053df696014d37f8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6507402 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/main@{#100029} | 1 年前 | |
Reland "[contexts] Unify context accessors after ContextCells" This is a reland of commit d2ab66c2a942893b9f6d7628ff8892e1d6a607b3 Changes from original: - The test inspector/debugger/set-breakpoint-after-gc relies on precise garbage collection and may fail if conservative stack scanning is used. We call GC multiple times to ensure the weak reference hold by the script is eventually collected. - Allow reading a ContextCell when printing debug stack frame. Original change's description: > [contexts] Unify context accessors after ContextCells > > The introduction of ContextCells removed the need for special handling > for ScriptContext (which previously used a side table for > let/const tracking and mutable numbers). > > This change refactors the context access logic: > - Internal get/set accessors are now protected to the Context class. > - External access should use the new functions: > - Get/Set: A safe (though potentially slower) > function for accessing elements in any context. > - GetNoCell/SetNoCell: A faster function that verifies the > element being accessed is not a ContextCell. > > Additionally, related bytecode operations and optimizer functions have > been renamed for consistency with these changes. > > Bug: 408128754 > > Change-Id: I785281ab6f13b0ae65578eb5d2f0a5750457ab5e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6450582 > Reviewed-by: Igor Sheludko <ishell@chromium.org> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Commit-Queue: Victor Gomes <victorgomes@chromium.org> > Cr-Commit-Position: refs/heads/main@{#99844} Bug: 408128754, 40789559 Change-Id: I78a3a99a4f364ed78965fbed56a084d38382d2fc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6479814 Reviewed-by: Igor Sheludko <ishell@chromium.org> Auto-Submit: Victor Gomes <victorgomes@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#99865} | 1 年前 | |
Report function location on wasm callframes When paused, previously only the function location for javascript function was reported. We can do the same for wasm. This allows the debugger to detect when leaving the function, which is a stop condition for autostepping Bug: chromium:1418938 Change-Id: Ie2dd47e4ea106bc7475e3c488c201e88520277b8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4341657 Commit-Queue: Kim-Anh Tran <kimanh@chromium.org> Reviewed-by: Kim-Anh Tran <kimanh@chromium.org> Auto-Submit: Philip Pfaffe <pfaffe@chromium.org> Cr-Commit-Position: refs/heads/main@{#86488} | 3 年前 | |
[cleanup] Fix inl header includes We have many inl headers which either do not include their non-inl header, or are including other headers first. Both can lead to compile errors because definitions of inline functions might not be visible in inl headers. This CL adds a script to fix those includes, and runs it over the whole code base. R=leszeks@chromium.org Change-Id: I1b7b04c59e5a5b89308512bfc40729f7ec4afc38 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6387805 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#99453} | 1 年前 | |
[inspector] Do not use receiver in Wasm related inspector interceptor ... since access to receiver from both native data property and interceptor callbacks (i.e. v8::PropertyCallbackInfo<T>::This()) will be deprecated soon. This CL moves interceptor from ContextProxy's prototype to the ContextProxy object itself in order to be able to replace usage of This() with HolderV2(). No behavioral change expected besides shorter prototype chain and inability to pass arbitrary receivers to the callback. Bug: 455600234 Change-Id: Ifeab58baa58df5092a5133fb85ca71c69a339a3e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7095686 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/main@{#103406} | 8 个月前 | |
Include guards should be at the top of files. For the include guard optimization to kick in the include guards should be the first thing in the file, not counting comments. In some cases the guard has been moved above a comment for consistency even though this does not matter. A couple of include guards have been renamed for uniqueness. git cl upload complained about some lint nits which have been fixed. Change-Id: Iaa208ea6557c36c84bc7bb77c787ba9feb7cf037 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6275067 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Erik Corry <erikcorry@chromium.org> Cr-Commit-Position: refs/heads/main@{#98907} | 1 年前 | |
[inspector][wasm] Re-add WasmValue as JSObject subclass. BREAKING CHANGE: The values of Wasm locals, stack, and globals are now represented as objects instead of holding the (primitive) values directly, and SIMD128 values are no longer represented as Uint8Arrays. The DWARF extension has been prepared for this breaking change. The new WasmValue comes with type and value properties that hold its contents. The motivation here is that this is a more extensible approach. In case of SIMD128, the value property holds the canonical string representation, which has the additional advantage that these values can be compared with === (and ==). This partially reverts https://crrev.com/c/2614428, the main difference here being that WasmValue is now a proper JSObject that can be exposed on the DebugEvaluate proxy API. Screenshot: https://imgur.com/rcahNKM.png Bug: chromium:1170282, chromium:1071432, chromium:1159402 Change-Id: Iea304e3680775123c41deb4c3d172ac949da1b98 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2643384 Reviewed-by: Philip Pfaffe <pfaffe@chromium.org> Reviewed-by: Zhi An Ng <zhin@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#72570} | 5 年前 | |
2026.03.30 arkweb_144代码蓝黄同步 Signed-off-by: jiujiaoxiaogula <sujiahao10@huawei.com> Change-Id: I00194d339064f999dedfc211cd5af5501cbed0fb | 3 个月前 | |
Remove last uses of GetIsolate and GetHeap This is the manual follow-up to the mostly automatic https://crrev.com/c/6495413. Those methods will be removed in a follow-up (https://crrev.com/c/6582963). Depending on what makes most sense, we either use Isolate::Current() directly, or store it in a variable that is reused multiple times, or we pass the isolate as a parameter. R=leszeks@chromium.org Bug: 396607238 Change-Id: I9366410849cd4fa39fb792db9bb2ad35dba86ffe Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6582961 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#100468} | 1 年前 | |
Fix random presubmit warnings Those were flushed out in https://crrev.com/c/6582961. R=leszeks@chromium.org Change-Id: I97024c19a4211c3057ae36ee5c6585996b14e42a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6579374 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#100471} | 1 年前 | |
Reland "[handles] Migration to direct handles, part 12" This is a reland of commit 5fa54d85a10049a55ba2fa02bc05145ddee7d19a Original change's description: > [handles] Migration to direct handles, part 12 > > This CL migrates a large number of handles to direct handles. The > changes are only relevant for builds with v8_enable_direct_handle=true. > > Affected source directories: api, asmjs, ast, builtins, codegen, > compiler, d8, debug, deoptimizer, diagnostics, execution, extensions, > heap, ic, init, interpreter, json, maglev, objects, parsing, profiler, > regexp, runtime, snapshot, strings, wasm, and tests. > > Bug: 42203211 > Change-Id: I2334b3295e5780e8f52d0b13d1545dce29fcf81e > Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6181904 > Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> > Reviewed-by: Omer Katz <omerkatz@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#98240} Bug: 42203211 Change-Id: Ie21acd681c12e7212185d61a19bd858365650204 Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6187462 Reviewed-by: Omer Katz <omerkatz@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Nikolaos Papaspyrou <nikolaos@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/main@{#98249} | 1 年前 | |
[liveedit] Remove dynamic programming diffing implementation Myers algorithm for live edit diffing has been enabled since 10.6 without any reported problems, so we can safely remove the dynamic programming approach with 10.8. R=kimanh@chromium.org Bug: chromium:1205288 Change-Id: I95c26c11e949b8c36a0b6abd54859b3936933e9d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3901811 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Kim-Anh Tran <kimanh@chromium.org> Cr-Commit-Position: refs/heads/main@{#83240} | 3 年前 | |
[cleanup] Remove leaptiering ifdefs from tiering Bug: 42204201 Change-Id: I10d7765fd38e58c48633d0cc659dcf0c1918787a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6994660 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Cr-Commit-Position: refs/heads/main@{#102830} | 9 个月前 | |
[debug] Allow live-editing of top-most frame This CL extends the live edit mechanism to allow editing the function that is currently on top of the stack, as long as that call frame is the only activation of that function. The CL changes how we look for functions on the current JS stack: Instead of starting at thread_local_top we start at the frame we are currently paused in. This is possible since there can not be any JavaScript frames above the current "break frame", only C++ frames which are not relevant for live edit. If the edited script modifes the top-most function, the inspector will trigger a restart of that call frame. That is why we check if we can actually restart the function and only allow the live edit to go through if that is the case. Note that this CL also adds a kill switch in the form of a runtime flag for this feature, in case we need to pull the plug and disable this feature again via back-merge. R=jarin@chromium.org Bug: chromium:1334484 Change-Id: I711913df96c8acc786ad4de28de804d2f90e1847 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3695353 Reviewed-by: Kim-Anh Tran <kimanh@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/main@{#81097} | 3 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 10 个月前 | ||
| 5 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 7 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 7 个月前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 10 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 1 年前 | ||
| 8 个月前 | ||
| 1 年前 | ||
| 5 年前 | ||
| 3 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 9 个月前 | ||
| 3 年前 |