TASKING VX-toolset for ARM User Guide

Using the C Compiler2. In the left pane, select C/C++ Build.In the right pane the C/C++ Build page appears.3. On the Behaviour tab, select Use parallel build.4. You can specify the number of parallel jobs, or you can use an optimal number of jobs. In the lastcase, amk will fork as many jobs in parallel as cores are available.Number of SectionsThe linker speed depends on the number of sections in the object files. The more sections, the longerthe locating will take. You can decrease the link time by creating output sections in the LSL file. Forexample:Use compiler option --rename-sections=.text={name}section_layout ::linear{group (ordered){section "code_output1" ( size = 64k, attributes = x, fill=0xFF,overflow = "code_output2"){select "*__cocofun*";}}}4.7. Static Code AnalysisStatic code analysis (SCA) is a relatively new feature in compilers. Various approaches and algorithmsexist to perform SCA, each having specific pros and cons.SCA Implementation Design PhilosophySCA is implemented in the TASKING compiler based on the following design criteria:• An SCA phase does not take up an excessive amount of execution time. Therefore, the SCA can beperformed during a normal edit-compile-debug cycle.• SCA is implemented in the compiler front-end. Therefore, no new makefiles or work procedures haveto be developed to perform SCA.• The number of emitted false positives is kept to a minimum. A false positive is a message that indicatesthat a correct code fragment contains a violation of a rule/recommendation. A number of warnings isissued in two variants, one variant when it is guaranteed that the rule is violated when the code isexecuted, and the other variant when the rules is potentially violated, as indicated by a precedingwarning message.163