Handling NaNs (Not a Number, usually referring to operations that trigger non arithmetic numbers, such as 0/0) was not optimally handled by Wasmer LLVM compiler.
We had a custom NaN "canonicalizer" that was always canonicalizing NaNs (that means: making sure the NaN bits were always the same in any chipset) regardless of use case and need. We took a look on how other runtimes were doing it more optimally and realized we could use LLVM intrinsic calls for math operations so LLVM would handle it directly.
If you are curious about the tech details, here's the PR! https://github.com/wasmerio/wasmer/pull/2161