diff options
| author | bors <bors@rust-lang.org> | 2020-12-10 03:11:27 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2020-12-10 03:11:27 +0000 |
| commit | e413d89aa706060ddc347e1e06d551ec86d3f471 (patch) | |
| tree | c8ba4949a30607d1a8ae938c67ec67f6f0bb5547 /compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp | |
| parent | 58d2bad9f7ab0971495247b6c94978848760ca9d (diff) | |
| parent | 7647d03c33339bd85a1665047b22ae7e800fee98 (diff) | |
| download | rust-e413d89aa706060ddc347e1e06d551ec86d3f471.tar.gz rust-e413d89aa706060ddc347e1e06d551ec86d3f471.zip | |
Auto merge of #79274 - the8472:probe-eperm, r=nagisa
implement better availability probing for copy_file_range Followup to https://github.com/rust-lang/rust/pull/75428#discussion_r469616547 Previously syscall detection was overly pessimistic. Any attempt to copy to an immutable file (EPERM) would disable copy_file_range support for the whole process. The change tries to copy_file_range on invalid file descriptors which will never run into the immutable file case and thus we can clearly distinguish syscall availability.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp')
0 files changed, 0 insertions, 0 deletions