diff options
author | Alon Zakai <azakai@google.com> | 2022-10-24 12:34:29 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-10-24 12:34:29 -0700 |
commit | 5245b8cdf64dad2e2b7c19b08fe22d2e6039ffa7 (patch) | |
tree | ce2654a9e1af7eb9813a70471e32e72adcc11ab7 /src/passes/CodePushing.cpp | |
parent | 3986d95de1f3d91e4ec2193bc70c6c4b4fdbd1bd (diff) | |
download | binaryen-5245b8cdf64dad2e2b7c19b08fe22d2e6039ffa7.tar.gz binaryen-5245b8cdf64dad2e2b7c19b08fe22d2e6039ffa7.tar.bz2 binaryen-5245b8cdf64dad2e2b7c19b08fe22d2e6039ffa7.zip |
[NFC] Remove an ancient hack in ReFinalize (#5183)
Poking in the git history, this was some kind of hack for a problem that appears to
no longer exist since at least 5 years ago.
Logically, refinalize should never change a type from unreachable to none, or at
least if we have a place that does this, we should manually do the necessary things
around that, like updating the function's return type. The opposite, none (or anything
else) to unreachable is the common case, where we use refinalize to propagate
that type upwards.
Fuzzing also finds no issues.
Diffstat (limited to 'src/passes/CodePushing.cpp')
0 files changed, 0 insertions, 0 deletions