-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Current docker image doesn't support llvm upstream #47
Comments
Hi @Fraer current docker images base on fastcomp backend (instead of llvm upstream) Thank you for reporting! |
So is this an issue with the docker image? Can you re-title it accordingly please? |
@trzecieu it looks like you added upstream backend support, so we can close this? Thanks! Btw, are there docs for how to use the upstream backend there? |
Hi @kripken, upstream backend isn't added yet, I was fighting with recovering fastcomp llvm. |
I see, thanks @trzecieu |
Fixed now: trzeci/emscripten-upstream
And how it looked like:
This is a first implementation, which is not size optimized yet and it's 100MB larger than fastcomp version of the same image. Nonetheless, it should be fully functional now! Cheers, |
Great news, thanks @trzecieu ! |
Thank's a lot @trzecieu. I'll be looking forward to testing the new "upstream" container. One small comment: Would it be possible for you to add some documentation to https://hub.docker.com/r/trzeci/emscripten-upstream/ that explains if "emscripten-upstream" contain the same content as "emscripten" or "emscripten-slim"? |
Definitely will do, I'm doing some clean-up and improving documentation on another branch, cheers! |
If env var EMCC_WASM_BACKEND=1
When calling any of emconfigure or emcc, etcc ...
The text was updated successfully, but these errors were encountered: