<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/library/std/src/thread, branch stable</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=stable</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=stable'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2025-07-29T10:19:51+00:00</updated>
<entry>
<title>Rollup merge of #144500 - joboet:thread-name-stack-overflow, r=ChrisDenton</title>
<updated>2025-07-29T10:19:51+00:00</updated>
<author>
<name>Stuart Cook</name>
<email>Zalathar@users.noreply.github.com</email>
</author>
<published>2025-07-29T10:19:51+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=4bfbd80babd7186598afae348023580c06a28109'/>
<id>urn:sha1:4bfbd80babd7186598afae348023580c06a28109</id>
<content type='text'>
thread name in stack overflow message

Fixes rust-lang/rust#144481, which is caused by the thread name not being initialised yet when setting up the stack overflow information. Unfortunately, the stack overflow UI test did not test for the correct thread name being present, and testing this separately didn't occur to me when writing https://github.com/rust-lang/rust/pull/140628.

This PR contains the smallest possible fix I could think of: passing the thread name explicitly to the platform thread creation function. In the future I'd very much like to explore some possibilities around merging the thread packet and thread handle into one structure and using that in the platform code instead – but that's best left for another PR.

This PR also amends the stack overflow test to check for thread names, so we don't run into this again.

``@rustbot`` label +beta-nominated
</content>
</entry>
<entry>
<title>thread name in stack overflow message</title>
<updated>2025-07-28T16:09:35+00:00</updated>
<author>
<name>joboet</name>
<email>jonasboettiger@icloud.com</email>
</author>
<published>2025-07-26T12:29:00+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=73751a04910d08052bf6b825f8829cacba86c648'/>
<id>urn:sha1:73751a04910d08052bf6b825f8829cacba86c648</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rollup merge of #143859 - orlp:thread-into-raw-align, r=jhpratt</title>
<updated>2025-07-26T07:19:29+00:00</updated>
<author>
<name>Trevor Gross</name>
<email>t.gross35@gmail.com</email>
</author>
<published>2025-07-26T07:19:29+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=2fcea9fb68c8e04f10e5cb15bbfb486de9800afa'/>
<id>urn:sha1:2fcea9fb68c8e04f10e5cb15bbfb486de9800afa</id>
<content type='text'>
Guarantee 8 bytes of alignment in Thread::into_raw

When using `AtomicPtr` for synchronization it's incredibly useful when you've got a couple bits you can stuff metadata in. By guaranteeing that `Thread`'s `Inner` struct is aligned to 8 bytes everyone can use the bottom 3 bits to signal other things, such as a critical section, etc.

This guarantee is thus very useful and costs us nothing.
</content>
</entry>
<entry>
<title>Add LocalKey&lt;Cell&gt;::update</title>
<updated>2025-07-15T21:17:57+00:00</updated>
<author>
<name>Cameron Steffen</name>
<email>cam.steffen94@gmail.com</email>
</author>
<published>2025-07-15T19:14:22+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=1120cb2fe54fae7a1a8ccd5beb941f5b207084c0'/>
<id>urn:sha1:1120cb2fe54fae7a1a8ccd5beb941f5b207084c0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Tidy</title>
<updated>2025-07-12T23:20:29+00:00</updated>
<author>
<name>Orson Peters</name>
<email>orsonpeters@gmail.com</email>
</author>
<published>2025-07-12T23:20:29+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=6f4d0bdde85f9e2a0e61bb3e16d407540ddc09ba'/>
<id>urn:sha1:6f4d0bdde85f9e2a0e61bb3e16d407540ddc09ba</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Guarantee 8 bytes of alignment in Thread::into_raw</title>
<updated>2025-07-12T22:58:46+00:00</updated>
<author>
<name>Orson Peters</name>
<email>orsonpeters@gmail.com</email>
</author>
<published>2025-07-12T22:58:12+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=69b9bae57ded527f5fd7f036b6cc1cca0b462ac4'/>
<id>urn:sha1:69b9bae57ded527f5fd7f036b6cc1cca0b462ac4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Auto merge of #141829 - dvdsk:sleep_until_linux, r=cuviper,RalfJung</title>
<updated>2025-07-06T23:00:51+00:00</updated>
<author>
<name>bors</name>
<email>bors@rust-lang.org</email>
</author>
<published>2025-07-06T23:00:51+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=ca98d4d4b3114116203699c2734805547df86f9a'/>
<id>urn:sha1:ca98d4d4b3114116203699c2734805547df86f9a</id>
<content type='text'>
Specialize sleep_until implementation for unix (except mac)

related tracking issue: https://github.com/rust-lang/rust/issues/113752
Supersedes https://github.com/rust-lang/rust/pull/118480 for the reasons see: https://github.com/rust-lang/rust/issues/113752#issuecomment-2902594469

Replaces the generic catch all implementation with target_os specific ones for: linux/netbsd/freebsd/android/solaris/illumos etc. Other platforms like wasi, macos/ios/tvos/watchos and windows will follow in later separate PR's (once this is merged).
</content>
</entry>
<entry>
<title>sleep_until: use clock_nanosleep where possible</title>
<updated>2025-07-06T15:36:49+00:00</updated>
<author>
<name>dvdsk</name>
<email>noreply@davidsk.dev</email>
</author>
<published>2025-05-31T13:33:46+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=f24ee2c9b15dc3734e9ebd74ba0563a1e6c545db'/>
<id>urn:sha1:f24ee2c9b15dc3734e9ebd74ba0563a1e6c545db</id>
<content type='text'>
Using clock nanosleep leads to more accurate sleep times on platforms
where it is supported.

To enable using clock_nanosleep this makes `sleep_until` platform
specific. That unfortunatly requires identical placeholder
implementations for the other platforms (windows/mac/wasm etc).

we will land platform specific implementations for those later. See the
`sleep_until` tracking issue.

This requires an accessors for the Instant type. As that accessor is only
used on the platforms that have clock_nanosleep it is marked as allow_unused.

32bit time_t targets do not use clock_nanosleep atm, they instead rely
on the same placeholder as the other platforms. We could make them
use clock_nanosleep too in the future using `__clock_nanosleep_time64`.

__clock_nanosleep_time64 is documented at:
https://www.gnu.org/software/libc/manual/html_node/64_002dbit-time-symbol-handling.html
</content>
</entry>
<entry>
<title>setup CI and tidy to use typos for spellchecking and fix few typos</title>
<updated>2025-07-03T07:51:06+00:00</updated>
<author>
<name>klensy</name>
<email>klensy@users.noreply.github.com</email>
</author>
<published>2024-12-07T10:51:08+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=c76d032f0144b650a438ee1efba89c475e0b115b'/>
<id>urn:sha1:c76d032f0144b650a438ee1efba89c475e0b115b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>update cfg(bootstrap)</title>
<updated>2025-05-12T13:33:37+00:00</updated>
<author>
<name>Pietro Albini</name>
<email>pietro@pietroalbini.org</email>
</author>
<published>2025-05-10T08:51:12+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=2ce08ca5d6046600ff641bfa4018247f3b9451c5'/>
<id>urn:sha1:2ce08ca5d6046600ff641bfa4018247f3b9451c5</id>
<content type='text'>
</content>
</entry>
</feed>
