commit 6c127652097928ee1707a7bd1d5247e9fe1b3a2b
author Derek Schuff <dschuff@chromium.org> Thu Jan 25 09:48:38 2024 -0800
committer Copybara-Service <copybara-worker@google.com> Thu Jan 25 09:50:22 2024 -0800
tree 1d49093ca34f11ab999ba535bf086444ebcb0e07
parent 0c5e93f9f6bddc6d810b4b66bbfe9fa957a83529

[Object][Wasm] Allow parsing of GC types in type and table sections (#79235)

This change allows a WasmObjectFile to be created from a wasm file even
if it uses typed funcrefs and GC types. It does not significantly change how
lib/Object models its various internal types (e.g. WasmSignature,
WasmElemSegment), so LLVM does not really "support" or understand such
files, but it is sufficient to parse the type, global and element sections, discarding
types that are not understood. This is useful for low-level binary tools such as
nm and objcopy, which use only limited aspects of the binary (such as function
definitions) or deal with sections as opaque blobs.

This is done by allowing `WasmValType` to have a value of `OTHERREF`
(representing any unmodeled reference type), and adding a field to
`WasmSignature` indicating it's a placeholder for an unmodeled reference
type (since there is a 1:1 correspondence between WasmSignature objects
and types in the type section).
Then the object file parsers for the type and element sections are expanded
to parse encoded reference types and discard any unmodeled fields.

GitOrigin-RevId: 7f409cd82b322038f08a984a07377758e76b0e4c