Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow atomic operations up to 32 bits #44978

Merged
merged 1 commit into from
Oct 8, 2017
Merged

Allow atomic operations up to 32 bits #44978

merged 1 commit into from
Oct 8, 2017

Commits on Oct 2, 2017

  1. Allow atomic operations up to 32 bits 

    The ARMv5te platform does not have instruction-level support for atomics, however the kernel provides [user space helpers](https://www.kernel.org/doc/Documentation/arm/kernel_user_helpers.txt) which can be used to perform atomic operations. When linked with `libc`, the atomic symbols needed by Rust will be provided, rather than CPU level intrinsics.

As this target is specifically `linux` and `gnueabi`, it is reasonable to assume the Linux Kernel and libc will be available for the target. There is a large performance penalty, as we are not using CPU level intrinsics, however this penalty is likely preferable to not having the target at all.

I have used this change in a custom target (along with `xargo`) to build `std`, as well as a number of higher level crates.
    @jamesmunns
    jamesmunns committed Oct 2, 2017
    Configuration menu
    Copy the full SHA
    1e26094 View commit details
    Browse the repository at this point in the history