Andreas Haas f7a1932ef9 [wasm] Re-exported globals preserve their identity ... V8 fails a recently added spec test that when an imported global get re-exported, it should preserve its identity. This CL fixes the behavior in V8. Drive-by change: fix the object printer of globals: a global which stores a reference type only has a tagged buffer, a global which stores a value type only has an untagged buffer. R=clemensb@chromium.org Bug: v8:10556 Change-Id: I949d147fe4395610cfec6cf60082e1faecb23036 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2235702 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#68513}		2020-06-24 14:10:43 +00:00
..
third_party	[wasm] Re-exported globals preserve their identity	2020-06-24 14:10:43 +00:00
after.js	[wasm][tests] Sync testharness of wasm-js tests with wpt	2020-06-16 08:17:19 +00:00
BUILD.gn	Reland "[wasm] Add a new wasm-js testsuite to run js-api tests"	2018-10-18 20:18:55 +00:00
OWNERS	Use relative paths to OWNERS files	2019-08-12 13:52:52 +00:00
report.js	[wasm][tests] Sync testharness of wasm-js tests with wpt	2020-06-16 08:17:19 +00:00
testcfg.py	[wasm][tests] Sync testharness of wasm-js tests with wpt	2020-06-16 08:17:19 +00:00
testharness-additions.js	[wasm][tests] Sync testharness of wasm-js tests with wpt	2020-06-16 08:17:19 +00:00
tests.tar.gz.sha1	[wasm] Update wasm spec tests	2020-06-16 22:00:04 +00:00
wasm-js.status	[wasm] Re-exported globals preserve their identity	2020-06-24 14:10:43 +00:00