| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-08-06 | redox: convert to target_family unix | Jeremy Soller | -84/+0 | |
| 2019-04-10 | Eliminate `FnBox` usages from libstd. | CrLF0710 | -2/+1 | |
| 2019-02-28 | libstd => 2018 | Taiki Endo | -7/+7 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -10/+0 | |
| 2018-12-14 | Remove dead code | Oliver Scherer | -1/+0 | |
| 2018-12-06 | Change sys::Thread::new to take the thread entry as Box<dyn FnBox() + 'static>̣ | Jethro Beekman | -1/+2 | |
| 2018-11-06 | refactor: use shorthand fields | teresy | -1/+1 | |
| 2018-07-10 | Add missing `dyn` for cloudabi, redox, unix and wasm | ljedrz | -1/+1 | |
| 2018-04-12 | Import the `alloc` crate as `alloc_crate` in std | Simon Sapin | -1/+1 | |
| … to make the name `alloc` available. | ||||
| 2018-03-24 | Fix build on non-Unix platforms | Tatsuyuki Ishi | -0/+1 | |
| 2018-01-31 | Use a range to identify SIGSEGV in stack guards | Josh Stone | -2/+3 | |
| 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<usize>` 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. | ||||
| 2017-09-13 | Move default stack min size to thread implementations | Tobias Schaffner | -0/+2 | |
| The default min stack size value is smaller on l4re and therefore this value has to be different depending on the platform. | ||||
| 2016-11-28 | Commit to fix make tidy | Jeremy Soller | -1/+1 | |
| 2016-11-28 | Switch to using syscall crate directly - without import | Jeremy Soller | -14/+12 | |
| 2016-10-30 | Implement thread | Jeremy Soller | -14/+12 | |
| 2016-10-29 | Implement env, reentrant mutex, and partially implement scoped thread ↵ | Jeremy Soller | -3/+7 | |
| locals. Better error messages for unsupported features | ||||
| 2016-10-28 | Remove unsafe libc layer | Jeremy Soller | -16/+13 | |
| 2016-10-27 | Add redox system | Jeremy Soller | -0/+94 | |
