Marc Poulhiès

(ping @TamarChristinaArm , I'll try to handle that shortly...)

The arm64 with an updated go has now (local test): ``` d-libc/multilib/csu/crtn.o [ALL ] /opt/.build/aarch64-unknown-linux-gnu/buildtools/lib/gcc/aarch64-unknown-linux-gnu/16.0.0/../../../../aarch64-unknown-linux-gnu/bin/ld: cannot find -lgcc_s: N o such file or directory [ALL ] /opt/.build/aarch64-unknown-linux-gnu/buildtools/lib/gcc/aarch64-unknown-linux-gnu/16.0.0/../../../../aarch64-unknown-linux-gnu/bin/ld: cannot find -lgcc_s:...

cc @CohenArthur Currently building, but looks fine.

``` === rust Summary === # of expected passes 10443 # of expected failures 74 # of unsupported tests 7 ``` Identical count as current master.

``` gcc/rust/ChangeLog: * Make-lang.in: New file. ``` This is misleading. "New file" is idiomatic for "this is a new file". You probably meant "I've added new file rules in the...

You can probably kill the 2 first commits, as one is reverted the other.

Also, it seems your branch is not using a recent main as the base and it causes conflicts. Can you rebase over latest main?

Looks like there are still conflicts (at least github thinks there are..). And can you please remove the 2 firsts commits? See:  Having: - commit A - Revert commit...

Also, your base branch is really old:  You really need to use a recent `main` to test everything applies and works, currently, you are 276 commits behind the `main`...

the rv-linux toolchain can link to a binary, but of course we can't execute it. It seems we do have a config issue as some rv target are wrongly enable...