Hi, I'm a maintainer of https://hub.docker.com/r/trzeci/emscripten/ and I need some hand with last changes for Emscripten backend
My current observation is that 1.38.31 was the last SDK version which was possible to compile fastcomp from sources, then every other version includes this 'frozen' version. Than is if I install 1.38.40 (non-upstream) I'm getting binaries of clang that I got with 1.38.31. Is that correct? In case of the upstream version I'm also getting aside fastcomp version: ``` ./upstream/fastcomp/bin/clang --version clang version 6.0.1 (/b/s/w/ir/cache/git/chromium.googlesource.com-external-github.com-emscripten--core-emscripten--fastcomp--clang 98df4be387dde3e3918fa5bbb5fc43e1a0e1daac) (/b/s/w/ir/cache/git/chromium.googlesource.com-external-github.com-emscripten--core-emscripten--fastcomp 1b4148f39a69c7fc62edadd85e4122b68694dfb7) (emscripten 1.38.31 : 1.38.31) ``` Why is that needed still? Last question about the upstream clang version which is ATM: clang version 10.0.0 (/b/s/w/ir/cache/git/chromium.googlesource.com-external-github.com-llvm-llvm--project ea134f221f2a5c075b7539876a444b4a07362912). - is there something special with served binaries (like special compilation flags, or just a regular clang 10 release)? Is it needed to be on clang 10.0.0? What I notice is that regardless if I install 1.38.34-upstream or 1.38.41-upstream - I'm getting exactly the same binaries of clang Any help with solving/confirming issues from above will be helpful to get back on track with docker images. Cheers! -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/e8741ec1-f53e-4a39-afc1-5461a8cfee29%40googlegroups.com.
