-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Promote powerpc-unknown-linux-musl to Tier 2 target #106932
Comments
@est31 Thx, but my question also is couldn't this be handled by the same compiler team etc as the already existing powerpc-unknown-linux-gnu? I want to bring attention to this issue (to hopefully attract people that could be maintainers etc) shouldn't ideally be a tracking issue for that? is that what you mean by Major Change Proposal? How and where would i go about creating that? |
The tier policy linked answers why: promoting a target from tier 3 to tier 2 increases the burden on every PR submitted to rustc, because after that, it is no longer acceptable to make a change that causes the target to no longer build, even if it doesn't have to pass most tests. That means it is not acceptable to not have someone who can answer questions about how it should be fixed. When a target is no longer maintainable at a higher tier, it may be demoted to tier 3, or even removed entirely. This has certainly happened before. It has even happened to tier 1 targets. The musl targets do require additional maintenance support because they don't have the same build requirements as the GNU targets. MCPs are described here: |
I am going to close this as not a bug; if you know someone willing to be a target maintainer for |
I was wondering why powerpc-unknown-linux-musl isn't a Tier 2 target yet, as i understand it it is very similar to the Promote powerpc-unknown-linux-gnu target, only difference is the C library
Was hoping that there could be a tracking issue for this, but somewhat unsure about whom to ask this question to.
As compiler already supports this target what is lacking here, std library support?
The text was updated successfully, but these errors were encountered: