OpenE2K/rust
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

green: Don't return the red zone in stack_bounds()

Browse Source 
This is mostly just an implementation detail, and anyone worried about the stack
bounds doesn't need to be bothered with the red zone because it's not usable
anyway.

Closes #12897
This commit is contained in:
Alex Crichton 2014-03-14 22:46:13 -07:00
parent 1218f6db77
commit bf67783332
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/libgreen/task.rs
View File

@ -20,14 +20,15 @@
use std::any::Any;
use std::cast;
use std::rt::env;
use std::raw;
use std::rt::Runtime;
use std::rt::env;
use std::rt::local::Local;
use std::rt::rtio;
use std::rt::stack;
use std::rt::task::{Task, BlockedTask, SendMessage};
use std::task::TaskOpts;
use std::unstable::mutex::NativeMutex;
use std::raw;
use context::Context;
use coroutine::Coroutine;
@ -469,7 +470,9 @@ impl Runtime for GreenTask {
let c = self.coroutine.as_ref()
.expect("GreenTask.stack_bounds called without a coroutine");
(c.current_stack_segment.start() as uint,
// Don't return the red zone as part of the usable stack of this task,
// it's essentially an implementation detail.
(c.current_stack_segment.start() as uint + stack::RED_ZONE,
c.current_stack_segment.end() as uint)
}