summaryrefslogtreecommitdiff
path: root/src/binaryen-c.cpp
diff options
context:
space:
mode:
authorHeejin Ahn <aheejin@gmail.com>2020-11-13 11:48:01 -0800
committerGitHub <noreply@github.com>2020-11-13 11:48:01 -0800
commit4989d79fb15dfc01d35be4b595d4246f91a55405 (patch)
tree1aa8eb144de36b802b90d0b45fbf19c9e3e6c064 /src/binaryen-c.cpp
parent0f49b56029f93c1b54736ed2473d23f457d46894 (diff)
downloadbinaryen-4989d79fb15dfc01d35be4b595d4246f91a55405.tar.gz
binaryen-4989d79fb15dfc01d35be4b595d4246f91a55405.tar.bz2
binaryen-4989d79fb15dfc01d35be4b595d4246f91a55405.zip
Make getExpressionName resemble instruction names (#3352)
This function does not return exact instruction names but more of category names. But when there is a matching instruction, as in case of `global.get/set` or `local.get/set`, it seems to return instruction names. In that regard, this makes `getExpressionName`'s return values to similar to that of real instruction names when possible, in case of some atomic instructions and `memory.init/copy` and `data.drop`. It is hard to make a test for this because this function is used in a very limited way in the codebase, such as: - When printing error messages - When printing a stack instruction names, but only for control flow instructions - When printing instruction names in Metrics
Diffstat (limited to 'src/binaryen-c.cpp')
0 files changed, 0 insertions, 0 deletions