https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=master 2025-10-02T08:27:48+00:00 2025-10-02T08:27:48+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-10-02T08:27:48+00:00 urn:sha1:92aac1bdf61642cfc99498ca86e663cf53d2039e Support `#[rustc_align_static]` inside `thread_local!` Tracking issue: rust-lang/rust#146177 ```rust thread_local! { #[rustc_align_static(64)] static SO_ALIGNED: u64 = const { 0 }; } ``` This increases the amount of recursion the macro performs (once per attribute in addition to the previous once per item), making it easier to hit the recursion limit. I’ve added workarounds to limit the impact in the case of long doc comments, but this still needs a crater run just in case. r? libs ``@rustbot`` label A-attributes A-macros A-thread-locals F-static_align T-libs 2025-10-01T16:28:18+00:00 Jules Bertholet julesbertholet@quoi.xyz 2025-10-01T15:32:54+00:00 urn:sha1:94f00f4e4a0240bc7b8284c78482e37af252309a 2025-10-01T08:12:44+00:00 ivmarkov ivan.markov@gmail.com 2025-10-01T08:12:44+00:00 urn:sha1:b1c212f8502e8e7fcb66da0e8da98db770cb7c02 2025-09-29T19:42:41+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-09-29T19:42:41+00:00 urn:sha1:8223831942e7668d890955a1a67a69e49c286e3d std: implement `hostname` Resolves https://github.com/rust-lang/libs-team/issues/330 Tracking issue: https://github.com/rust-lang/rust/issues/135142 This is based on rust-lang/rust#135141, but I've reimplemented the UNIX version, which now: * uses `sysconf(_SC_HOST_NAME_MAX)` as an initial buffer length * returns `OutOfMemory` if the `Vec` allocation fails * retries the operation if it detects that the name returned by `gethostname` was truncated Additionally, as part of the rebase, I had to move some WinSock abstractions (initialisation and error access) to `sys::pal` so that they can be accessed from `sys::net::hostname`. CC ``@orowith2os`` (and thank you for your work!) 2025-09-29T08:24:54+00:00 joboet jonasboettiger@icloud.com 2025-09-23T15:14:51+00:00 urn:sha1:97333f8c9a0f774cc8d0025bbc51848e1f60427d 2025-09-29T01:32:14+00:00 bors bors@rust-lang.org 2025-09-29T01:32:14+00:00 urn:sha1:772f380092b30680313b70a622cafc17f03e6bff Skip stack overflow handler for panic=immediate-abort std installs guard pages and a signal handler to ensure that stackoverflows 1) terminate abruptly and 2) print an nice message. Even for panic=immediate-abort, 1) is desirable, we don't want silent data corruption there. But 2) is completely unnecessary, as users deliberately *don't* want nice messages, they want minimum binary size. Therefore, skip the entire guard signal handler setup, which saves a lot of bytes. I tested this with a hello world binary using fat LTO, build-std, panic=immediate-abort, opt-level=s, strip=debuginfo. `size` reports significant savings: ``` text data bss dec hex filename 15252 1032 104 16388 4004 tiny-before 6881 964 48 7893 1ed5 tiny-after2 ``` `nm -U` goes from 71 to 56, getting rid of a bunch of stack overflow related symbols. The disk size goes from `31k` to `24k`. The impact on the error message is minimal, as the message was already missing. before: ``` fish: Job 1, './tiny-so-before' terminated by signal SIGABRT (Abort) ``` after: ``` fish: Job 1, './tiny-so-after' terminated by signal SIGSEGV (Address boundary error) ``` I didn't test the Windows part, but it likely also has savings. 2025-09-28T16:13:10+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-09-28T16:13:10+00:00 urn:sha1:322dca8551ba2e395268ddff9bcf58e0d0479813 std::net: update tcp deferaccept delay type to Duration. See comment [here](https://github.com/rust-lang/rust/issues/119639#issuecomment-2839330337). 2025-09-27T21:05:39+00:00 Jules Bertholet julesbertholet@quoi.xyz 2025-09-27T19:47:06+00:00 urn:sha1:4d32b9a1783343d42a9864fe3d2115daa2cb425e 2025-09-27T14:25:47+00:00 Jeremy Soller jackpot51@gmail.com 2025-09-27T14:25:47+00:00 urn:sha1:760ed37769c4902c97c874d324978472ce02f9ba 2025-09-27T12:16:06+00:00 Noratrieb 48135649+Noratrieb@users.noreply.github.com 2025-09-27T11:37:29+00:00 urn:sha1:660a3486fc6da2c3599a167d73d849178f98bc17 std installs guard pages and a signal handler to ensure that stackoverflows 1) terminate abruptly and 2) print an nice message. Even for panic=immediate-abort, 1) is desirable, we don't want silent data corruption there. But 2) is completely unnecessary, as users deliberately *don't* want nice messages, they want minimum binary size. Therefore, skip the entire guard signal handler setup, which saves a lot of bytes. I tested this with a hello world binary using fat LTO, build-std, panic=immediate-abort, opt-level=s, strip=debuginfo. `size` reports significant savings: ``` text data bss dec hex filename 15252 1032 104 16388 4004 tiny-before 6881 964 48 7893 1ed5 tiny-after2 ``` `nm -U` goes from 71 to 56, getting rid of a bunch of stack overflow related symbols. The disk size goes from `31k` to `24k`. The impact on the error message is minimal, as the message was already missing. before: ``` fish: Job 1, './tiny-so-before' terminated by signal SIGABRT (Abort) ``` after: ``` fish: Job 1, './tiny-so-after' terminated by signal SIGSEGV (Address boundary error) ```