Changes between Version 6 and Version 7 of GCI/Coding/AddPerSectionSupportToBSPs

Timestamp:

01/07/16 01:29:24 (8 years ago)

Author:

Joel Sherrill

Comment:

Add more on repeat on variants

GCI/Coding/AddPerSectionSupportToBSPs

@@ -70 +70 @@
 Note that the "time" command was used to measure how long this took to execute. The next lines show the size of the sample executables. The final line is "0" indicating the invocation was successful.
 
+Repeat this for every BSP variant in the BSP family.
+
 Now make the modifications needed to turn on the per element section capability:
 
@@ -76 +78 @@
 * Edit one or more linkcmds files located within either c/src/lib/libbsp/CPU/BSP/startup/ or c/src/lib/libbsp/CPU/shared/startup to add the KEEP directives.
 
-Using the "build_bsp" script, rebuild the BSP variants in the BSP Family and again note the sizes. If there is no reduction, something is not right. If the reduction is near 100%, then something is not right. 
+Using the "build_bsp" script, rebuild each the BSP variants in the BSP Family and again keep a running record of the sizes. The before and after size information is a critical part of the commit information. 
+
+There are a few quick indicators if something is not right.
+
+* If the reduction is near 100%, then something is not right. You will likely need mentor help to resolve this.
+
+* If the BSP did not reduce in size at all, then something is not right.
+
+The expected drop is 10-50% for the tests with cdtest.exe and cxx_iostream.exe often showing the greatest reductions.
 
 If the BSP variant is one which can be tested on a simulator, then you need to test it. 
@@ -118 +128 @@
 The complete patch and commit message for the mips/jmr3904 can be viewed at https://git.rtems.org/rtems/commit/c/src?id=bd655345c1a5f7dba42ddf6cd56f6259c62eb267.
 
+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.
+