Skip to content

Rollup of 3 pull requests#159553

Closed
jhpratt wants to merge 92 commits into
rust-lang:mainfrom
jhpratt:rollup-ZD6DsAD
Closed

Rollup of 3 pull requests#159553
jhpratt wants to merge 92 commits into
rust-lang:mainfrom
jhpratt:rollup-ZD6DsAD

Conversation

@jhpratt

@jhpratt jhpratt commented Jul 19, 2026

Copy link
Copy Markdown
Member

Successful merges:

r? @ghost

Create a similar rollup

LorrensP-2158466 and others added 30 commits July 12, 2026 13:13
…is is the same behaviour as `posix_fallocate`.

And add tests for `fallocate` based on `posix_fallocate`.
To match the deadlocked diagnostic in both tests, we will need to
call the `libc::read/write()` methods directly.
memcmp: add tests and update comments
This updates the rust-version file to 48c2cee.
FileDescription: make destroy a NOP by default and document the risks
This updates the rust-version file to 55b6bd8.
remove bogus sanity check from weak memory mixed-size logic
Dropped readiness watchers are now removed from the global readiness
interest table when the GC runs.
This updates the rust-version file to 38a0576.
RalfJung and others added 16 commits July 17, 2026 09:24
replace global readiness watcher table by per-FD state
std on Android does vectored I/O at offsets through weak
preadv/pwritev symbols with a raw syscall fallback (bionic gained
them in API level 24). The weak symbols did not resolve under Miri,
so these calls failed. Register them for Android so they land in the
existing shims, and un-skip the Android case in the fs tests.
Resolve preadv/pwritev as weak symbols on Android
More consistent with the default functions for `Read`

Co-Authored-By: Clar Fon <15850505+clarfonthey@users.noreply.github.com>
…clarfonthey

Move `std::io::BufRead` to `alloc::io`

ACP: rust-lang/libs-team#755
Tracking issue: rust-lang#154046
Split From: rust-lang#156527
~~Blocked On: rust-lang#158545

## Description

Moves `std::io::BufRead` to `alloc::io`. This is effectively a direct cut and paste, but with a large diff due to how many implementations need to be moved into `alloc`. Blocked on rust-lang#158545.

---

## Notes

* No AI tooling of any kind was used during the creation of this PR.
* Please see rust-lang#154046 (comment) for a review order and broader context for this PR.
…=jhpratt

Remove SIZE generic param from DisplayBuffer in core::net

These symbols were observed on the surface of `core.o`:
```
<core::net::display_buffer::DisplayBuffer<15> as core::fmt::Write>::write_char
<core::net::display_buffer::DisplayBuffer<15> as core::fmt::Write>::write_fmt
<core::net::display_buffer::DisplayBuffer<15> as core::fmt::Write>::write_str
<core::net::display_buffer::DisplayBuffer<21> as core::fmt::Write>::write_char
<core::net::display_buffer::DisplayBuffer<21> as core::fmt::Write>::write_fmt
<core::net::display_buffer::DisplayBuffer<21> as core::fmt::Write>::write_str
<core::net::display_buffer::DisplayBuffer<39> as core::fmt::Write>::write_char
<core::net::display_buffer::DisplayBuffer<39> as core::fmt::Write>::write_fmt
<core::net::display_buffer::DisplayBuffer<39> as core::fmt::Write>::write_str
<core::net::display_buffer::DisplayBuffer<58> as core::fmt::Write>::write_char
<core::net::display_buffer::DisplayBuffer<58> as core::fmt::Write>::write_fmt
<core::net::display_buffer::DisplayBuffer<58> as core::fmt::Write>::write_str
```
There's no reason to instantiate four different copies of this super simple logic, so remove the size parameter allowing each case to call into the same shared machine code.

It's not possible to inline these symbols into the `{SocketAddrV*,Ipv*Addr}::fmt` methods because `core::fmt::write` constructs a `&mut dyn fmt::Write` to the `DisplayBuffer`.
@rust-bors rust-bors Bot added the rollup A PR which is a rollup label Jul 19, 2026
@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output. labels Jul 19, 2026
@jhpratt

jhpratt commented Jul 19, 2026

Copy link
Copy Markdown
Member Author

@bors r+ rollup=never p=5

@rust-bors

rust-bors Bot commented Jul 19, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 0c864c8 has been approved by jhpratt

It is now in the queue for this repository.

@rust-bors rust-bors Bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 19, 2026
@jhpratt jhpratt closed this Jul 19, 2026
@rust-bors rust-bors Bot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Jul 19, 2026
@rust-bors

rust-bors Bot commented Jul 19, 2026

Copy link
Copy Markdown
Contributor

This pull request was unapproved due to being closed.

@jhpratt
jhpratt deleted the rollup-ZD6DsAD branch July 19, 2026 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

rollup A PR which is a rollup S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output.

Projects

None yet

Development

Successfully merging this pull request may close these issues.