Hi, Willy
Hi Zhangjin,
On Sat, Aug 12, 2023 at 04:27:01AM +0800, Zhangjin Wu wrote:
Hi, Willy
Here is v2 of the customized CROSS_COMPILE support, this helps a lot during the testing of the other cross-arch nolibc changes:
$ ARCHS="i386 x86_64 arm64 arm mips ppc ppc64 ppc64le riscv s390" $ for arch in ${ARCHS[@]}; do printf "%9s: " $arch; make run-user XARCH=$arch | grep status; doneBased on your suggestion, we did this changes:
- The qemu notes patch [1] is removed, welcome your doc file ;-)
- Arnd's crosstools are customized by default
- Import cc-cross-prefix to support local cross toolchains too
- Use mips64 toolchains for mips like x86_64 toolchains for i386, allow download less toolchains
- Use HOSTCC for libc-test compiling
(...)
I think it's basically OK (just this mips64 thing). I've picked patch 3 already since it's a fix. Once we agree on what to do there, I can queue it if that helps (I can modify mips64- to mips- in the patch if that's OK for you, no need to resend for this, just let me know).
It is ok for me, thanks ;-)
I thought somebody may add mips64 support soon, but we do only have mips currently, it is fair to not use mips64 toolchain.
I think that later I'll further extend XARCH with new variants to support ARMv5 and Thumb2, because we have different code for this and I continue to manually change the CFLAGS to test both.
Ok, what about further add x86_64 as the default variant for x86 (like ppc for powerpc)? and then it is able to only resereve the variables for x86_64. I have prepared a patch for this goal in our new tinyconfig patchset, it will further avoid adding the same nolibc-test-x86.config and nolibc-test-x86_64.config.
Best regards, Zhangjin
Thanks, Willy