From 3c78e93c959e3cc9d0fe47ce3eaccc2814367356 Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Tue, 30 Jun 2020 09:51:13 +0200 Subject: score: Clarify CPU_USE_LIBC_INIT_FINI_ARRAY option Update #4018. --- cpukit/score/cpu/no_cpu/include/rtems/score/cpu.h | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'cpukit/score/cpu/no_cpu') diff --git a/cpukit/score/cpu/no_cpu/include/rtems/score/cpu.h b/cpukit/score/cpu/no_cpu/include/rtems/score/cpu.h index 84125aa16b..50313bbd61 100644 --- a/cpukit/score/cpu/no_cpu/include/rtems/score/cpu.h +++ b/cpukit/score/cpu/no_cpu/include/rtems/score/cpu.h @@ -250,9 +250,10 @@ extern "C" { #define CPU_MAXIMUM_PROCESSORS 32 /** - * The following define determines whether or not this CPU port will use - * libc global constructors and destructors instead of _init/_fini functions - * depending on .ctors and .dtors linker sections. + * The following define determines whether or not this CPU port will use the C + * library support to run the global constructors and destructors on + * architectures that use .init_array and .fini_array sections. If defined to + * FALSE, then the _init() and _fini() functions will be used. */ #define CPU_USE_LIBC_INIT_FINI_ARRAY TRUE -- cgit v1.2.3