Changes between Version 10 and Version 11 of GSoC/2013/UnifiedAPIs

Timestamp:

09/24/13 20:44:05 (11 years ago)

Author:

Vipulnayyar

Comment:

GSoC/2013/UnifiedAPIs

@@ -39 +39 @@
 #Compile a list of all RTEMS internal functions(i.e starting with an '_' ) defined in cpukit & libcpu.
 #Compile another list of functions starting with an '_' being executed in BSP by searching for a ';' to ensure that function is actually being called. Searching for a function being called from a file can be a bit intimidating if the function calling spans multiple lines, meaning that the function name is on one line & the semicolon on another. Since grep only parses line by line, so it cannot do this task very easily. What happens now is that all the newlines are trimmed while searching a file. The whole file now being concatenated in a single line, so grep is ideal for searching the pattern [ |^][_]+[a-z|A-Z|0-9|_]*[ ]*[\n]*\([^;]*\)[ ]*;
+#Find common function names in the above two lists in order to ensure that the function being called in a bsp is infact been defined in cpukit or libcpu. Report it.
+
+
+In order to obtain the results of the script successfully, either call it from a libbsp, cpu family or a bsp directory or pass it a path for a single or multiple bsp directories so that it can validate the location of a bsp in the RTEMS tree. If no path is passed, the pwd is evaluated and searched for bsps.
+
+ * Passing only the directory name for bsp, cpu family or libbsp displays the discrepancies found only for critical files & functions. Following parameters need to be passed to expand the horizon
+ * --warnings : gives all the critical & non-critical discrepancies found in a bsp.
+ * --verbose : gives the whole story of a BSP. Any discrepancy & a correct rule implementation is also displayed.
+ * --tests : gives test specific checks for each given BSP.