-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Add notbsd process_vm_readv and process_vm_writev system calls #283
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
60df216
to
1931ee4
Compare
Didn't work on Android, moving to just Linux. |
Add notbsd process_vm_readv and process_vm_writev system calls
💔 Test failed - status-appveyor |
@bors: retry On Wed, May 11, 2016 at 10:03 AM, bors notifications@github.com wrote:
|
Add notbsd process_vm_readv and process_vm_writev system calls
💔 Test failed - travis |
@bors: retry On Wed, May 11, 2016 at 3:14 PM, bors notifications@github.com wrote:
|
🔒 Merge conflict |
☔ The latest upstream changes (presumably #284) made this pull request unmergeable. Please resolve the merge conflicts. |
1931ee4
to
c9496fe
Compare
@alexcrichton rebased! |
Add notbsd process_vm_readv and process_vm_writev system calls
💔 Test failed - travis |
@bors: retry On Thu, May 12, 2016 at 3:13 PM, bors notifications@github.com wrote:
|
Add notbsd process_vm_readv and process_vm_writev system calls
☀️ Test successful - status-appveyor, travis |
Bumped bitflags version to 0.4 and removed warning Bumped bitflags version to 0.4 and removed warning about derive with raw pointer
This commit updates to the latest nightly's syntax where `#[target_feature = "+foo"]` is now deprecated in favor of `#[target_feature(enable = "foo")]`. Additionally `#[target_feature]` can only be applied to `unsafe` functions for now. Along the way this removes a few exampels that were just left around and also disables the `fxsr` modules as that target feature will need to land in upstream rust-lang/rust first as it's currently unknown to the compiler.
No description provided.