diff options
Diffstat (limited to 'testsuites/samples/minimum/init.c')
| -rw-r--r-- | testsuites/samples/minimum/init.c | 20 |
1 files changed, 5 insertions, 15 deletions
diff --git a/testsuites/samples/minimum/init.c b/testsuites/samples/minimum/init.c index c988d6d750..ee14a1aef4 100644 --- a/testsuites/samples/minimum/init.c +++ b/testsuites/samples/minimum/init.c @@ -81,7 +81,12 @@ static void *Init( uintptr_t ignored ) * demonstrates that the user can specify how small of a minimum * stack they want. */ +#ifdef RTEMS_GCOV_COVERAGE +#define CONFIGURE_MINIMUM_TASK_STACK_SIZE \ + (CPU_STACK_MINIMUM_SIZE - CPU_STACK_ALIGNMENT) +#else #define CONFIGURE_MINIMUM_TASK_STACK_SIZE 512 +#endif /* * Keep the interrupt/initialization stack as is. Otherwise, the test may fail @@ -100,21 +105,6 @@ static void *Init( uintptr_t ignored ) #define CONFIGURE_MAXIMUM_PRIORITY 15 /* - * This configures RTEMS to use a single memory pool for the RTEMS Workspace - * and C Program Heap. If not defined, there will be separate memory pools - * for the RTEMS Workspace and C Program Heap. Having separate pools - * does haved some advantages in the event a task blows a stack or writes - * outside its memory area. However, in low memory systems the overhead of - * the two pools plus the potential for unused memory in either pool is - * very undesirable. - * - * In high memory environments, this is desirable when you want to use - * the RTEMS "unlimited" objects option. You will be able to create objects - * until you run out of memory. - */ -#define CONFIGURE_UNIFIED_WORK_AREAS - -/* * In this application, the initialization task performs the system * initialization and then transforms itself into the idle task. */ |