Arjun Ramesh

I am curious as to the purpose of the output of the `--format=llvmir-unopt` option for `wamrc` if the LLVM cannot be compiled. I was under the assumption I would be...

I'm running into this exact same issue. Still doesn't work on my end. Not just with the current directory, but with any host filesystem endpoint.

Notes about the new target `wasm32-linux-musl`, added in this [rustc](https://github.com/arjunr2/rust) fork to implement a [Wasm Linux Interface](https://github.com/arjunr2/WALI) - Patching of `cc`, `ctest`, and `libtest` are still under progress for this...

As date of initiating this PR, `main` was unable to build the rust compiler and I was pointed to `libc-0.2`, which seemed to work for the compiler. It does make...

It is intended for upstreaming. This fork of [rustc](https://github.com/arjunr2/rust) supports the target. I'm also generally confused about the process since `rustc` itself depends on a patched libc crate to build....

Awesome, thanks @tgross35, @alexcrichton. Will split this PR into multiple chunks and get rid of testing as a tier-3 target

This makes sense. Whether the additions should go into either `b32` or `b64` can be discussed. I currently did `b64` since the conventions for most records for the `wali` ABI...

On a side note, I think it would actually be good to standardize the syscall shim across all targets as well. Implicit mismatching of types with expected values from C...

New PR retargetting this to main

Reducing dependency size is good. As for targets to build, in addition to Wasm, I'd like to have the host platform as a target for clang too. If you can...