[Bug 1984] CONFIGURE_MINIMUM_STACK_SIZE vs CONFIGURE_MINIMUM_TASK_STACK_SIZE
bugzilla-daemon at rtems.org
bugzilla-daemon at rtems.org
Thu Dec 8 07:37:33 UTC 2011
https://www.rtems.org/bugzilla/show_bug.cgi?id=1984
Sebastian Huber <sebastian.huber at embedded-brains.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sebastian.huber at embedded-br
| |ains.de
--- Comment #4 from Sebastian Huber <sebastian.huber at embedded-brains.de> 2011-12-08 01:37:33 CST ---
(In reply to comment #2)
> This is fine. I still am not convinced the default behavior of propagating
> user-defined CONFIGURE_MINIMUM_STACK_SIZE to the idle stack size and the
> interrupt stack size is a good idea, considering there are specific CONFIGURE
> macros for overriding those.
This is one of the strange things I noticed while implementing PR 1924.
Using the normal minimum stack size for the idle thread is a huge waste of
memory in most systems.
--
Configure bugmail: https://www.rtems.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the bugs
mailing list