Your browser does not support JavaScript! Skip to main content
Free 30-day trial Customer portal Careers DO-178C Handbook
 
Rapita Systems
 

Industry leading verification tools & services

Rapita Verification Suite (RVS)

  RapiTest - Unit/system testing   RapiCover - Structural coverage analysis   RapiTime - Timing analysis (inc. WCET)   RapiTask - Scheduling visualization   RapiCoverZero - Zero footprint coverage analysis   RapiTimeZero - Zero footprint timing analysis   RapiTaskZero - Zero footprint scheduling analysis

Multicore verification

  MACH178   Multicore Timing Solution   RapiDaemons

Services

  V & V Services   Qualification   Training   Tool Integration  Support

Industries

  Aerospace (DO-178C)   Automotive (ISO 26262)   Space

Other

  RTBx   Mx-Suite   Software licensing   Product life cycle policy  RVS development roadmap

Latest from Rapita HQ

Latest news

Danlaw Acquires Maspatechnologies - Expanding Rapita Systems to Spain
Rapita co-authored paper wins ERTS22 Best paper award
A look back on Rapita's Multicore DO-178C training in Huntsville
RVS 3.17 Launched
View News

Latest from the Rapita blog

Why mitigating interference alone isn’t enough to verify timing performance for multicore DO-178C projects
There are how many sources of interference in a multicore system?
Supporting modern development methodologies for verification of safety-critical software
Flexible licensing software fit for modern working
View Blog

Latest discovery pages

do178c DO-178C Guidance: Introduction to RTCA DO-178 certification
matlab_simulink MATLAB® Simulink® MCDC coverage and WCET analysis
code_coverage_ada Code coverage for Ada, C and C++
amc-20-193 AMC 20-193
View Discovery pages

Upcoming events

Aerospace Tech Week Europe 2023
2023-03-29
Certification Together International Conference
2023-05-10
View Events

Technical resources for industry professionals

Latest White papers

DO178C Handbook
Efficient Verification Through the DO-178C Life Cycle
A Commercial Solution for Safety-Critical Multicore Timing Analysis
Compliance with the Future Airborne Capability Environment (FACE) standard
View White papers

Latest Videos

Efficient DO-178C verification - WCET analysis
Efficient DO-178C verification - Code coverage
Efficient DO-178C verification - Functional testing
SCADE Test video thumbnail
Complementary DO-178C verification with Ansys(R) SCADE Test(TM) and RVS
View Videos

Latest Case studies

Supporting ISO 26262 ASIL D software verification for EasyMile
RapiCover’s advanced features accelerate the certification of military UAV Engine Control
Front cover of whitepaper collins
Delivering world-class tool support to Collins Aerospace
View Case studies

Other Downloads

 Webinars

 Brochures

 Product briefs

 Technical notes

 Research projects

Discover Rapita

Who we are

The company menu

  • About us
  • Customers
  • Distributors
  • Locations
  • Partners
  • Research projects
  • Contact us

US office

+1 248-957-9801
info@rapitasystems.com
Rapita Systems, Inc.
41131 Vincenti Ct.
Novi
MI 48375
USA

UK office

+44 (0)1904 413945
info@rapitasystems.com
Rapita Systems Ltd.
Atlas House
Osbaldwick Link Road
York, YO10 3JB
UK

Spain office

+34 930 46 42 72
info@rapitasystems.com
Rapita Systems S.L.
Parc UPC, Edificio K2M
c/ Jordi Girona, 1-3, Office 306-307
Barcelona 08034
Spain

Working at Rapita

Careers

Careers menu

  • Current opportunities & application process
  • Working at Rapita
Back to Top

Understanding the value of WCET optimisation within high-integrity real-time software

Breadcrumb

  1. Home
  2. Blog
  3. Understanding the value of WCET optimisation within high-integrity real-time software
Nick
2010-05-06

High-integrity software is typically thought of as being carefully constructed according to rigorous development procedures that primarily ensure its functional correctness. One casualty of this process can be run-time performance but, given the relatively small number of units being produced, the run-time performance can be addressed by over-specifying the hardware. In this environment, timing optimisation would appear to be completely inappropriate, since it should be unnecessary and could add to the already high costs of ensuring functional correctness.

However, optimisation does have an important role to play in high-integrity, real-time software. In order to function correctly, the software must not only compute the correct results but also compute those results within a well bounded amount of time. Establishing a worst-case execution time (WCET) less than the allotted budget can be extremely difficult in the presence of complex software and hardware and it may well be cheaper to apply some well chosen WCET optimisations as part of the timing validation process.

WCET optimisations are modifications to the software that either improve the actual performance of the software or make it possible (or cost-effective) to establish a lower WCET value. Unlike traditional average-case optimisations which generally add complexity to the code, WCET optimisations often result in software that is either no more complex or even simpler than the original code. Making any change at all to the software is an additional development cost but WCET optimisations are less expensive in the development process than average-case optimisations.

Consider the following loop. The worst-case execution time is achieved when the loop iterates over all 100 elements, testing each for being zero.

for( i = 0; i < 100; ++i )
{
if( 0 == data[i] )
{
/* After first zero, all subsequent values are zero
* and we can safely exit the loop.
*/
break;
}
sum += data[i];
}

In this version of the same code, we have removed the test for zero. Now the WCET is still achieved when the loop iterates over all 100 elements but we have saved 100 tests for zero data. The code is simpler and the WCET is lower.

for( i = 0; i < 100; ++i )
{
/* After first zero, all subsequent values are zero
* and we can safely continue the loop.
*/
sum += data[i];
}

Furthermore, since the loop now always executes exactly 100 times, it lends itself to easy unrolling. In the example below there will be 25 test-and-branch operations rather than 100. Note that automatic, compiler loop unrolling is typically disabled in high-integrity projects, making such manual loop unrolling more effective than would otherwise be the case.

for( i = 0; i < 100; i += 4 )
{
sum += data[i] + data[i+1] + data[i+2] + data[i+3];
}

RapiTime cannot tell which WCET optimisations to apply to the code but it can tell where in the software such optimisations will have their biggest impact. By applying only the optimisations with the biggest effect, we minimise the number of optimisations applied and thus the development costs that arise from optimisation. This allows us to reach the point at which WCET optimisations are more cost-effective than proving timing correctness without such optimisations.

DO-178C webinars

DO178C webinars

White papers

DO178C Handbook Efficient Verification Through the DO-178C Life Cycle
A Commercial Solution for Safety-Critical Multicore Timing Analysis
Compliance with the Future Airborne Capability Environment (FACE) standard
5 key factors to consider when selecting an embedded testing tool

Related blog posts

Why Static analysis doesn't work for Multicore WCET estimation

.
2019-10-07

WCET analysis of object code with zero instrumentation

.
2017-02-27

A funny thing happened on the way to a Worst-Case Execution Time Conference...

.
2015-10-09

Things that make real-time hard - parallelization

.
2013-09-04

Pagination

  • Current page 1
  • Page 2
  • Page 3
  • Page 4
  • Page 5
  • Page 6
  • Next page Next ›
  • Last page Last »
  • Solutions
    • Rapita Verification Suite
    • RapiTest
    • RapiCover
    • RapiTime
    • RapiTask
    • MACH178

    • Verification and Validation Services
    • Qualification
    • Training
    • Integration
  • Latest
  • Latest menu

    • News
    • Blog
    • Events
    • Videos
  • Downloads
  • Downloads menu

    • Brochures
    • Webinars
    • White Papers
    • Case Studies
    • Product briefs
    • Technical notes
    • Software licensing
  • Company
  • Company menu

    • About Rapita
    • Careers
    • Customers
    • Distributors
    • Industries
    • Locations
    • Partners
    • Research projects
    • Contact
  • Discover
    • AMC 20-193
    • What is CAST-32A?
    • Multicore Timing Analysis
    • MC/DC Coverage
    • Code coverage for Ada, C & C++
    • Embedded Software Testing Tools
    • Aerospace Software Testing
    • Automotive Software Testing
    • Certifying eVTOL
    • DO-178C
    • WCET Tools
    • Worst Case Execution Time
    • Timing analysis (WCET) & Code coverage for MATLAB® Simulink®

All materials © Rapita Systems Ltd. 2023 - All rights reserved | Privacy information | Trademark notice Subscribe to our newsletter