Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Complete tier 3 target information #126451

Open
16 of 49 tasks
ChrisDenton opened this issue Jun 14, 2024 · 17 comments
Open
16 of 49 tasks

Complete tier 3 target information #126451

ChrisDenton opened this issue Jun 14, 2024 · 17 comments
Labels
A-targets Area: Concerning the implications of different compiler targets C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@ChrisDenton
Copy link
Member

ChrisDenton commented Jun 14, 2024 •
edited
Loading

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
Beta Give feedback
@rustbot rustbot added the needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. label Jun 14, 2024
@ChrisDenton ChrisDenton added T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC and removed needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. labels Jun 14, 2024
@ChrisDenton
Copy link
Member Author

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

@jieyouxu jieyouxu added the A-targets Area: Concerning the implications of different compiler targets label Jun 14, 2024
@semarie
Copy link
Contributor

semarie commented Jun 14, 2024 •
edited
Loading

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
Copy link
Member Author

ChrisDenton commented Jun 14, 2024 •
edited
Loading

Thanks!

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

@ChrisDenton
Copy link
Member Author

ChrisDenton commented Jun 14, 2024 •
edited
Loading

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
Copy link
Contributor

semarie commented Jun 14, 2024

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 [email protected] .

@asomers
Copy link
Contributor

asomers commented Jun 14, 2024

@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
Copy link
Member Author

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.

@ChrisDenton ChrisDenton mentioned this issue Jun 14, 2024
Merged
@Noratrieb
Copy link
Member

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
Copy link
Contributor

asomers commented Jun 14, 2024

Yes @ChrisDenton you can put me down. Also, use [email protected] as a fallback.

@Yn0ga
Copy link
Contributor

Yn0ga commented Jun 14, 2024 via email

@ChrisDenton
Copy link
Member Author

Yes @ChrisDenton you can put me down. Also, use [email protected] as a fallback.

Thanks!

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.

No worries! Thanks for responding so quickly.

@bjorn3
Copy link
Member

bjorn3 commented Jun 16, 2024

#126192 will add target information for all Redox OS targets (both tier 2 and tier 3).

matthiaskrgr added a commit to matthiaskrgr/rust that referenced this issue Jun 20, 2024
@matthiaskrgr
Rollup merge of rust-lang#126481 - ChrisDenton:powerpc-unkown-openbsd…
a8d641f 
…, r=ehuss

Add `powerpc-unknown-openbsd` maintaince status

As noted in rust-lang#126451 (comment) `powerpc-unknown-openbsd` is not maintained by the OpenBSD devs. If a maintainer is found this can be updated with their information but we should document the current status and note explicitly that it's different from other OpenBSD targets.
workingjubilee added a commit to workingjubilee/rustc that referenced this issue Jun 21, 2024
@workingjubilee
Rollup merge of rust-lang#126481 - ChrisDenton:powerpc-unkown-openbsd…
7ba62e3 
…, r=ehuss

Add `powerpc-unknown-openbsd` maintaince status

As noted in rust-lang#126451 (comment) `powerpc-unknown-openbsd` is not maintained by the OpenBSD devs. If a maintainer is found this can be updated with their information but we should document the current status and note explicitly that it's different from other OpenBSD targets.
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this issue Jun 21, 2024
@matthiaskrgr
Rollup merge of rust-lang#126481 - ChrisDenton:powerpc-unkown-openbsd…
854fa51 
…, r=ehuss

Add `powerpc-unknown-openbsd` maintenance status

As noted in rust-lang#126451 (comment) `powerpc-unknown-openbsd` is not maintained by the OpenBSD devs. If a maintainer is found this can be updated with their information but we should document the current status and note explicitly that it's different from other OpenBSD targets.
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this issue Jun 21, 2024
@matthiaskrgr
Rollup merge of rust-lang#126481 - ChrisDenton:powerpc-unkown-openbsd…
0c1d396 
…, r=ehuss

Add `powerpc-unknown-openbsd` maintenance status

As noted in rust-lang#126451 (comment) `powerpc-unknown-openbsd` is not maintained by the OpenBSD devs. If a maintainer is found this can be updated with their information but we should document the current status and note explicitly that it's different from other OpenBSD targets.
rust-timer added a commit to rust-lang-ci/rust that referenced this issue Jun 21, 2024
@rust-timer
Unrolled build for rust-lang#126481
ad073c6 
Rollup merge of rust-lang#126481 - ChrisDenton:powerpc-unkown-openbsd, r=ehuss

Add `powerpc-unknown-openbsd` maintenance status

As noted in rust-lang#126451 (comment) `powerpc-unknown-openbsd` is not maintained by the OpenBSD devs. If a maintainer is found this can be updated with their information but we should document the current status and note explicitly that it's different from other OpenBSD targets.
flip1995 pushed a commit to flip1995/rust-clippy that referenced this issue Jun 28, 2024
@matthiaskrgr
Rollup merge of #126481 - ChrisDenton:powerpc-unkown-openbsd, r=ehuss
a140120 
Add `powerpc-unknown-openbsd` maintenance status

As noted in rust-lang/rust#126451 (comment) `powerpc-unknown-openbsd` is not maintained by the OpenBSD devs. If a maintainer is found this can be updated with their information but we should document the current status and note explicitly that it's different from other OpenBSD targets.
@biabbas
Copy link
Contributor

biabbas commented Aug 2, 2024

All 6 vxworks targets platform support information is updated with pr #128431

@ChrisDenton
Copy link
Member Author

Except for powerpc64-wrs-vxworks?

@biabbas
Copy link
Contributor

biabbas commented Aug 2, 2024

Except for powerpc64-wrs-vxworks?

We're not actively working on rust for VxWorks PowerPC targets. They are not built or shipped with the current VxWorks workbench.

@biabbas
Copy link
Contributor

biabbas commented Aug 2, 2024

I missed powerpc64-wrs-vxworks during that pr.

@biabbas biabbas mentioned this issue Aug 2, 2024
Closed
@ChrisDenton ChrisDenton mentioned this issue Aug 2, 2024
Closed
@biabbas
Copy link
Contributor

biabbas commented Sep 2, 2024

commit 1e3ea29 completes platform support documentation for VxWorks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-targets Area: Concerning the implications of different compiler targets C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@asomers @ChrisDenton @semarie @bjorn3 @Yn0ga @jieyouxu @rustbot @Noratrieb @biabbas