[rtems commit] score: Clarify CPU_USE_LIBC_INIT_FINI_ARRAY option

[Sebastian Huber]

Module:    rtems
Branch:    master
Commit:    3c78e93c959e3cc9d0fe47ce3eaccc2814367356
Changeset: http://git.rtems.org/rtems/commit/?id=3c78e93c959e3cc9d0fe47ce3eaccc2814367356

Author:    Sebastian Huber <sebastian.huber at embedded-brains.de>
Date:      Tue Jun 30 09:51:13 2020 +0200

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(-)

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 84125aa..50313bb 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