Open UnitedMarsupials opened 1 month ago
Hello @UnitedMarsupials and thank you for opening this issue.
Yes, you can #define SIMDE_FLOAT16_API 1
before importing any SIMDe header to work around this. Or as a compiler command line option -DSIMDE_FLOAT16_API=1
.
What flags are set by the wasm32-wasi target? It would be good to add a fix near https://github.com/simd-everywhere/simde/blob/e30e6ec44cdbc85c04d6cb1f26fb6d93f43cc5ea/simde/simde-f16.h#L71
Yes, you can
#define SIMDE_FLOAT16_API 1
Thanks! Let me try that.
What flags are set by the wasm32-wasi target?
Using the trick from here, I conclude, that, in case of clang
, at least, these are:
#define __wasi__ 1
#define __wasm 1
#define __wasm32 1
#define __wasm32__ 1
#define __wasm__ 1
#define __wasm_mutable_globals__ 1
#define __wasm_sign_ext__ 1
Yes, you can
#define SIMDE_FLOAT16_API 1
Thanks! Let me try that.
Did that work?
How can we test SIMDE with WASI in our CI? We can make a PR to not use the _Float16
if __wasi__
is defined, but I'll want a CI build & run of the tests under WASI to confirm
Hello. As you may know, Mozilla bundles an older version of simde with their sources, and it works. I'm trying to use the latest version (0.8.2) installed by the FreeBSD port on my machine.
Unfortunately, compiling for the
wasm32-wasi
fails:Is this a bug? Perhaps, I can set the
SIMDE_FLOAT16_API
to something as a work-around?