calvin2021y

Yes, it fix the build error.

has 2 warning left ```sh wamr/core/shared/platform/windows/win_socket.c:186:71: warning: passing 'unsigned int *' to parameter of type 'int *' converts between pointers to integer types with different sign [-Wpointer-sign] 186 | accept(server_sock->raw.socket,...

I build this projects for clang with mingw, I guess clang+mingw use posix solution for exception so use patch remove BH_PLATFORM_WINDOWS https://github.com/bytecodealliance/wasm-micro-runtime/issues/3809

Sorry, I will report druntime related into upstream in future. this one is reported. this patch fix the `riscv64-unknown-linux-musl` druntime ```diff diff --git a/core/sys/posix/signal.d b/core/sys/posix/signal.d index e3d80fb..9c0e423 100644 --- a/core/sys/posix/signal.d...

`ldc2 -mtriple=riscv64-unknown-linux-musl --target-abi=lp64d -mattr=+zba,+zbb,+zbc,+zbs --float-abi=hard test.d` with lto link there will be error: ```sh cannot link object files with different floating-point ABI from /risc64/bin/../sysroot/lib/crt1.o ```

with `-mattr=+d` skip this warning: ```sh Hard-float 'd' ABI can't be used for a target that doesn't support the D instruction set extension (ignoring target-abi) Hard-float 'd' ABI can't be...

the clang `sysroot/lib/crt1.o`: ```sh Attribute Section: riscv File Attributes Tag_RISCV_stack_align: 16-bytes Tag_RISCV_arch: "rv64i2p1_m2p0_a2p1_f2p2_d2p2_zicsr2p0_zifencei2p0_zmmul1p0_zaamo1p0_zalrsc1p0_zba1p0_zbb1p0_zbc1p0_zbs1p0" ``` ldc2 lto object: ```sh Attribute Section: riscv File Attributes Tag_RISCV_stack_align: 16-bytes Tag_RISCV_arch: "rv64i2p1_f2p2_d2p2_zicsr2p0_zba1p0_zbb1p0_zbc1p0_zbs1p0" ```

with `-mattr=+m,+a,+f,+d,+zicsr,+zifencei,+zmmul,+zaamo,+zalrsc,+zba,+zbb,+zbc,+zbs` get same `Tag_RISCV_arch` like `sysroot/lib/crt1.o` but still get error: ```sh cannot link object files with different floating-point ABI from sysroot/lib/crt1.o ```

It still same error. I report wrong 'ldc2 lto object arch' (it is read from without lto object), the object with lto create by ldc2 is `LLVM bitcode file`. and...

I know nothing about GitHub Actions. If it's possible to download the Alpine root filesystem, extract it, and then execute a chroot, maybe it could work without container.