summaryrefslogtreecommitdiff
path: root/src/parser/parsers.h
diff options
context:
space:
mode:
authorAlon Zakai <azakai@google.com>2024-01-08 16:03:33 -0800
committerGitHub <noreply@github.com>2024-01-09 00:03:33 +0000
commit185019919b1fa2efe8d02056827a31f4f50dd01e (patch)
tree19caab62ddbc1481d676b8e49e51bd5ddf8ebb78 /src/parser/parsers.h
parentcc0fab918aed3643abdc3566ade3f70f06d1d954 (diff)
downloadbinaryen-185019919b1fa2efe8d02056827a31f4f50dd01e.tar.gz
binaryen-185019919b1fa2efe8d02056827a31f4f50dd01e.tar.bz2
binaryen-185019919b1fa2efe8d02056827a31f4f50dd01e.zip
Fix global effect computation with -O flags (#6211)
We tested --generate-global-effects --vacuum and such, but not --generate-global-effects -O3 or the other -O flags. Unfortunately, our targeted testing missed a bug because of that. Specifically, we have special logic for -O flags to make sure the passes they expand into run with the proper opt and shrink levels, but that logic happened to also interfere with global effect computation. It would also interfere with allowing GUFA info or other things to be stored on the side, which we've proposed. This PR fixes that + future issues. The fix is to just allow a pass runner to execute more than once. We thought to avoid that and assert against it to keep the model "hermetic" (you create a pass runner, you run the passes, and you throw it out), which feels nice in a way, but it led to the bug here, and I'm not sure it would prevent any other ones really. It is also more code. It is simpler to allow a runner to execute more than once, and add a method to clear it. With that, the logic for -O3 execution is both simpler and does not interfere with anything but the opt and shrink level flags: we create a single runner, give it the proper options, and then keep using that runner + those options as we go, normally.
Diffstat (limited to 'src/parser/parsers.h')
0 files changed, 0 insertions, 0 deletions