Files
rt-thread/components/libc/cplusplus
seteiro 3577e7a6ed [components][libc] run .init_array constructors in cplusplus_system_init
Newer GCC emits C++ global constructors into .init_array, which many
linker scripts keep outside [__ctors_start__, __ctors_end__), so they
never ran. Walk __init_array_start/__init_array_end (weak) as well,
skipping entries already covered by the ctors range.

Add RT_USING_CPP_CRT_INIT for ports whose startup runtime already runs
.init_array, default on for the simulator. With it set, only the
.init_array walk is skipped; the ctors range is still walked.

Renesas RA/RA_WIRELESS/RZ families select it when C++ is enabled: FSP
SystemInit() already walks .init_array, so boards whose linker script
only provides __init_array_* would run constructors twice. Boards that
fold .init_array into the ctors range (ra6m3-hmi-board, ra8d1, rz)
still run them once via RT-Thread.

Also source env.sh and restore RTT_EXEC_PATH in ToolsCI project generate
and dist steps so scons is on PATH (exit 127) and the ARM toolchain path
is not overwritten by env.sh.

Fixes #11778
2026-10-11 16:11:07 +08:00
..
…
…

C++ support for RT-Thread

This is the C++ component in RT-Thread RTOS. In order to support C++ language, this component implement a basic environment, such as new/delete operators.

Because RT-Thread RTOS is used in embedded system mostly, there are some rules for C++ applications:

  1. DOES NOT use exception.
  2. DOES NOT use Run-Time Type Information (RTTI).
  3. Template is discouraged and it easily causes code text large.
  4. Static class variables are discouraged. The time and place to call their constructor function could not be precisely controlled and make multi-threaded programming a nightmare.
  5. Multiple inheritance is strongly discouraged, as it can cause intolerable confusion.

About GNU GCC compiler

please add following string in your ld link script:

// in your .text section
PROVIDE(__ctors_start__ = .);
/* old GCC version uses .ctors */
KEEP(*(SORT(.ctors.*)))
KEEP(*(.ctors))
/* new GCC version uses .init_array */
KEEP (*(SORT(.init_array.*)))
KEEP (*(.init_array))
PROVIDE(__ctors_end__ = .);

. = ALIGN(4);

// as a standalone section if you use ARM target.

/* The .ARM.exidx section is used for C++ exception handling. */
/* .ARM.exidx is sorted, so has to go in its own output section.  */
__exidx_start = .;
ARM.exidx :
{
    *(.ARM.exidx* .gnu.linkonce.armexidx.*)

    /* This is used by the startup in order to initialize the .data secion */
    _sidata = .;
} > CODE
__exidx_end = .;

/* .data section which is used for initialized data */

// in your .data section
PROVIDE(__dtors_start__ = .);
KEEP(*(SORT(.dtors.*)))
KEEP(*(.dtors))
PROVIDE(__dtors_end__ = .);

. = ALIGN(4);