Uh oh!
There was an error while loading. Please reload this page.
Vxworks / Unix deduplication - #77666
Conversation
rust-highfive
commented
Oct 7, 2020
r? @dtolnay (rust_highfive has picked a reviewer for you, use r? to override) |
m-ou-se
commented
Oct 7, 2020
Cc @BaoshanPang |
tesuji
commented
Oct 8, 2020
This is nice, however there is no CI for Vxworks (tier 3). |
m-ou-se
commented
Oct 8, 2020
Yup, I noticed. Keeping an oudated copy of |
bors
commented
Oct 9, 2020
☔ The latest upstream changes (presumably #77674) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels: |
618340e to
7592d97Compare
dtolnay
left a comment
There was a problem hiding this comment.
Thanks!
Accepting without particular scrutiny beyond confirming that every thing changed in the PR is gated with target_os = "vxworks".
dtolnay
commented
Oct 15, 2020
@bors r+ |
bors
commented
Oct 15, 2020
📌 Commit 7592d97c1213273b80337324049082cd3c9315ca has been approved by |
bors
commented
Oct 16, 2020
☔ The latest upstream changes (presumably #78001) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels: |
m-ou-se
commented
Oct 16, 2020
@rustbot modify labels: +S-waiting-on-review -S-waiting-on-author |
dtolnay
commented
Oct 16, 2020
@bors r+ |
bors
commented
Oct 16, 2020
📌 Commit 0f0257b has been approved by |
bors
commented
Oct 16, 2020
bors
commented
Oct 16, 2020
☀️ Test successful - checks-actions, checks-azure |
Move `sys::vxworks` code to `sys::unix` Follow-up to rust-lang#77666, `sys::vxworks` is almost identical to `sys::unix`, the only differences are the `rand`, `thread_local_dtor`, and `process` implementation. Since `vxworks` is `target_family = unix` anyway, there is no reason for the code not to live inside of `sys::unix` like all the other unix-OSes. https://github.com/rust-lang/rust/blob/e41f378f825488a537b024fc3ed599d9c12fda96/compiler/rustc_target/src/spec/vxworks_base.rs#L12 `@rustbot` label: +T-libs-impl
Move `sys::vxworks` code to `sys::unix` Follow-up to rust-lang#77666, `sys::vxworks` is almost identical to `sys::unix`, the only differences are the `rand`, `thread_local_dtor`, and `process` implementation. Since `vxworks` is `target_family = unix` anyway, there is no reason for the code not to live inside of `sys::unix` like all the other unix-OSes. https://github.com/rust-lang/rust/blob/e41f378f825488a537b024fc3ed599d9c12fda96/compiler/rustc_target/src/spec/vxworks_base.rs#L12 ``@rustbot`` label: +T-libs-impl
sys/vxworkswas almost entirely an (outdated) copy ofsys/unix. I went through every file to check the differences and tried to figure out if they were simply outdated or intentional differences betweenunixandvxworks. Most of them did not have anyvxworks-specific changes, so are deleted. I've added some minorcfg(target_os = "vxworks")-specific things tosys/unixto allow for deduplication.Before this change, the vxworks target didn't compile because its outdated process implementation did not match the expected interface anymore. This also fixes that:
stdcompiles again forx86_64-wrs-vxworks.It's probably good to merge
sys/vxworksentirely intosys/unix, but it might be better to to that in a follow-up PR.@rustbot modify labels: +T-libs +C-cleanup