len0rd/FreeRTOS-Kernel
1
0
Fork 0
mirror of https://github.com/FreeRTOS/FreeRTOS-Kernel.git synced 2025-10-15 01:07:47 -04:00
Code Issues Projects Releases Packages Wiki Activity
FreeRTOS-Kernel/FreeRTOS/Test/CBMC/proofs/Task/TaskIncrementTick
History
alfred gedeon ae92d8c6ee
Add uncrustify github workflow (#659) 
* Add uncrustify github workflow

* Fix exclusion pattern

* fix find expression

* exclude uncrustify files

* Uncrustify common demo and test files

* exlude white space checking files

* Fix EOL whitespace checker

* Remove whitespaces from EOL

* Fix space at EOL

* Fix find spaces at EOL

Co-authored-by: Archit Aggarwal <architag@amazon.com>
2021-07-22 14:23:48 -07:00
..
Configurations.json Copying CBMC proofs from aws/amazon-freertos repo ./tools/cbmc to this repo ./FreeRTOS/Test/CBMC as is. 2020-03-31 14:21:53 -07:00
README.md Copying CBMC proofs from aws/amazon-freertos repo ./tools/cbmc to this repo ./FreeRTOS/Test/CBMC as is. 2020-03-31 14:21:53 -07:00
TaskIncrementTick_harness.c Add uncrustify github workflow (#659) 2021-07-22 14:23:48 -07:00
tasks_test_access_functions.h Add uncrustify github workflow (#659) 2021-07-22 14:23:48 -07:00

README.md

This proof demonstrates the memory safety of the TaskIncrementTick function. We assume that task lists are initialized and filled with a few list items. We also assign nondeterministic values to some global variables.

Configurations available:

  • default: The default configuration. useTickHook1: The default
  • configuration with configUSE_TICK_HOOK=1

This proof is a work-in-progress. Proof assumptions are described in the harness. The proof also assumes the following functions are memory safe and have no side effects relevant to the memory safety of this function:

  • prvTraceGetTaskNumber
  • prvTracePortGetTimeStamp
  • prvTraceStoreKernelCallWithNumericParamOnly
  • prvTraceStoreTaskReady
  • vApplicationTickHook