- 19 12月, 2011 1 次提交
-
-
由 Brian Anderson 提交于
Throwing in upcall_fail ends up running lots of code in the red zone. To avoid it we have the personality function figure out which stack it's on and switch as needed.
-
- 18 12月, 2011 1 次提交
-
-
由 Brian Anderson 提交于
-
- 07 12月, 2011 2 次提交
-
-
由 Brian Anderson 提交于
rust_task is using the word limit it two ways, so one has to change.
-
由 Brian Anderson 提交于
When unwinding through __morestack the stack limit in the TLS is invalidated and must be reset. Instead of actually landing at __morestack we're just going to make all our Rust landing pads call upcall_reset_stack_limit, which will find the stack segment that corresponds to the current stack pointer and put the limit in the TLS. Also massively expand the stack segment red zone to make more room for the dynamic linker. Will fix in the future.
-
- 02 12月, 2011 1 次提交
-
-
由 Brian Anderson 提交于
-
- 01 12月, 2011 2 次提交
-
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
- 23 11月, 2011 1 次提交
-
-
由 Brian Anderson 提交于
-
- 19 11月, 2011 3 次提交
-
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
- 17 11月, 2011 3 次提交
-
-
由 Brian Anderson 提交于
-
由 Niko Matsakis 提交于
to char[16], not struct{long,long}
-
由 Niko Matsakis 提交于
-
- 14 11月, 2011 1 次提交
-
-
由 Brian Anderson 提交于
-
- 12 11月, 2011 2 次提交
-
-
由 Brian Anderson 提交于
Sucks, but otherwise there are races when one task drops the refcount to zero followed by another bumping it again
-
由 Brian Anderson 提交于
-
- 01 11月, 2011 1 次提交
-
-
由 Patrick Walton 提交于
-
- 27 9月, 2011 2 次提交
-
-
由 Patrick Walton 提交于
-
由 Patrick Walton 提交于
-
- 24 9月, 2011 1 次提交
-
-
由 Patrick Walton 提交于
-
- 22 9月, 2011 1 次提交
-
-
由 Patrick Walton 提交于
rustc: Port the fn and obj traversal logic over from the GC branch. Doesn't actually do anything yet due to lack of support in trans.
-
- 21 9月, 2011 2 次提交
-
-
由 Patrick Walton 提交于
-
由 Patrick Walton 提交于
-
- 20 9月, 2011 1 次提交
-
-
由 Patrick Walton 提交于
-
- 15 9月, 2011 2 次提交
-
-
由 Brian Anderson 提交于
The failure will basically go 'through' the dead parent and continue propagating the failure (as if the child was reparented).
-
由 Brian Anderson 提交于
-
- 08 9月, 2011 2 次提交
-
-
由 Brian Anderson 提交于
When a task fails, we will throw an exception, then catch it at the bottom of the stack. On Windows we don't do this yet because the exception doesn't propagate correctly. No cleanups yet. Issue #236
-
由 Brian Anderson 提交于
The motivation here is that the bottom of each stack needs to contain a C++ try/catch block so that we can unwind. This is already the case for main, but not spawned tasks. Issue #236
-
- 26 8月, 2011 1 次提交
-
-
由 Eric Holk 提交于
-
- 20 8月, 2011 1 次提交
-
-
由 Patrick Walton 提交于
-
- 18 8月, 2011 1 次提交
-
-
由 Eric Holk 提交于
-
- 17 8月, 2011 3 次提交
-
-
由 Patrick Walton 提交于
-
由 Eric Holk 提交于
-
由 Eric Holk 提交于
Removed trans_comm.rs from the compiler. Updating aio/sio to work with the new chan and port system, started on a networking module for the standard library.
-
- 16 8月, 2011 3 次提交
- 09 8月, 2011 1 次提交
-
-
由 unknown 提交于
This is the new way to refer to tasks in rust-land. Currently all they do is serve as a key to look up the old rust_task structure. Ideally they won't be ref counted, but baby steps.
-
- 06 8月, 2011 1 次提交
-
-
由 Eric Holk 提交于
-