History

Meco Man ed09f38012 [libc] remove RT_USING_LIBC		2021-12-30 01:27:25 +08:00
..
cpp11	[libc] remove RT_USING_LIBC	2021-12-30 01:27:25 +08:00
Kconfig	[libc] remove RT_USING_LIBC	2021-12-30 01:27:25 +08:00
README.md	[libc] remove RT_USING_LIBC	2021-12-30 01:27:25 +08:00
SConscript	[update] support armclang and c++11.	2021-09-16 09:51:33 +08:00
cxx_Mutex.cpp	[mutex] use RT_IPC_FLAG_PRIO to replace RT_IPC_FLAG_FIFO	2021-11-17 15:57:15 -05:00
cxx_Semaphore.cpp	[modify] those file name is risky if you use both "c++" and "POSIX pthread".	2021-10-13 15:20:29 +08:00
cxx_Thread.cpp	[modify] those file name is risky if you use both "c++" and "POSIX pthread".	2021-10-13 15:20:29 +08:00
cxx_crt.cpp	[modify] those file name is risky if you use both "c++" and "POSIX pthread".	2021-10-13 15:20:29 +08:00
cxx_crt.h	[modify] those file name is risky if you use both "c++" and "POSIX pthread".	2021-10-13 15:20:29 +08:00
cxx_crt_init.c	[modify] those file name is risky if you use both "c++" and "POSIX pthread".	2021-10-13 15:20:29 +08:00
cxx_lock.h	[modify] those file name is risky if you use both "c++" and "POSIX pthread".	2021-10-13 15:20:29 +08:00
cxx_mail.h	[modify] those file name is risky if you use both "c++" and "POSIX pthread".	2021-10-13 15:20:29 +08:00
cxx_mutex.h	[modify] those file name is risky if you use both "c++" and "POSIX pthread".	2021-10-13 15:20:29 +08:00
cxx_queue.h	[modify] those file name is risky if you use both "c++" and "POSIX pthread".	2021-10-13 15:20:29 +08:00
cxx_semaphore.h	[modify] those file name is risky if you use both "c++" and "POSIX pthread".	2021-10-13 15:20:29 +08:00
cxx_thread.h	[modify] those file name is risky if you use both "c++" and "POSIX pthread".	2021-10-13 15:20:29 +08:00

README.md

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:

DOES NOT use exception.
DOES NOT use Run-Time Type Information (RTTI).
Template is discouraged and it easily causes code text large.
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.
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);