diff options
| author | Sam Clegg <sbc@chromium.org> | 2021-12-07 11:07:46 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-12-07 19:07:46 +0000 |
| commit | 356162224a50375166af2c45595e92d61aec02b9 (patch) | |
| tree | f1d175144ca7a5a39b0b00c8c56f56897f7e9024 /src/binary.cc | |
| parent | c9f22f2b73ed3b01172bfbcfe4f7304dea212ec9 (diff) | |
| download | wabt-356162224a50375166af2c45595e92d61aec02b9.tar.gz wabt-356162224a50375166af2c45595e92d61aec02b9.tar.bz2 wabt-356162224a50375166af2c45595e92d61aec02b9.zip | |
Show tag names in objdump disassembly (#1774)
Tag names are not officially part of the extended-name-section proposal
(because it only deals with naming things that are in the spec already).
However, I think its reasonable (and useful) to include these names
under a speculative subsection ID, on the basis that tags can only exist
when exceptions are enabled and that engines should ignore unknown name
types.
Diffstat (limited to 'src/binary.cc')
| -rw-r--r-- | src/binary.cc | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/src/binary.cc b/src/binary.cc index 60b20cbb..96103b4a 100644 --- a/src/binary.cc +++ b/src/binary.cc @@ -42,6 +42,7 @@ const char* GetSectionName(BinarySection sec) { } } +// clang-format off const char* NameSubsectionName[] = { "module", "function", @@ -53,9 +54,14 @@ const char* NameSubsectionName[] = { "global", "elemseg", "dataseg", + "tag", }; +// clang-format on const char* GetNameSectionSubsectionName(NameSectionSubsection subsec) { + static_assert(WABT_ENUM_COUNT(NameSectionSubsection) == + WABT_ARRAY_SIZE(NameSubsectionName), + "Malformed ExprTypeName array"); return NameSubsectionName[size_t(subsec)]; } |