-
Notifications
You must be signed in to change notification settings - Fork 214
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
compiler_builtins 0.1.20 (likely) broke xargo compilation #322
Comments
Or maybe that breakage is expected? Are compiler_builtins updates semver-compatible in the sense that old compilers can still work when using newer compiler_builtins? |
Most likely cause: #311 |
alexcrichton
added a commit
to alexcrichton/compiler-builtins
that referenced
this issue
Nov 11, 2019
Don't emit the intrinsics for platforms which don't actually have the instructions to do atomic loads/stores. Closes rust-lang#322
I think this should be fixed with #324, and when merged I'll make a new release. Thanks for the report! |
alexcrichton
added a commit
that referenced
this issue
Nov 11, 2019
Don't emit the intrinsics for platforms which don't actually have the instructions to do atomic loads/stores. Closes #322
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since compiler_builtins 0.1.20 was released, Miri is broken on macOS and Windows as xargo fails to build libstd. (Currently latest xargo ignores the lockfile, so it will always build libstd with the latest version of all involved crates. A fix for that is hopefully going to be released soon, but that seems orthogonal.)
On Windows, the error is
and on macOS, it starts with
The text was updated successfully, but these errors were encountered: