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

I        0+0x3      read  @00000004 i32:0 / 00000000
I        1+0x3      read  @00000001  i8:0 / 00
I        3+0x5      store @00000004 i32:305419896 / 12345678
I        0+0x3      read  @00000002 i32:1450704896 / 56780000
I        1+0x3      read  @00000006  i8:52 / 34
I        2+0x3      read  @00000002 f32:68169720922112.000000 / 56780000
I        4+0x5      store @00000004  i8:171 / ab
I        0+0x3      read  @00000002 i32:1454047232 / 56ab0000
I        2+0x3      read  @00000002 f32:94008244174848.000000 / 56ab0000
[wasm] Add flag for memory tracing With --wasm-trace-memory, both compiled code and the interpreter will output each memory load or store. This helps to debug miscompilations in emscripten or in V8, like the referenced bug. R=titzer@chromium.org Bug: chromium:718858 Change-Id: I90704d164975b11c65677f86947ab102242d5153 Reviewed-on: https://chromium-review.googlesource.com/684316 Reviewed-by: Ben Titzer <titzer@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#48255} 2017-10-02 07:39:30 +00:00			`I 0+0x3 read @00000004 i32:0 / 00000000`
			`I 1+0x3 read @00000001 i8:0 / 00`
			`I 3+0x5 store @00000004 i32:305419896 / 12345678`
			`I 0+0x3 read @00000002 i32:1450704896 / 56780000`
			`I 1+0x3 read @00000006 i8:52 / 34`
			`I 2+0x3 read @00000002 f32:68169720922112.000000 / 56780000`
			`I 4+0x5 store @00000004 i8:171 / ab`
			`I 0+0x3 read @00000002 i32:1454047232 / 56ab0000`
			`I 2+0x3 read @00000002 f32:94008244174848.000000 / 56ab0000`