diff options
| author | Stuart Cook <Zalathar@users.noreply.github.com> | 2024-10-08 13:19:43 +1100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-08 13:19:43 +1100 |
| commit | e416a9cf4e09ae58431175e3408b582ab289e9a8 (patch) | |
| tree | fd93494c5eafe118b1e55d768881b7487efa4a8c /tests/coverage/branch/while.rs | |
| parent | 4d638960186c3ee5485a1e0738e4a5c3df5ef62b (diff) | |
| parent | 51537c686c16121aecb5a2b916a1c91a68d60770 (diff) | |
| download | rust-e416a9cf4e09ae58431175e3408b582ab289e9a8.tar.gz rust-e416a9cf4e09ae58431175e3408b582ab289e9a8.zip | |
Rollup merge of #131170 - madsmtm:target-info-esp32-vendor, r=workingjubilee
Fix `target_vendor` in non-IDF Xtensa ESP32 targets `rustc`'s Xtensa ESP32 targets are the following: - `xtensa-esp32-none-elf` - `xtensa-esp32-espidf` - `xtensa-esp32s2-none-elf` - `xtensa-esp32s2-espidf` - `xtensa-esp32s3-none-elf` - `xtensa-esp32s3-espidf` The ESP-IDF targets already set `target_vendor="espressif"`, however, the ESP32 is, from my understanding, produced by Espressif regardless of whether using the IDF or not, so we should set the target vendor there as well?
Diffstat (limited to 'tests/coverage/branch/while.rs')
0 files changed, 0 insertions, 0 deletions