Changes between Version 8 and Version 9 of GCI/Coding/AddPerSectionSupportToBSPs

Timestamp:

09/12/18 19:51:44 (6 years ago)

Author:

Gedare Bloom

Comment:

--

GCI/Coding/AddPerSectionSupportToBSPs

@@ -2 +2 @@
 
 [[TOC(GCI/Coding/AddPerSectionSupportToBSPs, depth=2)]]
-
-You '''must''' have completed "Getting Started: Hello World" before attempting this task.
 
 When a program is compiled and linked, the linker attempts to resolve all references to functions and data elements required by the program. By default, the GNU linker will place an entire object file into an application executable even if only one symbol is required by the application. This can lead to unused code in an executable. This is undesirable from both an application image size and code review perspective.
@@ -10 +8 @@
 
 Although large parts of RTEMS are carefully implemented to have only one method per file, experiments with turning on this capability have shown reductions in RTEMS test programs and user applications of up to 50% in overall size. 
+
+== Directions for Students ==
+
+**Pre-Requisite**: You '''must''' have completed "Getting Started: Hello World" or the equivalent of [wiki:GSoC/GettingStarted Getting Started for GSoC Students] before attempting this task.
 
 This task consists of turning on this capability for a specific BSP family. A BSP family is the collection of BSPs under a single directory such as c/src/lib/libbsp/CPU/BSP_FAMILY. The make/custom directory has a BSP.cfg file for each BSP which may be built. If the BSP Family supports multiple BSP variants, the BSP.cfg files may include either a shared ".inc" file or a base ".cfg" file with common settings.
@@ -29 +31 @@
 macro to such sections. See for example c/src/lib/libbsp/sparc/shared/startup/linkcmds.base which has already been tailored. Each BSP will have a linkcmds file which may or may not include a shared base file.
 
-== Task Requirements ==
+=== Task Requirements ===
 
 In the description of this task, you were given a BSP Family to enable this capability for. The BSP Family will be named CPU/BSP_FAMILY which indicates its location in the source tree and implies a set of BSP variants as described above.
@@ -132 +134 @@
 If the BSP Family has multiple variants, the commit message will need to include the before and after information for each BSP variant in the family.
 
+== Directions for Mentors ==
+Check the commit, if it looks good and you have rights, push it. If not, ask on devel for a maintainer to push it.