Add default compiler prefixes for thumbv7a/thumbv7r/thumbv8r bare-metal targets#1742
Conversation
NobodyXu
left a comment
There was a problem hiding this comment.
Thanks! Just a question
| "armv7r-none-eabihf" => Some("arm-none-eabi"), | ||
| "armv8r-none-eabihf" => Some("arm-none-eabi"), | ||
| "thumbv7a-none-eabi" => Some("arm-none-eabi"), | ||
| "thumbv7a-none-eabihf" => Some("arm-none-eabi"), |
There was a problem hiding this comment.
The description of the pr linked seems to match it to a arm-none-eabihf, as well as any target ends with hf
|
Thank you so much for your review! I thought so too before, but the existing entries in this match arm already map all eabihf targets to |
|
Thank you! I just remember that we use Line 2384 in b49589a |
These five
Thumb-modebare-metal Arm targets were recently promoted to Tier 2 inrust-lang/rust(MCP is here). Without entries in
get_default_prefix, thecccrate falls back tothe host compiler, which errors on
-mthumb.