#3862 closed enhancement (fixed)

Canonicalize CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY

Reported by: Sebastian Huber Owned by: Sebastian Huber
Priority: normal Milestone: 5.1
Component: config Version: 5
Severity: normal Keywords: qualification
Cc: Blocked By:
Blocking:

Description

The CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY configuration option is documented to be a boolean feature macro (is defined or undefined). However, in confdefs.h it uses the values TRUE and FALSE. It is the only configuration option implemented like this. Change it to use defined/undefined instead like the other options. This affects existing application configurations which use:

#define CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY FALSE

An unintentional zero of the workspace has an effect on the system boot time. This is an acceptable trade-off for the more canonical configuration.

Change History (2)

comment:1 Changed on 02/06/20 at 14:22:27 by Sebastian Huber <sebastian.huber@…>

Resolution: fixed
Status: assignedclosed

In 1d43a97/rtems:

config: CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY

Canonicalize CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY and use
defined/undefined instead of TRUE/FALSE.

Close #3862.

comment:2 Changed on 06/23/21 at 07:07:55 by Sebastian Huber

Keywords: qualification added
Note: See TracTickets for help on using tickets.