target tier policy: require ability to produce object code #115217
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update target tier policy to require that targets be able to produce object code with a supported backend. Signed-off-by: David Wood <david@davidtw.co>
rustbot
added
the
S-waiting-on-review
I think we can require or at least recommend this from the start so it applies to new tier-3 platforms. We already have other rules that aren't enforced on legacy targets. |
|
Superseded by #118708. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update target tier policy to require that targets be able to produce object code with a supported backend.
In the discussions around rust-lang/compiler-team#655, there was an open question of what exact requirement to make of tier three targets should be - require a test producing assembly which can be cross-compiled, or just require that it is possible at all. I've opted for the latter in this pull request, just because that's simpler to start with, once we have assembly tests for every existing target, we could update this.
r? @wesleywiser