-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
rustc segfaults while translating inline assembly to write memory location #31437
Comments
I've changed the title, as I've managed to reduce test case. |
rustc was built with just |
I'm compiling beta 1.7, will report if it is resolved. |
Can confirm that this happens with 1.7.0-dev as well. |
Debug build shows segfault as a result of failed assertion:
Which leads to the following issues: |
This one looks promising, I will try it out: effcd29 |
On my ARM machine there's no problem using a nightly. You were using an i386 host cross-compiler, right? It duly segfaults under |
Yeah, I haven't tried with nightly, just with v1.6 and v1.7-beta. I will try the nightly as well, perhaps tomorrow.
Correct. Thanks! |
Still segfaults rustc 1.8.0-dev :-(. |
Getting interesting! The rustc I was using was built Feb, 4th from a source snapshot. Other differences between how yours and mine were built (apart from native vs cross) are: |
Interesting, thanks! I will try first with the llvm's patch! |
No, wait - theses details are completely irrelevant. I get the segfault too - the reason I was able to compile was using |
Doesn't even compile on a nightly for 1.13. |
Probably a similar issue so I'll report here:
|
Still segfaults with |
Adding another voice to the chorus pointing out that this is still broken. My example code:
This makes it difficult to give a pedagogical examples of writing interrupt-safe locks in a no_std environment (the Of course, it could be that my assembler is messed up, in which case I'd welcome a correction. :-) |
This issue does not apply to the new The legacy |
Results in:
Backtrace:
rustc:
The text was updated successfully, but these errors were encountered: