"bad fde: FDE is really a CIE" warning on x64 linux musl

[coolreader18]

Describe the bug

I'm assuming this is similar to bytecodealliance/wasmtime#1904 - there are a bunch of warnings in logs libunwind: __unw_add_dynamic_fde: bad fde: FDE is really a CIE, with wasmer 1.0.2, rustc 1.50, os AWS lambda (originally seen) or arch linux (reproduced).

Steps to reproduce

wasmer/lib/cli/ $ cargo build --release --features llvm
wasmer/lib/cli/ $ cargo build --release --target x86_64-unknown-linux-musl
wasmer/ $ target/release/wasmer compile --jit --llvm lib/c-api/tests/assets/qjs.wasm -o qjs.wjit
Engine: jit
Compiler: llvm
Target: x86_64-unknown-linux-gnu
✔ File compiled successfully to `qjs.wjit`.
wasmer/ $ target/x86_64-unknown-linux-musl/release/wasmer run qjs.wjit
libunwind: __unw_add_dynamic_fde: bad fde: FDE is really a CIE
libunwind: __unw_add_dynamic_fde: bad fde: FDE is really a CIE
libunwind: __unw_add_dynamic_fde: bad fde: FDE is really a CIE
# snip - 930 total lines of warnings
libunwind: __unw_add_dynamic_fde: bad fde: FDE is really a CIE
libunwind: __unw_add_dynamic_fde: bad fde: FDE is really a CIE
libunwind: __unw_add_dynamic_fde: bad fde: FDE is really a CIE
QuickJS - Type "\h" for help
qjs > 

[coolreader18]

Also occurs with tests/wasi-wast/wasi/snapshot1/hello.wasm with 203 warnings

[syrusakbary]

Interesting... we solved the bug in #1650.

It might be the case that somehow the gnu compiler is not detected?
#1631 (comment)

[Hywan]

Possible unresolved (at the time of writing) issue, https://bugs.llvm.org/show_bug.cgi?id=44074

[syrusakbary]

Closing the issue, as we believe it's already solved.
If that's not the case feel free to reopen it @coolreader18