97e72bbfcb
The index to be traced can be a full (platform-dependent) pointer sized integer now. This CL prepares memory tracing for that. As a drive-by, the "address" field is renamed to "offset", or "effective_offset", depending on the situation. R=manoskouk@chromium.org Bug: v8:10949 Change-Id: I1fabfdb57835f041e1310a4eb4024d6254c08752 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2465825 Reviewed-by: Manos Koukoutos <manoskouk@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#70477}
15 lines
1.3 KiB
Plaintext
15 lines
1.3 KiB
Plaintext
liftoff func: 0+0x3 load from 0000000000000004 val: i32:0 / 00000000
|
|
liftoff func: 1+0x3 load from 0000000000000001 val: i8:0 / 00
|
|
liftoff func: 3+0x5 store to 0000000000000004 val: i32:305419896 / 12345678
|
|
liftoff func: 0+0x3 load from 0000000000000002 val: i32:1450704896 / 56780000
|
|
liftoff func: 1+0x3 load from 0000000000000006 val: i8:52 / 34
|
|
liftoff func: 2+0x3 load from 0000000000000002 val: f32:68169720922112.000000 / 56780000
|
|
liftoff func: 4+0x5 store to 0000000000000004 val: i8:171 / ab
|
|
liftoff func: 0+0x3 load from 0000000000000002 val: i32:1454047232 / 56ab0000
|
|
liftoff func: 2+0x3 load from 0000000000000002 val: f32:94008244174848.000000 / 56ab0000
|
|
liftoff func: 6+0x7 store to 0000000000000004 val: s128:48879 48879 48879 48879 / 0000beef 0000beef 0000beef 0000beef
|
|
liftoff func: 5+0x3 load from 0000000000000002 val: s128:-1091633152 -1091633152 -1091633152 -1091633152 / beef0000 beef0000 beef0000 beef0000
|
|
liftoff func: 7+0x3 load from 0000000000000004 val: i16:48879 / beef
|
|
liftoff func: 8+0x3 load from 0000000000000002 val: i64:-4688528683866062848 / beef0000beef0000
|
|
liftoff func: 9+0x3 load from 0000000000000002 val: f64:-0.000015 / beef0000beef0000
|