: The fixed size stack would probably be best placed just above the bss with
: the heap above that. This would not require any mods to the linker or
: binary format, just changes to the kernel.
:
What exactly is being gained by making this modification? The stack
is fixed size in both cases. Is it just that we currently pre-reserve the maximum
combined heap/stack now, and in the future wouldn't require the heap size
to be known?
- Re: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- Re: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- Re: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
