Document thumbv7neon-linux-androideabi and thumbv7neon-unknown-linux-gnueabihf #197
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
…gnueabihf The above targets were added in rust-lang/rust#56947 Also correct existing ARM Android entries.
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.
The
thumbv7neon-linux-androideabiandthumbv7neon-unknown-linux-gnueabihftargets were added in rust-lang/rust#56947. The glibc target was added to CI for release via rustup in rust-lang/rust#57862.Also correct existing ARM Android entries. Specifically, the
armv7Android target is a thumb-mode target despite its name (corresponds to armeabi-v7a with thumb enabled in Android) and, AFAICT, thearmAndroid target isn't an ARMv7 target but an ARMv5TE target (corresponds to armeabi in Android).