https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.85.0 2025-01-26T00:48:11+00:00 2025-01-26T00:48:11+00:00 Chris Denton chris@chrisdenton.dev 2025-01-21T17:27:24+00:00 urn:sha1:5f5e70bfc6391374546a2fd240d8612717af69f4 (cherry picked from commit fed5f98c47e64bc5e96679165d16e5eec8b4917e) 2025-01-01T12:21:19+00:00 Kleis Auke Wolthuizen github@kleisauke.nl 2024-12-09T14:09:34+00:00 urn:sha1:b6af0c483672e87a815755beec57f0e30cc4a84f Align it with musl, which also prefers using lstat() here. 2025-01-01T12:21:19+00:00 Kleis Auke Wolthuizen github@kleisauke.nl 2024-12-09T14:06:31+00:00 urn:sha1:ef58e8b989a4c191c08005b7a8ce12f8ef697a43 Since Emscripten uses musl libc internally. Non-functional change: all LFS64 symbols were aliased to their non-LFS64 counterparts in rust-lang/libc@7c952dceaad4cdc35e00884fcb12a713d41a87e0. 2024-12-28T13:49:45+00:00 bors bors@rust-lang.org 2024-12-28T13:49:45+00:00 urn:sha1:3c1e750364012e78dcc46e5c96973fab42c7b295 Unify fs::copy and io::copy on Linux Currently, `fs::copy` first tries a regular file copy (via copy_file_range) and then falls back to userspace read/write copying. We should use `io::copy` instead as it tries copy_file_range, sendfile, and splice before falling back to userspace copying. This was discovered here: https://github.com/SUPERCILEX/fuc/issues/40 Perf impact: `fs::copy` will now have two additional statx calls to decide which syscall to use. I wonder if we should get rid of the statx calls and only continue down the next fallback when the relevant syscalls say the FD isn't supported. 2024-12-27T13:01:07+00:00 bors bors@rust-lang.org 2024-12-27T13:01:07+00:00 urn:sha1:6d3db555e614eb50bbb40559e696414e69b6eff9 Rollup of 8 pull requests Successful merges: - #134606 (ptr::copy: fix docs for the overlapping case) - #134622 (Windows: Use WriteFile to write to a UTF-8 console) - #134759 (compiletest: Remove the `-test` suffix from normalize directives) - #134787 (Spruce up the docs of several queries related to the type/trait system and const eval) - #134806 (rustdoc: use shorter paths as preferred canonical paths) - #134815 (Sort triples by name in platform_support.md) - #134816 (tools: fix build failure caused by PR #134420) - #134819 (Fix mistake in windows file open) r? `@ghost` `@rustbot` modify labels: rollup 2024-12-27T12:44:15+00:00 许杰友 Jieyou Xu (Joe) 39484203+jieyouxu@users.noreply.github.com 2024-12-27T12:44:15+00:00 urn:sha1:5544091054f6496b7e98258cc3725e3e7ef1fc26 Fix mistake in windows file open In #134722 this should have been `c::FileAllocationInfo` not `c::FileEndOfFileInfo`. Oops. 2024-12-27T12:44:11+00:00 许杰友 Jieyou Xu (Joe) 39484203+jieyouxu@users.noreply.github.com 2024-12-27T12:44:11+00:00 urn:sha1:7bbbfc650dd9ab474a1d79dcf127e91022e0422e Windows: Use WriteFile to write to a UTF-8 console If the console code page is UTF-8 then we can simply write to it without needing to convert to UTF-16 and calling `WriteConsole`. 2024-12-27T10:14:53+00:00 bors bors@rust-lang.org 2024-12-27T10:14:53+00:00 urn:sha1:42591a4cc0ccfc487b5f0813a77c79137fd10eb5 Fix renaming symlinks on Windows Previously we only detected mount points and not other types of links when determining reparse point behaviour. Also added some tests to avoid this regressing again in the future. 2024-12-27T10:07:10+00:00 Chris Denton chris@chrisdenton.dev 2024-12-26T12:03:37+00:00 urn:sha1:54b130afa268f886bddb93e7cf086c75ae0f1529 Previously we only detected mount points and not other types of links when determining reparse point behaviour. 2024-12-27T09:20:37+00:00 Chris Denton chris@chrisdenton.dev 2024-12-24T11:04:12+00:00 urn:sha1:0af396f183b815be2b9905faee499c5cddf1c0b9