-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added custom risc32-imac for esp-espidf target #111369
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @b-naber (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
These commits modify compiler targets. |
r? compiler-team |
The esp-idf platform is already supported, but our initial PR (#87666) didn't have the platform support content (just the mention in platform-support.md), perhaps it was missed or maybe this is a newer thing. I can add this in a separate PR. |
I see, I that case adding the platform support page in a separate PR seems fine. |
Opened #111389 |
This comment has been minimized.
This comment has been minimized.
…=jyn514 Add esp-idf platform-support page As mentioned in rust-lang#111369 (comment), the initial PR for esp-idf didn't include a platform support document which is required for the merge of rust-lang#111369.
☔ The latest upstream changes (presumably #111452) made this pull request unmergeable. Please resolve the merge conflicts. |
@bors Hi!, solved :) |
@Nassiel Could you also update the table inside |
@MabezDev Please validate the changes on |
@bors rollup |
@Nassiel: 🔑 Insufficient privileges: not in try users |
Hi @oli-obk do you have any clue of when this will be included? |
Please rebase over the latest master so the merge commits go away and squash all your commits |
@rustbot author |
@bors r+ |
📌 Commit 947af4223a53157239605c08b0dbac224a699288 has been approved by It is now in the queue for this repository. |
Not done. |
@bors r- |
Key part of request was |
@Nassiel -- In case you're not familiar, it's as simple as: I'm looking forward to this going in so I don't need to deal with a custom build 🙂 |
Or I'm doing something very wrong, or it fails everywhere. I merged from the master to this branch because there was a PR in parallel that modified my own files, so I needed to solve the conflict. Every time I try to do the squash, Git complains that I'm trying to squash a merge and that cannot be done. So I took the middle street, redo all the changes from the source again, and did a push force. Now it's only ONE commit without merges. Hope now it's compliance with the policies. @klensy @oli-obk Honestly, I though this was a very stupid PR but it took a lot much more work than I expected for 4 files. |
Thanks. Sorry about the git pains. I forgot how it is as I haven't done a regular merge in a long time. @bors r+ |
Added custom risc32-imac for esp-espidf target ESP32-C6 and the upcoming ESP32-P4 are the first Espressif chips that support the "A" (atomic) extension of the RISCV specification. As such, they do not work with the existing `riscv32imc-esp-espidf` target and instead need a new one (in this PR) called `riscv32imac-esp-espidf`.
…iaskrgr Rollup of 7 pull requests Successful merges: - rust-lang#111058 (Correct fortanix LVI test print function) - rust-lang#111369 (Added custom risc32-imac for esp-espidf target) - rust-lang#111962 (Make GDB Python Pretty Printers loadable after spawning GDB, avoiding required `rust-gdb`) - rust-lang#112019 (Don't suggest changing `&self` and `&mut self` in function signature to be mutable when taking `&mut self` in closure) - rust-lang#112199 (Fix suggestion for matching struct with `..` on both ends) - rust-lang#112220 (Cleanup some `EarlyBinder::skip_binder()` -> `EarlyBinder::subst_identity()`) - rust-lang#112325 (diagnostics: do not suggest type name tweaks on type-inferred closure args) r? `@ghost` `@rustbot` modify labels: rollup
ESP32-C6 and the upcoming ESP32-P4 are the first Espressif chips that support the "A" (atomic) extension of the RISCV specification.
As such, they do not work with the existing
riscv32imc-esp-espidf
target and instead need a new one (in this PR) calledriscv32imac-esp-espidf
.