rust/src/libstd/sys/common/thread_info.rs, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2016-11-01T17:08:24+00:00std: Move sys_common to libstd/sys_common2016-11-01T17:08:24+00:00Brian Andersonbanderson@mozilla.com2016-09-30T23:26:44+00:00urn:sha1:ca30691813836e1c6896e5ba5d4397eb717e7270
Make the directory structure reflect the module structure. I've always
found the existing structure confusing.
Use `#[prelude_import]` in `libstd`.2016-08-24T22:12:48+00:00Jeffrey Seyfriedjeffrey.seyfried@gmail.com2016-08-22T19:47:38+00:00urn:sha1:9a2c8783d91624261317316f996d8d2d09b7b6a4Register new snapshots2015-08-11T22:11:13+00:00Alex Crichtonalex@alexcrichton.com2015-08-11T21:31:23+00:00urn:sha1:938099a7ebccbad2a2cad58d71df316d5ccd512c
* Lots of core prelude imports removed
* Makefile support for MSVC env vars and Rust crates removed
* Makefile support for morestack removed
syntax: Implement #![no_core]2015-08-04T00:23:01+00:00Alex Crichtonalex@alexcrichton.com2015-07-30T00:01:14+00:00urn:sha1:5cccf3cd256420d9f32c265e83036dea1d5f94d8
This commit is an implementation of [RFC 1184][rfc] which tweaks the behavior of
the `#![no_std]` attribute and adds a new `#![no_core]` attribute. The
`#![no_std]` attribute now injects `extern crate core` at the top of the crate
as well as the libcore prelude into all modules (in the same manner as the
standard library's prelude). The `#![no_core]` attribute disables both std and
core injection.
[rfc]: https://github.com/rust-lang/rfcs/pull/1184
std: Be resilient to failure in pthread_getattr_np2015-07-21T16:18:30+00:00Alex Crichtonalex@alexcrichton.com2015-07-16T18:59:53+00:00urn:sha1:d68b152c3e2feb6ee18bdf2c992098376dbb528c
This can fail on linux for various reasons, such as the /proc filesystem not
being mounted. There are already many cases where we can't set up stack guards,
so just don't worry about this case and communicate that no guard was enabled.
I've confirmed that this allows the compiler to run in a chroot without /proc
mounted.
Closes #22642
std: Don't assume thread::current() works on panic2015-04-27T23:15:36+00:00Alex Crichtonalex@alexcrichton.com2015-04-15T19:27:05+00:00urn:sha1:d98ab4faf869ff0430ad73260b13ef8e473ef212
Inspecting the current thread's info may not always work due to the TLS value
having been destroyed (or is actively being destroyed). The code for printing
a panic message assumed, however, that it could acquire the thread's name
through this method.
Instead this commit propagates the `Option` outwards to allow the
`std::panicking` module to handle the case where the current thread isn't
present.
While it solves the immediate issue of #24313, there is still another underlying
issue of panicking destructors in thread locals will abort the process.
Closes #24313
Mass rename uint/int to usize/isize2015-03-26T19:10:22+00:00Alex Crichtonalex@alexcrichton.com2015-03-26T00:06:52+00:00urn:sha1:43bfaa4a336095eb5697fb2df50909fd3c72ed14
Now that support has been removed, all lingering use cases are renamed.
Implement RFC 909: move thread_local into thread2015-03-23T18:28:54+00:00Aaron Turonaturon@mozilla.com2015-03-20T07:46:13+00:00urn:sha1:6bd3ab0d8140053475a901ad4e2e80e98955bcb0
This commit implements [RFC
909](https://github.com/rust-lang/rfcs/pull/909):
The `std::thread_local` module is now deprecated, and its contents are
available directly in `std::thread` as `LocalKey`, `LocalKeyState`, and
`ScopedKey`.
The macros remain exactly as they were, which means little if any code
should break. Nevertheless, this is technically a:
[breaking-change]
Closes #23547
std: Remove #[allow] directives in sys modules2015-03-12T17:23:27+00:00Alex Crichtonalex@alexcrichton.com2015-03-10T03:04:35+00:00urn:sha1:c933d44f7bb908aa520250b608f85bfacfccc337
These were suppressing lots of interesting warnings! Turns out there was also
quite a bit of dead code.
Fallout from stabilization2015-02-17T23:14:17+00:00Aaron Turonaturon@mozilla.com2015-02-17T23:10:25+00:00urn:sha1:d0de2b46e9bcca93971ef64d6ecdef872633f246