about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src/errors.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2024-10-09 16:43:06 +0000
committerbors <bors@rust-lang.org>2024-10-09 16:43:06 +0000
commit5cdee0781fb5d2b3dd4064a101402dad575fa773 (patch)
tree7dda8d4ba2f2a3643df9fa6e96865fc73934c965 /compiler/rustc_codegen_llvm/src/errors.rs
parent8e8dd57ac26ce4af9172e19e4059f8b67aece7fa (diff)
parent45606066029ece21e5df869c52419df7a6c3990a (diff)
downloadrust-5cdee0781fb5d2b3dd4064a101402dad575fa773.tar.gz
rust-5cdee0781fb5d2b3dd4064a101402dad575fa773.zip
Auto merge of #3946 - FrankReh:fix-over-synchronization-of-epoll, r=RalfJung
Fix over synchronization of epoll

Fixes #3944.

The clock used by epoll is now per event generated, rather than by the `epoll's` ready_list.

The same epoll tests that existed before are unchanged and still pass. Also the `tokio` test case we had worked on last week still passes with this change.

This change does beg the question of how the epoll event states should change. Perhaps rather than expose public crate bool fields, so setters should be provided that include a clock parameter or an optional clock parameter. Also should all the epoll event possibilities have their clock sync tested the way these commit lay out testing. In this first go around, only the pipe's EPOLLIN is tested. The EPOLLOUT might deserve testing too, as would the eventfd. Any future source of epoll events would also fit into that category.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions