[PATCH] D91203: [WebAssembly] Fixed wasm64 DWARF using 64-bit code pointer sizes

[Sam Clegg via Phabricator via llvm-commits]

sbc100 added a comment.

> I expect they'd intend to read a code pointer from program memory (eg: a void (*)()) and expect it means the same thing as reading a code pointer from the DWARF data itself (eg: low_pc of a function, etc).

There is simply no way to do this in WebAssembly.  The code pointers used by the user code are table indexes they will never match bytecode offsets (which is what  low_pc is).  Given that we already have DWARF consumers of WebAssembly DWARF pointers I wonder how they handle this today?

For example 1, 2, and 3 are perfectly valid function addresses in user code but make no sense as bytecode offsets.   @yurydelendik will know more about this is handled.


CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D91203/new/

https://reviews.llvm.org/D91203