rust/src/libstd/sys_common/thread_info.rs, branch try

mv std libs to library/

2020-07-28T00:51:13+00:00

Format libstd with rustfmt

2019-11-30T02:43:27+00:00

This commit applies rustfmt with rust-lang/rust's default settings to files in src/libstd *that are not involved in any currently open PR* to minimize merge conflicts. THe list of files involved in open PRs was determined by querying GitHub's GraphQL API with this script: https://gist.github.com/dtolnay/aa9c34993dc051a4f344d1b10e4487e8 With the list of files from the script in outstanding_files, the relevant commands were: $ find src/libstd -name '*.rs' \ | xargs rustfmt --edition=2018 --unstable-features --skip-children $ rg libstd outstanding_files | xargs git checkout -- Repeating this process several months apart should get us coverage of most of the rest of libstd. To confirm no funny business: $ git checkout $THIS_COMMIT^ $ git show --pretty= --name-only $THIS_COMMIT \ | xargs rustfmt --edition=2018 --unstable-features --skip-children $ git diff $THIS_COMMIT # there should be no difference

libstd => 2018

2019-02-27T19:06:15+00:00

Remove licenses

2018-12-26T04:08:33+00:00

rustc_driver: get rid of extra thread on Unix

2018-03-18T14:05:28+00:00

Use a range to identify SIGSEGV in stack guards

2018-01-31T19:41:29+00:00

Previously, the `guard::init()` and `guard::current()` functions were returning a `usize` address representing the top of the stack guard, respectively for the main thread and for spawned threads. The `SIGSEGV` handler on `unix` targets checked if a fault was within one page below that address, if so reporting it as a stack overflow. Now `unix` targets report a `Range` representing the guard memory, so it can cover arbitrary guard sizes. Non-`unix` targets which always return `None` for guards now do so with `Option`, so they don't pay any overhead. For `linux-gnu` in particular, the previous guard upper-bound was `stackaddr + guardsize`, as the protected memory was *inside* the stack. This was a glibc bug, and starting from 2.27 they are moving the guard *past* the end of the stack. However, there's no simple way for us to know where the guard page actually lies, so now we declare it as the whole range of `stackaddr ± guardsize`, and any fault therein will be called a stack overflow. This fixes #47863.

use field init shorthand EVERYWHERE

2017-08-15T22:29:17+00:00

Like #43008 (f668999), but _much more aggressive_.

Use LocalKey::try_with in std

2017-07-11T00:18:36+00:00

std: remove a workaround for privacy limitations that isn't necessary anymore

2017-03-14T01:42:23+00:00

std: Move sys_common to libstd/sys_common

2016-11-01T17:08:24+00:00

Make the directory structure reflect the module structure. I've always found the existing structure confusing.