On 05/10/2021 03:51, Chris Johns wrote:
On 5/10/21 4:29 am, Sebastian Huber wrote:
On 02/10/2021 01:44, Chris Johns wrote:
The fatal extensions have a well defined order (position in the
table). The user has the full control over the initial extensions table.
Is it backwards compatible when this new mode is enabled?
When you enable a new feature you get new behaviour. I am not sure what you mean
with backward compatible in this case. If you don't enable the exception to
signal mapping (default), then nothing changes.
"The user has the full control over the initial extensions table."
Does this option change that? Is this feature mutually exclusive or additive to
any "current control" a user has?
In other words, it is not clear to me if I can add this option and still
maintain any existing controls I may have.
If it is not and users need to make changes the user code becomes a mess of
version defines. Is that what we want?
If you add the new option similar to the stack checker option
#ifdef CONFIGURE_STACK_CHECKER_ENABLED
RTEMS_STACK_CHECKER_EXTENSION,
#endif
then you can either use the application configuration option to enable
the extension at the recommended position or you can use the extension
define in your CONFIGURE_INITIAL_EXTENSIONS exactly where you want it.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.hu...@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
