diff options
| author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2020-02-14 08:40:41 +0100 |
|---|---|---|
| committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2020-02-25 07:15:18 +0100 |
| commit | 6b0873ffdfd59f163dbb3a64b77dd6604701435d (patch) | |
| tree | 2810ca7ae03050396ad97f215f19ac8bf38c5c79 /testsuites/sptests/sp54 | |
| parent | sptests/spcbssched03: Include missing header file (diff) | |
| download | rtems-6b0873ffdfd59f163dbb3a64b77dd6604701435d.tar.bz2 | |
config: Remove CONFIGURE_HAS_OWN_INIT_TASK_TABLE
The CONFIGURE_HAS_OWN_INIT_TASK_TABLE and
CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE are the last *_HAS_OWN_*
configuration options. These two options are probably unused, see also:
* https://lists.rtems.org/pipermail/users/2019-April/033129.html
* https://lists.rtems.org/pipermail/users/2019-April/033130.html
Removing them simplifies the configuration. If there is a real user need
which shows up after the removal, we can resurrect them on demand.
Using CONFIGURE_HAS_OWN_INIT_TASK_TABLE would have required the use of
the undocumented CONFIGURE_INIT_TASK_TABLE and
CONFIGURE_INIT_TASK_TABLE_SIZE configuration options.
Update #3873.
Diffstat (limited to 'testsuites/sptests/sp54')
| -rw-r--r-- | testsuites/sptests/sp54/init.c | 26 |
1 files changed, 8 insertions, 18 deletions
diff --git a/testsuites/sptests/sp54/init.c b/testsuites/sptests/sp54/init.c index 07001e1e5e..71437fac8e 100644 --- a/testsuites/sptests/sp54/init.c +++ b/testsuites/sptests/sp54/init.c @@ -24,9 +24,10 @@ const char rtems_test_name[] = "SP 54"; static void *Init( uintptr_t ignored ) { - rtems_status_code status; - rtems_task_priority pri; - rtems_id id; + rtems_status_code status; + rtems_task_priority pri; + rtems_id id; + const rtems_api_configuration_table *config; /* * It is possible that since this thread prints and there is no idle @@ -52,6 +53,10 @@ static void *Init( uintptr_t ignored ) rtems_test_assert( rtems_configuration_get_do_zero_of_workspace() ); + config = rtems_configuration_get_rtems_api_configuration(); + rtems_test_assert( config->number_of_initialization_tasks == 0 ); + rtems_test_assert( config->User_initialization_tasks_table == NULL ); + TEST_END(); rtems_test_exit(0); } @@ -68,21 +73,6 @@ static void *Init( uintptr_t ignored ) #define CONFIGURE_IDLE_TASK_BODY Init #define CONFIGURE_IDLE_TASK_INITIALIZES_APPLICATION -/* - * Another odd case to hit. Since we use the Init task is Idle task - * configuration, we can dummy up the initialization task configuration - * to have a non-NULL pointer and 0 tasks. - */ - -#define CONFIGURE_HAS_OWN_INIT_TASK_TABLE 1 - -rtems_initialization_tasks_table Initialization_tasks[1] = - { { 0, }}; - -#define CONFIGURE_INIT_TASK_TABLE Initialization_tasks -#define CONFIGURE_INIT_TASK_TABLE_SIZE 0 -#define CONFIGURE_INIT_TASK_STACK_SIZE 0 - #define CONFIGURE_DIRTY_MEMORY /* |