v8/test/message/wasm-trace-memory-interpreted.out

interpreter func:     0+0x3     load from 00000004 val: i32:0 / 00000000
interpreter func:     1+0x3     load from 00000001 val:  i8:0 / 00
interpreter func:     3+0x5      store to 00000004 val: i32:305419896 / 12345678
interpreter func:     0+0x3     load from 00000002 val: i32:1450704896 / 56780000
interpreter func:     1+0x3     load from 00000006 val:  i8:52 / 34
interpreter func:     2+0x3     load from 00000002 val: f32:68169720922112.000000 / 56780000
interpreter func:     4+0x5      store to 00000004 val:  i8:171 / ab
interpreter func:     0+0x3     load from 00000002 val: i32:1454047232 / 56ab0000
interpreter func:     2+0x3     load from 00000002 val: f32:94008244174848.000000 / 56ab0000
[wasm] Make the output of --wasm-trace-memory more understandable R=clemensh@chromium.org Change-Id: I21d185c73dc22a79311f3b35b2602a00a4b96112 Reviewed-on: https://chromium-review.googlesource.com/1141743 Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#54547} 2018-07-19 09:03:20 +00:00			`interpreter func: 0+0x3 load from 00000004 val: i32:0 / 00000000`
			`interpreter func: 1+0x3 load from 00000001 val: i8:0 / 00`
			`interpreter func: 3+0x5 store to 00000004 val: i32:305419896 / 12345678`
			`interpreter func: 0+0x3 load from 00000002 val: i32:1450704896 / 56780000`
			`interpreter func: 1+0x3 load from 00000006 val: i8:52 / 34`
			`interpreter func: 2+0x3 load from 00000002 val: f32:68169720922112.000000 / 56780000`
			`interpreter func: 4+0x5 store to 00000004 val: i8:171 / ab`
			`interpreter func: 0+0x3 load from 00000002 val: i32:1454047232 / 56ab0000`
			`interpreter func: 2+0x3 load from 00000002 val: f32:94008244174848.000000 / 56ab0000`