Aman Karmani

I added `f128:64` and that seemed to be enough. (https://github.com/StarGate01/Full-Stack-Fortran/compare/master...tmm1:update-emscripten) 2.0.31: ok 2.0.32: fails with libatomic reference changelog https://github.com/emscripten-core/emscripten/blob/main/ChangeLog.md#2032---10192021 commit list https://github.com/emscripten-core/emscripten/compare/2.0.31...2.0.32 -- I see, `clang` itself needs libatomic: ```...

Aha, I kept putting it in the wrong section. Confirmed working. Trying 2.0.34 next and will open a PR. Then we can try 3.x separately

2.0.34 fails with another datalayout issue: ``` #7 0.518 wasm-ld: warning: Linking two modules of different data layouts: 'lib/libgfortran.a(size_from_kind.c.bc at 4308686)' is 'e-m:e-p:32:32-p10:8:8-p20:8:8-i64:64-f128:64-n32:64-S128-ni:1:10:20' whereas 'ld-temp.o' is 'e-m:e-p:32:32-i64:64-n32:64-f128:64-S128'

2.0.33 also fails with that layout issue. I'll try adding `p10:8:8-p20:8:8` into the mix.

3.0.0: ok 3.1.10: fails ``` #8 0.553 wasm-ld: error: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.0git' Reader: 'LLVM 15.0.0git') ``` Sounds like some new LLVM feature? Not...

3.1.3 works as expected with no other changes.

Yea I suspect you may be right, and the compiled bits are being interpreted incorrectly now. I will keep investigating. Either way, quite a bit of good luck here and...

> emcc: warning: generating an executable with an object extension (.bc). If you meant to build an object file please use `-c, `-r`, or `-shared` [-Wemcc] This warning seems to...

> 3.0.0: ok > 3.1.10: fails > #8 0.553 wasm-ld: error: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.0git' Reader: 'LLVM 15.0.0git') > Yea, this definitely looks like...

> I assume Emscripten does not set the `-opaque-pointers`, otherwise the error would not pop up. I wonder where those opaque pointers are generated, maybe the bytecode IR is interpreted...