Changes between Version 2 and Version 3 of TBR/UserManual/Using_C_Plus_Plus

Timestamp:

10/21/05 19:40:54 (19 years ago)

Author:

JoelSherrill

Comment:

/* PowerPC Initialisation */ more format corrections

TBR/UserManual/Using_C_Plus_Plus

@@ -37 +37 @@
 BSP should call (gcc provided) '''_eabi()''' very early to set up a SYSV/EABI compliant environment (load r2/r13, stack align etc.). If you don't do this, e.g., SYSV/EABI short data areas won't work (see gcc -msdata -meabi options).
 
-RTEMS calls '''''init()''' which among other things works through the C++ static constructor list -- provided that your linker stript and '''bsp''specs''' files are correct. See [wiki:#InitMagic C++ .init Linker Magic] on how it works.
+RTEMS calls '''init()''' which among other things works through the C++ static constructor list -- provided that your linker stript and '''bsp_specs''' files are correct. See [wiki:#InitMagic C++ .init Linker Magic] on how it works.
 
- * However''', there is a problem here, in that '''''eabi()''' ends up calling '''''init()''' (actually, '''__init()*, we renamed to fix the problem   described here) when it is still too early to initialize the C++ environment.
+ * However, there is a problem here, in that '''eabi()''' ends up calling '''init()''' (actually, '''__init()''', we renamed to fix the problem described here) when it is still too early to initialize the C++ environment.
 
-  '''Note''' both details are of the 'seems to work' type. You won't notice anything if you don't call '''''eabi()''' until you try to use an essential SYSV/EABI feature. Likewise, calling '''''init()''' too early might not cause problems in many cases until one of your constructors uses an yet unavailable feature provided by RTEMS such as '''malloc()'''.
+  '''Note''' both details are of the 'seems to work' type. You won't notice anything if you don't call '''eabi()''' until you try to use an essential SYSV/EABI feature. Likewise, calling '''init()''' too early might not cause problems in many cases until one of your constructors uses an yet unavailable feature provided by RTEMS such as '''malloc()'''.
 
 For the PowerPC a typical chicken + egg. problem exists -
 
 ##we want to call '''_eabi()''' early (libbsp/powerpc/shared/start/start.S)
-##we want to prevent '''_''init()''' from being called too early (by '''''eabi()''')
+##we want to prevent '''_init()''' from being called too early (by '''eabi()''')
 ##we want to call '''__init()''' at the apropriate time.
 ##we dont want to hack gcc.
 
 Here's the solution using the '''.init''' magic as described in the appendix -
-  * an additional startup file '''rtems''crti.S''' ''terminates'' '''''_init()'''
+  * an additional startup file '''rtems_crti.S''' terminates '''_init()'''
   * so it becomes a no-op and introduces a new '''_init()''' entry point
   * to be used by RTEMS ([wiki:ThreadHandler ThreadHandler]).
@@ -79 +79 @@
 Here's what happens (properly linked executable) :
 
-   <verbatim></verbatim>
-
 ##BSP '''start.s''' calls '''_eabi()'''; SYSVI/EABI environment setup
-##'''''eabi()''' calls '''''_init()'''
+##'''eabi()''' calls '''_init()'''
 ##'''__init()''' returns immediately
 ##BSP initializes