FUTHARK-WASM-MULTICORE(1)

πŸ“¦
version 0.25.32 Β· 5 versions
, in ubuntu resolute, ubuntu stonking

πŸ’– FUTHARK-WASM-MULTICORE πŸ’–

okay bestie, so this is futhark-wasm-multicore, a page from the Futhark manual set (section 1, as the girlies say) β€” and it's the one you want when you're tryna compile Futhark to parallel WebAssembly. yes, parallel. multi-threaded. main character energy. periodt.


✨ NAME ✨

futhark-wasm-multicore β€” compile Futhark to parallel WebAssembly πŸ¦‹


🌸 SYNOPSIS 🌸

futhark wasm-multicore [options...] <program.fut>

that's it. that's the whole thing. options go in, your .fut program goes in, magic comes out πŸ’…


πŸŽ€ DESCRIPTION πŸŽ€

so here's the tea, bestie β˜• β€” futhark wasm-multicore takes a Futhark program and translates it into multi-threaded WebAssembly code. how? it does it in two little steps:

  1. it first generates C, exactly the way futhark c would.
  2. then it runs that C through Emscripten (emcc).

and what you get out the other side is a .js file πŸŽ‰ β€” which is iconic because it means the compiled code can be invoked from JavaScript.

also, the executables it produces implement the Futhark server protocol, so you can literally run them with Node.js. no cap. fr fr. 🫢


⭐ OPTIONS ⭐

  • accepts the same options as futhark-c β€” go read that page, bestie, it's all the same flags, we're not retyping them here πŸ’€

🌈 ENVIRONMENT VARIABLES 🌈

  • respects the same environment variables as futhark-wasm β€” same vibes, same env vars, go check that one out πŸ’œ

πŸŽ€ EXECUTABLE OPTIONS πŸŽ€

  • generated executables accept the same options as those generated by futhark-wasm β€” so like, whatever the spawned-out binaries from futhark-wasm take, these take too. identical behaviour, different thread count ✨

πŸ‘‘ SEE ALSO πŸ‘‘

  • futhark-c
  • futhark-wasm

2013-2020, DIKU, University of Copenhagen 🌸


and that's the whole page, babe 🧚 version 0.25.32, dated Mar 11, 2026 β€” written up by the Futhark girls, and you should read futhark-wasm next, iykyk πŸ’…βœ¨

πŸ“¦ where this page comes from