aboutsummaryrefslogtreecommitdiffstats
path: root/lib/compiler/vsn.mk
diff options
context:
space:
mode:
authorBjörn Gustavsson <[email protected]>2018-02-06 06:28:05 +0100
committerBjörn Gustavsson <[email protected]>2018-03-14 11:28:57 +0100
commitc896f08f5c028b1e31290e6a5502597401acd39f (patch)
treec8709d66de1d66d74f3f728f075a1e37a035bb98 /lib/compiler/vsn.mk
parent64859cc36efde18483f3a9116c85c2e73ecb304d (diff)
downloadotp-c896f08f5c028b1e31290e6a5502597401acd39f.tar.gz
otp-c896f08f5c028b1e31290e6a5502597401acd39f.tar.bz2
otp-c896f08f5c028b1e31290e6a5502597401acd39f.zip
v3_kernel: Stop ensuring one return value in #k_try{}
For unclear reasons, v3_kernel attempts to guarantee that #k_try{} always has at least one return value, even if it will never be used. I said "attempts", because the handler block that is executed when an exception is caught does not have the same guarantee. That means that if an exception is thrown, the return value will not actually be set. In practice, however, this is not a problem for the existing code generator (v3_codegen). The generated code will still be safe. If we are to rewrite the code generator to generate an SSA-based intermediate format, this inconsistency *will* cause problems when creating phi nodes. While at it, also remove an unecessary creation of new variables in generation of #k_try_enter{}.
Diffstat (limited to 'lib/compiler/vsn.mk')
0 files changed, 0 insertions, 0 deletions