Complete tier 3 target information

[ChrisDenton]

There are a number of tier 3 targets with missing support information on the Platform Support page. Let's fix that!

If you're maintain one or more of these targets can you answer the following questions:

• Does your target have std support or is it limited to no_std?
• Does it support running tools like rustc and cargo natively on the target?

You can either answer here or send a PR to update the Platform Support page.

I'll start trying to ping maintainers as I figure out who they are.

Missing tier 3 support status

• aarch64-unknown-freebsd (Add platform docs for FreeBSD. #129220)
• aarch64-unknown-teeos
• aarch64-unknown-redox (Various Redox OS fixes and add i686 Redox OS target #126192)
• aarch64-uwp-windows-msvc (Fill out missing Windows support information #126449)
• aarch64-wrs-vxworks (Add myself as VxWorks target maintainer for reference #128431)
• armeb-unknown-linux-gnueabi
• armv4t-unknown-linux-gnueabi
• armv5te-unknown-linux-uclibceabi
• armv6k-nintendo-3ds
• armv6-unknown-freebsd (Add platform docs for FreeBSD. #129220)
• armv7-unknown-freebsd (Add platform docs for FreeBSD. #129220)
• armv7-unknown-linux-uclibceabihf
• armv7-wrs-vxworks-eabihf (Add myself as VxWorks target maintainer for reference #128431)
• i686-uwp-windows-gnu (Fill out missing Windows support information #126449)
• i686-uwp-windows-msvc (Fill out missing Windows support information #126449)
• i686-wrs-vxworks (Add myself as VxWorks target maintainer for reference #128431)
• loongarch64-unknown-linux-musl (Promote loongarch64-unknown-linux-musl to Tier 2 with host tools #126298)
• m68k-unknown-linux-gnu
• mips64-openwrt-linux-musl
• mipsisa32r6-unknown-linux-gnu
• mipsisa32r6el-unknown-linux-gnu
• mipsisa64r6-unknown-linux-gnuabi64
• powerpc-unknown-linux-musl
• powerpc-unknown-openbsd (Add powerpc-unknown-openbsd maintenance status #126481)
• powerpc-wrs-vxworks-spe (Add myself as VxWorks target maintainer for reference #128431)
• powerpc-wrs-vxworks (Add myself as VxWorks target maintainer for reference #128431)
• powerpc64le-unknown-freebsd (Add platform docs for FreeBSD. #129220)
• powerpc-unknown-freebsd (Add platform docs for FreeBSD. #129220)
• powerpc64-unknown-linux-musl (Add target maintainer information for powerpc64-unknown-linux-musl #138905)
• powerpc64-wrs-vxworks (VxWorks code refactored  #128817)
• powerpc64le-unknown-linux-musl (Promote powerpc64le-unknown-linux-musl to tier 2 with host tools #133801)
• powerpc64-ibm-aix
• riscv32gc-unknown-linux-gnu
• riscv32gc-unknown-linux-musl
• riscv32im-risc0-zkvm-elf
• riscv32imac-unknown-xous-elf
• riscv64gc-unknown-freebsd
• riscv64gc-unknown-fuchsia
• riscv64gc-unknown-linux-musl
• riscv64-linux-android
• s390x-unknown-linux-musl
• thumbv7a-pc-windows-msvc (Fill out missing Windows support information #126449)
• thumbv7neon-unknown-linux-musleabihf
• wasm64-unknown-unknown
• x86_64-unknown-l4re-uclibc (Revive L4Re target #150885)
• x86_64-wrs-vxworks (Add myself as VxWorks target maintainer for reference #128431)
• xtensa-esp32-none-elf (Add std Xtensa targets support #126380)
• xtensa-esp32s2-none-elf (Add std Xtensa targets support #126380)
• xtensa-esp32s3-none-elf (Add std Xtensa targets support #126380)

[ChrisDenton]

@semarie, does powerpc-unknown-openbsd have std support? Does it support running rustc on the powerpc?

[semarie]

Regarding powerpc-unknown-openbsd, currently there is no support on OpenBSD by any OpenBSD developers. It was added in rust by @Yn0ga in #82733, and I am unaware if it is functional or not.
So I would keep no std support, and no rustc binary.

[ChrisDenton]

Thanks!

@Yn0ga would you be ok being listed as the maintainer for the powerpc-unknown-openbsd target?

[ChrisDenton]

Does anyone know who maintains the freebsd targets? @devnexen, I think you've been actively contributing for freebsd? Do you know which targets have std support? Do any have host tools support? Currently we have 3 freebsd targets with missing information:

• powerpc64le-unknown-freebsd
• powerpc-unknown-freebsd
• riscv64gc-unknown-freebsd

[semarie]

for FreeBSD, I would ping @asomers , @MikaelUrankar or @dankm (the commiters list in freebsd ports tree could found from https://github.com/freebsd/freebsd-ports/commits/main/lang/rust). the mail contact is rust@FreeBSD.org .

[asomers]

@ChrisDenton I don't work on rustc itself. But does the fact that I can do cargo check -Zbuild-std successfully for all three targets mean that they do have std support? I think it does.

[ChrisDenton]

Thanks @asomers! Successfully checking std is definitely a good sign. Though for maintenance purposes it's also good to know there's someone to willing to do maintenance should things break, Could someone from FreeBSD fill out contact information? E.g. we have a page for OpenBSD and NetBSD. If you'd like I can make a PR, I just need to know what to write.

[Noratrieb]

i think it makes sense to wait for # #121051 with this effort. it will make it easier to track and will avoid duplicated effort of first adding docs and then migrating them.
if you want to help out getting that PR merged, ping me somewhere

[asomers]

Yes @ChrisDenton you can put me down. Also, use rust@FreeBSD.org as a fallback.

[Yn0ga]

Chris, Thanks for reaching out. Unfortunately I'm really far from OpenBSD and rust these days (and from computing in general) so I'm afraid I won't be a really good fit for the role. Sorry about the let down. Take Care.

…

-------- Message d'origine -------- Le 14/06/2024 07:50, Chris Denton a écrit :

Thanks! ***@***.***(https://github.com/Yn0ga) would you be ok being listed as the maintainer for the target? — Reply to this email directly, [view it on GitHub](#126451 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AERSMYZ4HXDYGFAH7NTMWF3ZHKAD5AVCNFSM6AAAAABJJNFIBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRXGI2TSMJZGM). You are receiving this because you were mentioned.Message ID: ***@***.***>