On Aug 7, 2006, at 10:52 AM, Jan Erik Moström wrote:
The problem he's encountered has nothing to do with the thread's
stack space: it means that one single method is trying to use more
than 32k of stack space, all by itself.
Curious, why is there a limit? Is it because relative addressing or
something
else?
The PowerPC load and store instructions use a 16-bit immediate
offset, which yields a range of 32k above or below the base address.
Stack data is always located above the stack pointer, so one
instruction can reach no more than 32k of the stack at a time.
There are, of course, ways to work around this, but doing it in such
a way that normal methods are not penalized would be a fair bit of
work. Since the only methods which reach the limit are the ones so
large they ought to be refactored anyway, this has not been a priority.
Mars Saxman
REAL Software_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
