Kendall Bennett wrote:
>
> Brian Paul <[EMAIL PROTECTED]> wrote:
>
> > I considered this project myself when I got my Palm Pilot. However,
> > as I understand it, the system is limited to 32KB code and data
> > segments. Mesa's code is much larger and often allocates buffers
> > larger than 32KB.
>
> Not to mention that huge amounts of stack space that Mesa gobbles up.
> I spent three days this week tracking down problems that showed up in
> the latest Mesa sources when running under DOS and QNX with texture
> mapping. It turns out that these environments do not support growable
> stacks, and hence we need to pre-allocate in advance the amount of
> stack space that we need at link time. I was using a 50K stack. Turns
> out that in mesa there are a number of places where a 19K temporary
> variable is used on the stack for rendering purposes. Adding up all
> the stack space equalled a minimum stack of 60K before the program
> would start running.
>
> I am now using a 200K stack to be safe, but Mesa certainly does chew
> through the memory!
Where is the 19KB temporary variable is used? That still doesn't
seem like a lot to me but maybe there's a way to minimize it.
-Brian
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
