wasm2js: Support arbitrary temp variable types #6661
Conversation
src/wasm2js.h Outdated
| // Which are currently free to use | ||
| std::vector<std::vector<IString>> frees; // type => list of free names | ||
| std::unordered_map<Type, std::vector<IString>> | ||
| frees; // type => list of free names |
There was a problem hiding this comment.
If the comment is placed on its own line, we won't need this odd line break before the variable name.
| frees.resize(std::max(Type::i32, std::max(Type::f32, Type::f64)) + 1); | ||
| temps.clear(); | ||
| temps.resize(std::max(Type::i32, std::max(Type::f32, Type::f64)) + 1); | ||
| temps[Type::i32] = temps[Type::f32] = temps[Type::f64] = 0; |
There was a problem hiding this comment.
Was this resetting only necessary for the asserts below?
There was a problem hiding this comment.
Good catch, turns out it was not. I did not realize this class reused the instance for all the functions. What made me miss this in the outputs is that any excess temp vars that were added get removed by later optimizations... so it seemed like manually clearing was not needed, but it was. Fixed.
test/wasm2js/left-to-right.2asm.js Outdated
| | ||
| function $53() { | ||
| var wasm2js_i32$0 = 0, wasm2js_i32$1 = 0; | ||
| var wasm2js_i32$0 = 0, wasm2js_i32$2 = 0; |
There was a problem hiding this comment.
Do you know why the names changed?
There was a problem hiding this comment.
This diff was because of the extra temp vars - unneeded ones get optimized out, but the optimizer happened to pick other ones here. Anyhow, this part of the diff goes away in the last commit.
2 participants
Previously only basic types were allowed.
Generalizing this to arbitrary types means we use a map instead of a vector,
which is slower, but I can't measure any noticeable difference. Temp vars are
pretty rare, and there are just much slower parts of wasm2js, I think.