diff options
| author | bors <bors@rust-lang.org> | 2024-07-06 12:30:31 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-07-06 12:30:31 +0000 |
| commit | 838b8d5898711fb3e8e8fe3fd51edbbd72f9e20d (patch) | |
| tree | d48d766f44a893375b91cf61f29cfca2aebf9d19 /tests/coverage/branch/lazy-boolean.coverage | |
| parent | d358f5dcf9df582a9c8a28c647b11d1f99d626bc (diff) | |
| parent | d65e3688df6a282667aed91cea2c7ecfeb636313 (diff) | |
| download | rust-838b8d5898711fb3e8e8fe3fd51edbbd72f9e20d.tar.gz rust-838b8d5898711fb3e8e8fe3fd51edbbd72f9e20d.zip | |
Auto merge of #3698 - folkertdev:sched-setaffinity, r=RalfJung
implement `libc::sched_setaffinity` on linux fixes https://github.com/rust-lang/miri/issues/2749 the implementation, like `libc::sched_getaffinity`, just always returns `EINVAL`, which kind of simulates a device with zero cpus. I believe the idea is that callers of this function always do it to optimize, so they are likely to gracefully recover from this function returning an error. based on the libc crate, these functions are also available on android and freebsd (but not on macos or windows). So should the implementation of the `sched_*` functions just be copied to the android and freebsd shims?
Diffstat (limited to 'tests/coverage/branch/lazy-boolean.coverage')
0 files changed, 0 insertions, 0 deletions