Skip to main content
Magline joins Rapita Trailblazer Partnership Program to support DO-178 Certification
Eve Air Mobility joins Rapita Systems Trailblazer Partnership Program for eVTOL projects
Rapita Systems launches MACH178 Foundations for multicore DO-178C compliance
Collins Aerospace and Rapita present award winning paper at DASC 2024
Data Coupling Basics in DO-178C
Control Coupling Basics in DO-178C
Components in Data Coupling and Control Coupling
The ‘A’ Team comes to the rescue of code coverage analysis
DO-278A Guidance: Introduction to RTCA DO-278 approval
ISO 26262
Data Coupling & Control Coupling
Verifying additional code for DO-178C
DO-178C Multicore In-person Training (Fort Worth, TX)
DO-178C Multicore In-person Training (Toulouse)
The latest in the series of blog posts on optimizing embedded software with the aim of improving (i.e. reducing) worst-case execution times focuses on global variables and aliasing.
Software optimization techniques which improve worst-case execution times #14: Global Variables and Aliasing
Global variables can be modified indirectly via pointers or function calls. This typically means that the compiler cannot keep the value of a global variable in a register; it must write the value back to memory and re-load it each time it is used. For this reason, the use of global variables should be avoided in worst-case hotspot code. If the use of global variables is unavoidable, then it can be more efficient to cache the value into a local variable, which is then used extensively before its value is written back into the global variable.
Next week: Removing code from the worst-case path
DO-178C webinars
White papers
Mitigation of interference in multicore processors for A(M)C 20-193
Developing DO-178C and ED-12C-certifiable multicore software
Efficient Verification Through the DO-178C Life Cycle
A Commercial Solution for Safety-Critical Multicore Timing Analysis
