You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately my attempts to reproduce it at smaller scale in non-esp rust so far have failed, for now I'm assuming it's esp specific.
I'll continue trying to find the root cause minimal example, if found to be in mainline rust, I'll move the issue over there.
This seems to be allowed in >1.80 without import, but in release mode can cause an rustc/LLVM SIGSEGV. Changing it to an explicit import fixes this.
Meta
This is the version I originally found it in but it identical errors occurs in 1.80.0.
I'd be happy to look into this, even without a min repro, any repro will do because we have a backtrace (I'll do a local custom build of rust/LLVM with debugging symbols).
Side note: i404788/embassy@3b540cf 👀, you're working on a host driver in embassy!? Very cool, and very cool that you're using an s3 to develop it :D
Thanks, I'll be submitting my PR to esp-hal when the embassy side is sorted, we are having a mini working group @ embassy-rs/embassy#3307 to get traits & drivers across platforms aligned.
I've gotten the repro down to a managable size (https://github.com/i404788/rust-compile-crash-repro); it seems like maybe it has to do with the async_closure feature, but I've also included main.not.rs which also uses them but doesn't cause an issue (need to clean if coming from broken), Also I maybe got the wrong commit, at that point it is fixed but i404788/embassy@df729bf is the confirmed broken one, so it's possible i404788/embassy@dd408d4 fixed it.
Code
This commit fixes it in the project I originally used it in: i404788/embassy@3b540cf
Unfortunately my attempts to reproduce it at smaller scale in non-esp rust so far have failed, for now I'm assuming it's esp specific.
I'll continue trying to find the root cause minimal example, if found to be in mainline rust, I'll move the issue over there.
This seems to be allowed in >1.80 without import, but in release mode can cause an rustc/LLVM SIGSEGV. Changing it to an explicit import fixes this.
Meta
This is the version I originally found it in but it identical errors occurs in 1.80.0.
rustc --version --verbose
:Error output
RUST_BACKTRACE=1
has no effectThe text was updated successfully, but these errors were encountered: