[RTEMS Project] #3873: Remove CONFIGURE_HAS_OWN_INIT_TASK_TABLE

[RTEMS trac]

#3873: Remove CONFIGURE_HAS_OWN_INIT_TASK_TABLE
-----------------------------+------------------------------
 Reporter:  Sebastian Huber  |       Owner:  Sebastian Huber
     Type:  task             |      Status:  closed
 Priority:  normal           |   Milestone:  5.1
Component:  config           |     Version:  5
 Severity:  normal           |  Resolution:  fixed
 Keywords:                   |  Blocked By:
 Blocking:                   |
-----------------------------+------------------------------
Changes (by Sebastian Huber <sebastian.huber@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"3738a74014753ca37891f0725ca72ca82dd4391e/rtems-docs"
 3738a74/rtems-docs]:
 {{{
 #!CommitTicketReference repository="rtems-docs"
 revision="3738a74014753ca37891f0725ca72ca82dd4391e"
 c-user: Obsolete 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.

 Close #3873.
 }}}

--
Ticket URL: <http://devel.rtems.org/ticket/3873#comment:5>
RTEMS Project <http://www.rtems.org/>
RTEMS Project