v8/test/inspector/debugger/wasm-stepping-no-opcode-merging-expected.txt

Tests that Liftoff does not merge opcodes while stepping
Setting breakpoint at offset 33.
Paused at offset 33: [0]
Paused at offset 35: [0, 0]
Paused at offset 36: [0, 1]
Paused at offset 33: [-1]
Paused at offset 35: [-1, -1]
Paused at offset 36: [-1, 0]
Paused at offset 38: [-1]
Paused at offset 33: [13]
Paused at offset 35: [13, 13]
Paused at offset 36: [13, 0]
Paused at offset 38: [13]
Finished.
[liftoff] Add test for opcode-merging during stepping We currently still merge opcodes (i.e. i32 comparisons plus a br_if). This CL adds a test for this, which checks for the current behaviour. A follow-up CL will fix this and update the expected output accordingly. R=thibaudm@chromium.org Bug: v8:10350 Change-Id: I846aa931a3ec1a27043f04e830503d5732ae473e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2307232 Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#68957} 2020-07-20 10:51:09 +00:00			`Tests that Liftoff does not merge opcodes while stepping`
			`Setting breakpoint at offset 33.`
			`Paused at offset 33: [0]`
			`Paused at offset 35: [0, 0]`
[liftoff] Disable opcode merging when debugging For debugging code, disable opcode merging. Otherwise, the effect of the first merged opcode would not be observable when stepping. R=thibaudm@chromium.org Bug: v8:10350 Change-Id: Id656c9dee8f9676bf3d7881f3782e5ead76b5e71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2306802 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#68960} 2020-07-20 10:52:03 +00:00			`Paused at offset 36: [0, 1]`
[liftoff] Add test for opcode-merging during stepping We currently still merge opcodes (i.e. i32 comparisons plus a br_if). This CL adds a test for this, which checks for the current behaviour. A follow-up CL will fix this and update the expected output accordingly. R=thibaudm@chromium.org Bug: v8:10350 Change-Id: I846aa931a3ec1a27043f04e830503d5732ae473e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2307232 Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#68957} 2020-07-20 10:51:09 +00:00			`Paused at offset 33: [-1]`
			`Paused at offset 35: [-1, -1]`
[liftoff] Disable opcode merging when debugging For debugging code, disable opcode merging. Otherwise, the effect of the first merged opcode would not be observable when stepping. R=thibaudm@chromium.org Bug: v8:10350 Change-Id: Id656c9dee8f9676bf3d7881f3782e5ead76b5e71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2306802 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#68960} 2020-07-20 10:52:03 +00:00			`Paused at offset 36: [-1, 0]`
[liftoff] Add test for opcode-merging during stepping We currently still merge opcodes (i.e. i32 comparisons plus a br_if). This CL adds a test for this, which checks for the current behaviour. A follow-up CL will fix this and update the expected output accordingly. R=thibaudm@chromium.org Bug: v8:10350 Change-Id: I846aa931a3ec1a27043f04e830503d5732ae473e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2307232 Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#68957} 2020-07-20 10:51:09 +00:00			`Paused at offset 38: [-1]`
			`Paused at offset 33: [13]`
			`Paused at offset 35: [13, 13]`
[liftoff] Disable opcode merging when debugging For debugging code, disable opcode merging. Otherwise, the effect of the first merged opcode would not be observable when stepping. R=thibaudm@chromium.org Bug: v8:10350 Change-Id: Id656c9dee8f9676bf3d7881f3782e5ead76b5e71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2306802 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#68960} 2020-07-20 10:52:03 +00:00			`Paused at offset 36: [13, 0]`
[liftoff] Add test for opcode-merging during stepping We currently still merge opcodes (i.e. i32 comparisons plus a br_if). This CL adds a test for this, which checks for the current behaviour. A follow-up CL will fix this and update the expected output accordingly. R=thibaudm@chromium.org Bug: v8:10350 Change-Id: I846aa931a3ec1a27043f04e830503d5732ae473e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2307232 Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#68957} 2020-07-20 10:51:09 +00:00			`Paused at offset 38: [13]`
			`Finished.`