| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[turbolev] rename turboshaft_maglev_frontend to turbolev Bug: chromium:42204525 Change-Id: I36897a3cbcdb055b221deb56aa4d8cdd8483cf79 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6170992 Auto-Submit: Darius Mercadier <dmercadier@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Darius Mercadier <dmercadier@chromium.org> Cr-Commit-Position: refs/heads/main@{#98074} | 1 年前 | |
[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 个月前 | |
[tests] Remove mentions of --no-always-turbofan Bug: 431974094 Change-Id: I065cfcb8e0639b1a4b7b0c2c28beb6d217bbcb71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6780589 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101613} | 11 个月前 | |
[debugger] materialize scope values in TDZ as undefined. R=szuend@chromium.org Fixes: chromium:718827 Change-Id: I261ce2cf692b5bcf88f4f7f67249ec49c837de4e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2241521 Reviewed-by: Simon Zünd <szuend@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#68337} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[tests] Remove mentions of --no-always-turbofan Bug: 431974094 Change-Id: I065cfcb8e0639b1a4b7b0c2c28beb6d217bbcb71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6780589 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101613} | 11 个月前 | |
[temporal] Remove --harmony-temporal from non-Temporal tests In https://chromium-review.googlesource.com/c/v8/v8/+/7111926 I added --harmony-temporal to some tests to ensure they still pass with Temporal enabled. However, they are not Temporal tests; they should not be enabling this flag long term. Now that Temporal is unflagged (https://chromium-review.googlesource.com/c/v8/v8/+/7123876), this can be removed. Bug: 401065166 Change-Id: I00a7f7d585670bd0ddc10501931add682e803cfc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7124594 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Manish Goregaokar <manishearth@google.com> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#103562} | 7 个月前 | |
[wasm] Allow for-debugging code with Turbofan This is an exceptional case, and the code won't work for debugging, but we need to allow Turbofan to produce for_debugging code. R=mliedtke@chromium.org Fixed: 377971725 Change-Id: I8e6414e3472270df81bc13b4b00e60f79ed9a8d1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6014494 Reviewed-by: Matthias Liedtke <mliedtke@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#97158} | 1 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[tests] Fix assertFalse(exception) anti-pattern Some debugging tests relied on the following anti-pattern: let exception = false; try { /* ... some code that may throw on test failure ... */ } catch (e) { exception = e; } assertFalse(exception); This may be problematic if a falseish value is thrown. Change-Id: I02eace4cc656fc9581928a90ac53cda4dc72b30c Reviewed-on: https://chromium-review.googlesource.com/972822 Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#52105} | 8 年前 | |
Remove always-true --harmony-bigint runtime flag It was shipped in Chrome 67. Bug: v8:6791, v8:8238 Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;luci.v8.try:v8_linux_noi18n_rel_ng;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I94d8f0aa18570452403a35dea270b18f155c970a Reviewed-on: https://chromium-review.googlesource.com/1253604 Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#56310} | 7 年前 | |
[parser] Only reparse the relevant segments for class initializers This changes the source positions for static elements and instance members initializer functions to only cover exactly the region of a class they need. ParseClassLiteralBody is changed to only parse body statements, not everything starting from { to }. And class literal rewriting is moved outside to where the class literal is parsed, so that initializer functions can only do the bits that they need. The entire outer scope chain is always deserialized, and is used as the scope for parsing. Private variables and variables for computed field names are allowed to be created on the scope despite already being resolved. FinalizeReparsedClassScope is repurposed to properly initialize those variables after we finished parsing the class body. Change-Id: I87d10bc633dee40b99437af87d600fe06d711afc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5676330 Reviewed-by: Igor Sheludko <ishell@chromium.org> Auto-Submit: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#94853} | 1 年前 | |
[Test] Add PrepareForOptimization to debugger/ tests. BUG=v8:8801 Change-Id: Id5ef6219ba2dca2be0603dd0d45e7b27136836e9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1587391 Reviewed-by: Mythri Alle <mythria@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#61085} | 7 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug] removed most debugger js Removed most of mirrors.js and debug.js. Further steps: - migrate liveedit.js to native, - remove debugger context. R=yangguo@chromium.org TBR=leszeks@chromium.org Bug: v8:5530 Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I291ef20ef3c63a424d32e3e0c9d0962a6ca382d1 Reviewed-on: https://chromium-review.googlesource.com/1081176 Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#53480} | 7 年前 | |
[debug-wrapper] Further extend the debug wrapper This CL further extends the debug wrapper, migrates around 60 tests, and removes a few tests that use functionality we will not support anymore. In more detail: * Removed tests that use: * enable/disable individual breakpoints * invocationText() * the ScriptCollected event * showBreakPoints * evalFromScript (and similar) * mirror.constructedBy and mirror.referencedBy * event_data.promise() * Some frame.evaluate uses were adapted since due to differences between remote objects (inspector) and mirrors. For instance, exceptions are currently not recreated exactly, since the inspector protocol does not give us the stack and message separately. Other objects (such as 'this' in debug-evaluate-receiver-before-super) need to be explicitly converted to a string before the test works correctly. * Ensure that inspector stores the script before sending ScriptParsed and ScriptFailedToParse events in order to be able to use the script from within those events. * Better remote object reconstruction (e.g. for undefined and arrays). * New functionality in wrapper: * debuggerFlags().breakPointsActive.setValue() * scripts() * execState.setVariableValue() * execState.scopeObject().value() * execState.scopeObject().property() * execState.frame().allScopes() * eventData.exception() * eventData.script() * setBreakPointsActive() BUG=v8:5530 Review-Url: https://codereview.chromium.org/2497973002 Cr-Commit-Position: refs/heads/master@{#41019} | 9 年前 | |
[tests] Fix assertFalse(exception) anti-pattern Some debugging tests relied on the following anti-pattern: let exception = false; try { /* ... some code that may throw on test failure ... */ } catch (e) { exception = e; } assertFalse(exception); This may be problematic if a falseish value is thrown. Change-Id: I02eace4cc656fc9581928a90ac53cda4dc72b30c Reviewed-on: https://chromium-review.googlesource.com/972822 Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#52105} | 8 年前 | |
[tests] Fix assertFalse(exception) anti-pattern Some debugging tests relied on the following anti-pattern: let exception = false; try { /* ... some code that may throw on test failure ... */ } catch (e) { exception = e; } assertFalse(exception); This may be problematic if a falseish value is thrown. Change-Id: I02eace4cc656fc9581928a90ac53cda4dc72b30c Reviewed-on: https://chromium-review.googlesource.com/972822 Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#52105} | 8 年前 | |
[tests] Remove mentions of --no-always-turbofan Bug: 431974094 Change-Id: I065cfcb8e0639b1a4b7b0c2c28beb6d217bbcb71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6780589 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101613} | 11 个月前 | |
[debug-wrapper] Migrate more tests * Fix setting script-scope variables through inspector by internalizing their names. * Reconstruct values of Number, String, and Boolean classes. * Adapt a couple of tests for API restrictions. BUG=v8:5530 Review-Url: https://codereview.chromium.org/2512963002 Cr-Commit-Position: refs/heads/master@{#41175} | 9 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug-wrapper] Further extend the debug wrapper This CL further extends the debug wrapper, migrates around 60 tests, and removes a few tests that use functionality we will not support anymore. In more detail: * Removed tests that use: * enable/disable individual breakpoints * invocationText() * the ScriptCollected event * showBreakPoints * evalFromScript (and similar) * mirror.constructedBy and mirror.referencedBy * event_data.promise() * Some frame.evaluate uses were adapted since due to differences between remote objects (inspector) and mirrors. For instance, exceptions are currently not recreated exactly, since the inspector protocol does not give us the stack and message separately. Other objects (such as 'this' in debug-evaluate-receiver-before-super) need to be explicitly converted to a string before the test works correctly. * Ensure that inspector stores the script before sending ScriptParsed and ScriptFailedToParse events in order to be able to use the script from within those events. * Better remote object reconstruction (e.g. for undefined and arrays). * New functionality in wrapper: * debuggerFlags().breakPointsActive.setValue() * scripts() * execState.setVariableValue() * execState.scopeObject().value() * execState.scopeObject().property() * execState.frame().allScopes() * eventData.exception() * eventData.script() * setBreakPointsActive() BUG=v8:5530 Review-Url: https://codereview.chromium.org/2497973002 Cr-Commit-Position: refs/heads/master@{#41019} | 9 年前 | |
[tests] Remove mentions of --no-always-turbofan Bug: 431974094 Change-Id: I065cfcb8e0639b1a4b7b0c2c28beb6d217bbcb71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6780589 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101613} | 11 个月前 | |
[Test] Add PrepareForOptimization to debugger/ tests. BUG=v8:8801 Change-Id: Id5ef6219ba2dca2be0603dd0d45e7b27136836e9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1587391 Reviewed-by: Mythri Alle <mythria@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#61085} | 7 年前 | |
[tests] Fix assertFalse(exception) anti-pattern Some debugging tests relied on the following anti-pattern: let exception = false; try { /* ... some code that may throw on test failure ... */ } catch (e) { exception = e; } assertFalse(exception); This may be problematic if a falseish value is thrown. Change-Id: I02eace4cc656fc9581928a90ac53cda4dc72b30c Reviewed-on: https://chromium-review.googlesource.com/972822 Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#52105} | 8 年前 | |
[tests] Remove mentions of --no-always-turbofan Bug: 431974094 Change-Id: I065cfcb8e0639b1a4b7b0c2c28beb6d217bbcb71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6780589 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101613} | 11 个月前 | |
[tests] Remove mentions of --no-always-turbofan Bug: 431974094 Change-Id: I065cfcb8e0639b1a4b7b0c2c28beb6d217bbcb71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6780589 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101613} | 11 个月前 | |
[debug-wrapper] Conditional breaks, locals, evaluate, scopes This CL adds support for: * conditional breaks in setBreakpoint, * locals in frame.local{Count,Name,Value}, * evaluation on a frame in frame.evaluate, * and more detailed scope information in scopeObject. Uses of several functions that are not covered by the inspector protocol and are only used in tests have been removed. Local handling has been modified to also include arguments as locals. Inspector differs in this regard from our FrameDetails in that arguments are always shown as locals. Argument-related functions were removed. BUG=v8:5530 Review-Url: https://codereview.chromium.org/2491543002 Cr-Commit-Position: refs/heads/master@{#40917} | 9 年前 | |
Reland "[debugger] Expose reference to the function in debug-evaluate" This is a reland of 8de427fae840406cafd2cd5fd80b83a21a1b6fc2 Original change's description: > [debugger] Expose reference to the function in debug-evaluate > > R=verwaest@chromium.org > > Bug: chromium:878723 > Change-Id: Ic07f75f15230018b6d19cd1ee21f4be6dcad6360 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1667408 > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Commit-Queue: Yang Guo <yangguo@chromium.org> > Cr-Commit-Position: refs/heads/master@{#62385} TBR=jgruber@chromium.org Bug: chromium:878723 Change-Id: I0386655a9b2632d2d9438e674d4205ce5e5365f5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1679490 Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#62401} | 6 年前 | |
Introduce REPL mode Design doc: bit.ly/v8-repl-mode This CL adds a new REPL mode that can be used via DebugEvaluate::GlobalREPL. REPL mode only implements re-declaration of 'let' bindings at the moment. Example: REPL Input 1: let x = 21; REPL Input 2: let x = 42; This would normally throw a SyntaxError, but works in REPL mode. The implementation is done by: - Setting a 'repl mode' bit on {Script}, {ScopeInfo}, {ParseInfo} and script {Scope}. - Each global let declaration still gets a slot reserved in the respective {ScriptContext}. - When a new REPL mode {ScriptContext} is created, name clashes for let bindings are not reported as errors. - Declarations, loads and stores for global let in REPL mode are now "load/store global" instead of accessing their respective context slot directly. This causes a lookup in the ScriptContextTable where the found slot for each name is guaranteed to be the same (the first one). Bug: chromium:1004193, chromium:1018158 Change-Id: Ia6ab526b9f696400dbb8bfb611a4d43606119a47 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1876061 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#64793} | 6 年前 | |
[tests] Remove mentions of --no-always-turbofan Bug: 431974094 Change-Id: I065cfcb8e0639b1a4b7b0c2c28beb6d217bbcb71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6780589 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101613} | 11 个月前 | |
[Test] Add PrepareForOptimization to debugger/ tests. BUG=v8:8801 Change-Id: Id5ef6219ba2dca2be0603dd0d45e7b27136836e9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1587391 Reviewed-by: Mythri Alle <mythria@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#61085} | 7 年前 | |
[Test] Add PrepareForOptimization to debugger/ tests. BUG=v8:8801 Change-Id: Id5ef6219ba2dca2be0603dd0d45e7b27136836e9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1587391 Reviewed-by: Mythri Alle <mythria@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#61085} | 7 年前 | |
[tests] Fix assertFalse(exception) anti-pattern Some debugging tests relied on the following anti-pattern: let exception = false; try { /* ... some code that may throw on test failure ... */ } catch (e) { exception = e; } assertFalse(exception); This may be problematic if a falseish value is thrown. Change-Id: I02eace4cc656fc9581928a90ac53cda4dc72b30c Reviewed-on: https://chromium-review.googlesource.com/972822 Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#52105} | 8 年前 | |
[tests] Remove mentions of --no-always-turbofan Bug: 431974094 Change-Id: I065cfcb8e0639b1a4b7b0c2c28beb6d217bbcb71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6780589 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101613} | 11 个月前 | |
[debugger] Further stepping support in test wrapper This CL adds further support to the test wrapper. We are now able to run almost all mjsunit/debug-step-* tests using the inspector backend. debug-stepframe-* tests are not yet supported since inspector does not know a 'frame' step type. The interface has also been improved to be able to move these tests to inspector mostly without modification. BUG=v8:5330 Review-Url: https://codereview.chromium.org/2466273005 Cr-Commit-Position: refs/heads/master@{#40800} | 9 年前 | |
[flags] Rename --opt to --turbofan 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/+/3610431 Reviewed-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} | 4 年前 | |
Reland "Implement top-level await for REPL mode" This is a reland of 5bddc0e1429dd5885462c26a5082097766776d37 The original CL was speculatively reverted as it was suspected to cause failures on the non-determinism bot. This was ultimately confirmed to not be the case, so this CL is safe to reland as-is. Original change's description: > Implement top-level await for REPL mode > > Design doc: bit.ly/v8-repl-mode > > This CL allows the usage of 'await' without wrapping code in an async > function when using REPL mode in global evaluate. REPL mode evaluate > is changed to *always* return a Promise. The resolve value of the > promise is the completion value of the REPL script. > > The implementation is based on two existing mechanisms: > - Similar to async functions, the content of a REPL script is > enclosed in a synthetic 'try' block. Any thrown error > is used to reject the Promise of the REPL script. > > - The content of the synthetic 'try' block is also re-written the > same way a normal script is. This is, artificial assignments to > a ".result" variable are inserted to simulate a completion > value. The difference for REPL scripts is, that ".result" is > used to resolve the Promise of the REPL script. > > - ".result" is not returned directly but wrapped in an object > literal: "{ .repl_result: .result}". This is done to prevent > resolved promises from being chained and resolved prematurely: > > > Promse.resolve(42); > > should evaluate to a promise, not 42. > > Bug: chromium:1021921 > Change-Id: I00a5aafd9126ca7c97d09cd8787a3aec2821a67f > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1900464 > Reviewed-by: Yang Guo <yangguo@chromium.org> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Simon Zünd <szuend@chromium.org> > Cr-Commit-Position: refs/heads/master@{#65273} TBR: yangguo@chromium.org,verwaest@chromium.org Bug: chromium:1021921 Change-Id: I95c5dc17593161009a533188f91b4cd67234c32f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1954388 Reviewed-by: Simon Zünd <szuend@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#65360} | 6 年前 | |
[flags] Rename --opt to --turbofan 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/+/3610431 Reviewed-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} | 4 年前 | |
Adding support for const redeclaration on REPL mode. This change adds support for const redeclaration on REPL mode with the semantincs recommended in the design doc: 1) REPL scripts should not be able to reassign bindings to const variables. 2) Re-declaring const variables of page scripts is not allowed in REPL scripts. 3) Re-declearing const variables is not allowed in the same REPL script. 4) const re-declaration is allowed across separate REPL scripts. 5) Old references to previously declared variables get updated with the new value, even those references from within optimized functions. Design doc: https://goo.gle/devtools-const-repl Bug: chromium:1076427 Change-Id: Ic73d2ae7fcfbfc1f5b58f61e0c3c69e9c4d85d77 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2865721 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Mythri Alle <mythria@chromium.org> Commit-Queue: Luis Fernando Pardo Sixtos <lpardosixtos@microsoft.com> Cr-Commit-Position: refs/heads/master@{#74510} | 5 年前 | |
[spelling] Re-use to reuse Change-Id: I9ee5130dd2b7f778c85210090f9ce3fb2ef233ca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6191011 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#98304} | 1 年前 | |
[spelling] Re-use to reuse Change-Id: I9ee5130dd2b7f778c85210090f9ce3fb2ef233ca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6191011 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#98304} | 1 年前 | |
[tests] Fix assertFalse(exception) anti-pattern Some debugging tests relied on the following anti-pattern: let exception = false; try { /* ... some code that may throw on test failure ... */ } catch (e) { exception = e; } assertFalse(exception); This may be problematic if a falseish value is thrown. Change-Id: I02eace4cc656fc9581928a90ac53cda4dc72b30c Reviewed-on: https://chromium-review.googlesource.com/972822 Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#52105} | 8 年前 | |
[tests] Fix assertFalse(exception) anti-pattern Some debugging tests relied on the following anti-pattern: let exception = false; try { /* ... some code that may throw on test failure ... */ } catch (e) { exception = e; } assertFalse(exception); This may be problematic if a falseish value is thrown. Change-Id: I02eace4cc656fc9581928a90ac53cda4dc72b30c Reviewed-on: https://chromium-review.googlesource.com/972822 Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#52105} | 8 年前 | |
[debug-wrapper] Add caught/uncaught to exception pauses BUG=v8:5530 Review-Url: https://codereview.chromium.org/2480293009 Cr-Commit-Position: refs/heads/master@{#40877} | 9 年前 | |
[debug-wrapper] Add caught/uncaught to exception pauses BUG=v8:5530 Review-Url: https://codereview.chromium.org/2480293009 Cr-Commit-Position: refs/heads/master@{#40877} | 9 年前 | |
[debug-wrapper] Migrate more tests * Fix setting script-scope variables through inspector by internalizing their names. * Reconstruct values of Number, String, and Boolean classes. * Adapt a couple of tests for API restrictions. BUG=v8:5530 Review-Url: https://codereview.chromium.org/2512963002 Cr-Commit-Position: refs/heads/master@{#41175} | 9 年前 | |
[debugger] Further stepping support in test wrapper This CL adds further support to the test wrapper. We are now able to run almost all mjsunit/debug-step-* tests using the inspector backend. debug-stepframe-* tests are not yet supported since inspector does not know a 'frame' step type. The interface has also been improved to be able to move these tests to inspector mostly without modification. BUG=v8:5330 Review-Url: https://codereview.chromium.org/2466273005 Cr-Commit-Position: refs/heads/master@{#40800} | 9 年前 | |
[debugger] Further stepping support in test wrapper This CL adds further support to the test wrapper. We are now able to run almost all mjsunit/debug-step-* tests using the inspector backend. debug-stepframe-* tests are not yet supported since inspector does not know a 'frame' step type. The interface has also been improved to be able to move these tests to inspector mostly without modification. BUG=v8:5330 Review-Url: https://codereview.chromium.org/2466273005 Cr-Commit-Position: refs/heads/master@{#40800} | 9 年前 | |
[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 个月前 | |
[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 个月前 | |
[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 个月前 | |
[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 个月前 | |
[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 个月前 | |
[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 个月前 | |
[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 个月前 | |
[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 个月前 | |
[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 个月前 | |
[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 个月前 | |
[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 个月前 | |
[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 个月前 | |
[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 个月前 | |
Reland "[debug] Remove 'value unavailble' experiment" This is a reland of commit c7cbb4139bc5e7dc352fd9fd69fc9ac9ff7f4fc2 Relanding as is. Was reverted due to a test failure that turned out to be a flake that still reproduced after the revert landed. Flako run: https://ci.chromium.org/ui/p/v8/builders/try.triggered/v8_flako/b8758034788224082417/overview Original change's description: > [debug] Remove 'value unavailble' experiment > > The experiment was enabled in July 2023 and we haven't heard any > negative feedback so we can safely remove the experiment now. > > R=bmeurer@chromium.org > > Bug: chromium:1328681 > Change-Id: I6613a4e8e741d8c16881ec1adeb01e039244fac7 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5224284 > Commit-Queue: Simon Zünd <szuend@chromium.org> > Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> > Cr-Commit-Position: refs/heads/main@{#91968} Bug: chromium:1328681 Change-Id: I651e2a20c6612fc138246aa7e61daab285b57795 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5233640 Commit-Queue: Simon Zünd <szuend@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Simon Zünd <szuend@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#91978} | 2 年前 | |
[tests] Remove mentions of --no-always-turbofan Bug: 431974094 Change-Id: I065cfcb8e0639b1a4b7b0c2c28beb6d217bbcb71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6780589 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101613} | 11 个月前 | |
[debug-wrapper] Migrate more tests * Fix setting script-scope variables through inspector by internalizing their names. * Reconstruct values of Number, String, and Boolean classes. * Adapt a couple of tests for API restrictions. BUG=v8:5530 Review-Url: https://codereview.chromium.org/2512963002 Cr-Commit-Position: refs/heads/master@{#41175} | 9 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug-wrapper] Migrate more tests * Fix setting script-scope variables through inspector by internalizing their names. * Reconstruct values of Number, String, and Boolean classes. * Adapt a couple of tests for API restrictions. BUG=v8:5530 Review-Url: https://codereview.chromium.org/2512963002 Cr-Commit-Position: refs/heads/master@{#41175} | 9 年前 | |
[tests] Remove mentions of --no-always-turbofan Bug: 431974094 Change-Id: I065cfcb8e0639b1a4b7b0c2c28beb6d217bbcb71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6780589 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101613} | 11 个月前 | |
[elements] Rename FAST elements kinds The FAST_ prefix doesn’t make much sense — they’re all just different cases with their own optimizations. Packedness being implicit (e.g. FAST_ELEMENTS vs. FAST_HOLEY_ELEMENTS) is not ideal, either. This patch renames the FAST elements kinds as follows: - e.g. FAST_ELEMENTS => PACKED_ELEMENTS - e.g. FAST_HOLEY_ELEMENTS => HOLEY_ELEMENTS The following exceptions are left intact, for lack of a better name: - FAST_SLOPPY_ARGUMENTS_ELEMENTS - SLOW_SLOPPY_ARGUMENTS_ELEMENTS - FAST_STRING_WRAPPER_ELEMENTS - SLOW_STRING_WRAPPER_ELEMENTS This makes it easier to reason about elements kinds, and less confusing to explain how they’re used. R=jkummerow@chromium.org, cbruni@chromium.org BUG=v8:6548 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: Ie7c6bee85583c3d84b730f7aebbd70c1efa38af9 Reviewed-on: https://chromium-review.googlesource.com/556032 Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#46361} | 8 年前 | |
Fix common misspellings Bug: chromium:750830 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_chromium_rel_ng;master.tryserver.v8:v8_linux_noi18n_rel_ng Change-Id: Icab7b5a1c469d5e77d04df8bfca8319784e92af4 Reviewed-on: https://chromium-review.googlesource.com/595655 Commit-Queue: Julien Brianceau <jbriance@cisco.com> Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Daniel Ehrenberg <littledan@chromium.org> Cr-Commit-Position: refs/heads/master@{#47072} | 8 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[turbofan] Only save live registers on suspend When suspending, rather than saving all registers up to a certain index, only save the ones that are live according to the liveness analysis. Others are saved as optimized out constants, and are skipped during the GenaratorStore lowering. Symmetrically, only restore live registers when resuming. Change-Id: Icc2df905b0fe2fe5c372097bd67d5316edcd1b54 Reviewed-on: https://chromium-review.googlesource.com/905662 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#51153} | 8 年前 | |
[Test] Add PrepareForOptimization to debugger/ tests. BUG=v8:8801 Change-Id: Id5ef6219ba2dca2be0603dd0d45e7b27136836e9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1587391 Reviewed-by: Mythri Alle <mythria@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#61085} | 7 年前 | |
[tests] Remove mentions of --no-always-turbofan Bug: 431974094 Change-Id: I065cfcb8e0639b1a4b7b0c2c28beb6d217bbcb71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6780589 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101613} | 11 个月前 | |
Reland "[debug] Immediately step-in for 'stack check triggered' debug breaks" This is a reland of commit 3297ccca23d6d4d7bae2a730e4896faf454679fa This is a straight-up reland of the original CL. The failing test was flaky and removed with https://crrev.com/c/3868727. We replaced the test with a proper DevTools e2e test: https://crrev.com/c/3867522 Original change's description: > [debug] Immediately step-in for 'stack check triggered' debug breaks > > This CL changes debug breaks that are triggered via interrupts (i.e. > via stack check). One client of this behavior is the Debugger.pause > CDP method. > > The problem is that when we pause so early, the JSFunction didn't have > time yet to create and push it's context. This requires special > handling in the ScopeIterator and makes an upcoming change unnecessary > complex. > > Another (minor) problem is that local debug-evaluate can't change > context-allocated local variables (see changed regression bug). Since > the context is not yet created and pushed, variables are written to > the DebugEvaluateContext that goes away after the evaluation. > > The solution is to mirror what BreakOnNextFunction does. Instead > of staying paused in the middle of the function entry, we trigger > a "step in" and pause at the first valid breakable position instead. > This ensures that the function context is already created and pushed. > > Note that we do this only in case for JSFunctions. In all other cases > we keep the existing behavior and stay paused in the entry. > > R=jgruber@chromium.org > > Fixed: chromium:1246907 > Change-Id: I0cd8ae6e049a3b55bdd44858e769682a1ca47064 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3854501 > Reviewed-by: Jakob Linke <jgruber@chromium.org> > Commit-Queue: Simon Zünd <szuend@chromium.org> > Cr-Commit-Position: refs/heads/main@{#82817} Change-Id: I1938ccb5979fd80dff530b2ffe3f18714b7eff3f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3867727 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Jakob Linke <jgruber@chromium.org> Cr-Commit-Position: refs/heads/main@{#82901} | 3 年前 | |
[debugger] Further stepping support in test wrapper This CL adds further support to the test wrapper. We are now able to run almost all mjsunit/debug-step-* tests using the inspector backend. debug-stepframe-* tests are not yet supported since inspector does not know a 'frame' step type. The interface has also been improved to be able to move these tests to inspector mostly without modification. BUG=v8:5330 Review-Url: https://codereview.chromium.org/2466273005 Cr-Commit-Position: refs/heads/master@{#40800} | 9 年前 | |
[debugger] Further stepping support in test wrapper This CL adds further support to the test wrapper. We are now able to run almost all mjsunit/debug-step-* tests using the inspector backend. debug-stepframe-* tests are not yet supported since inspector does not know a 'frame' step type. The interface has also been improved to be able to move these tests to inspector mostly without modification. BUG=v8:5330 Review-Url: https://codereview.chromium.org/2466273005 Cr-Commit-Position: refs/heads/master@{#40800} | 9 年前 | |
[debugger] Further stepping support in test wrapper This CL adds further support to the test wrapper. We are now able to run almost all mjsunit/debug-step-* tests using the inspector backend. debug-stepframe-* tests are not yet supported since inspector does not know a 'frame' step type. The interface has also been improved to be able to move these tests to inspector mostly without modification. BUG=v8:5330 Review-Url: https://codereview.chromium.org/2466273005 Cr-Commit-Position: refs/heads/master@{#40800} | 9 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[explicit-resource-management] Add more DevTools tests This CL adds two missing test cases for stepping into disposal callbacks and error stack traces. Bug: 417615386 Change-Id: If872a40e15c786c788967339545d51b3df413e78 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6551810 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Commit-Queue: Rezvan Mahdavi Hezaveh <rezvan@chromium.org> Cr-Commit-Position: refs/heads/main@{#100407} | 1 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[flags] Rename --opt to --turbofan 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/+/3610431 Reviewed-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} | 4 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debugger] Further stepping support in test wrapper This CL adds further support to the test wrapper. We are now able to run almost all mjsunit/debug-step-* tests using the inspector backend. debug-stepframe-* tests are not yet supported since inspector does not know a 'frame' step type. The interface has also been improved to be able to move these tests to inspector mostly without modification. BUG=v8:5330 Review-Url: https://codereview.chromium.org/2466273005 Cr-Commit-Position: refs/heads/master@{#40800} | 9 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debug][cleanup] Use consistent StepInto and StepOver naming. In the Chrome DevTools Protocol, the step actions are named StepOut, StepOver, and StepInto, but internally we used StepOut, StepNext, and StepIn instead. This change adjusts the naming to be consistent. Bug: chromium:901814, chromium:1162229 Change-Id: Id3502a1b0a4aadd94734ec3d1fef73c1782fa220 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2928510 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#74877} | 5 年前 | |
[debugger] Further stepping support in test wrapper This CL adds further support to the test wrapper. We are now able to run almost all mjsunit/debug-step-* tests using the inspector backend. debug-stepframe-* tests are not yet supported since inspector does not know a 'frame' step type. The interface has also been improved to be able to move these tests to inspector mostly without modification. BUG=v8:5330 Review-Url: https://codereview.chromium.org/2466273005 Cr-Commit-Position: refs/heads/master@{#40800} | 9 年前 | |
[debug] retire ScriptWrapper - rewritten couple tests, - migrated JSMessageObject to real Script instead of wrapper, - removed wrapper. R=yangguo@chromium.org TBR=ulan@chromium.org Bug: v8:5530 Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ia95492344c7b5978a940e2ab007b389384537148 Reviewed-on: https://chromium-review.googlesource.com/1112851 Reviewed-by: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Cr-Commit-Position: refs/heads/master@{#54274} | 7 年前 | |
[Test] Add PrepareForOptimization to debugger/ tests. BUG=v8:8801 Change-Id: Id5ef6219ba2dca2be0603dd0d45e7b27136836e9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1587391 Reviewed-by: Mythri Alle <mythria@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#61085} | 7 年前 | |
[debug-wrapper] clearAllBreakPoints and several scripts functions This adds clearAllBreakPoints functionality (which requires tracking set breakpoints internally), and several script-related functions that rely on runtime functions. BUG=v8:5530 Review-Url: https://codereview.chromium.org/2508853003 Cr-Commit-Position: refs/heads/master@{#41064} | 9 年前 | |
[flag] Remove remaining mentions of --always-turbofan Bug: 431974094 Change-Id: Ib6fc1461fdd32545662465b785b62ba5c11fe0e9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6779590 Auto-Submit: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101659} | 11 个月前 | |
[tests] Remove mentions of --no-always-turbofan Bug: 431974094 Change-Id: I065cfcb8e0639b1a4b7b0c2c28beb6d217bbcb71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6780589 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101613} | 11 个月前 | |
[ignition/turbo] Perform liveness analysis on the bytecodes Replaces the graph-based liveness analyzer in the bytecode graph builder with an initial bytecode-based liveness analysis pass, which is added to the existing loop extent analysis. Now the StateValues in the graph have their inputs initialised to optimized_out, rather than being modified after the graph is built. Review-Url: https://codereview.chromium.org/2523893003 Cr-Commit-Position: refs/heads/master@{#41355} | 9 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 年前 | ||
| 9 个月前 | ||
| 11 个月前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 11 个月前 | ||
| 7 个月前 | ||
| 1 年前 | ||
| 5 年前 | ||
| 8 年前 | ||
| 7 年前 | ||
| 1 年前 | ||
| 7 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 7 年前 | ||
| 9 年前 | ||
| 8 年前 | ||
| 8 年前 | ||
| 11 个月前 | ||
| 9 年前 | ||
| 5 年前 | ||
| 9 年前 | ||
| 11 个月前 | ||
| 7 年前 | ||
| 8 年前 | ||
| 11 个月前 | ||
| 11 个月前 | ||
| 9 年前 | ||
| 6 年前 | ||
| 6 年前 | ||
| 11 个月前 | ||
| 7 年前 | ||
| 7 年前 | ||
| 8 年前 | ||
| 11 个月前 | ||
| 9 年前 | ||
| 4 年前 | ||
| 6 年前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 8 年前 | ||
| 8 年前 | ||
| 9 年前 | ||
| 9 年前 | ||
| 9 年前 | ||
| 9 年前 | ||
| 9 年前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 2 年前 | ||
| 11 个月前 | ||
| 9 年前 | ||
| 5 年前 | ||
| 9 年前 | ||
| 11 个月前 | ||
| 8 年前 | ||
| 8 年前 | ||
| 5 年前 | ||
| 8 年前 | ||
| 7 年前 | ||
| 11 个月前 | ||
| 3 年前 | ||
| 9 年前 | ||
| 9 年前 | ||
| 9 年前 | ||
| 5 年前 | ||
| 1 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 9 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 9 年前 | ||
| 7 年前 | ||
| 7 年前 | ||
| 9 年前 | ||
| 11 个月前 | ||
| 11 个月前 | ||
| 9 年前 |