Every programmer at some point during development would need to make changes to his or code to make it more efficient, either to deliver faster speeds or to run on less resources. This is what TASKING call code optimisation.
While there are several ways to tackle code optimisation, such as compressing, rearranging, and inlining, in their whitepaper, TASKING focus on the compiler built-in transformation techniques that can reduce a memory usage footprint.
While there are several built-in compiler optimisation tools readily available to programmers, their potential remains largely untapped. Either due to unfamiliarity or unawareness of these tools, engineers can be reluctant risking deadlines to try untested techniques, especially if they’re involved in developing safety-critical systems. In the white paper TASKING discuss a few easy to implement compiler optimisation techniques found in the TASKING toolsets.
These techniques are available on different scope levels up to the application scope, including MIL-linking, MIL-splitting, inlining, and code compaction, also known as reverse-inlining. While these code optimisation techniques can be applied to any software development application, the context into which TASKING will present is for safety-critical automotive systems.