Adding volatile to tasks.c's runtime information to protect against… #62
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…compiler optimization
As diskussed in https://forums.freertos.org/t/make-runtime-stats-working-with-compiler-optimization-enabled/9846 and on lined out on https://blog.the78mole.de/freertos-debugging-on-stm32-cpu-usage/, this makes run-time stats working with compiler optimizations.
Description
Protecting the runtime information against compiler optimizations, it needs some volatile added.
Test Steps
Build FreeRTOS with GENERATE_RUN_TIME_STATS and try to extract it. It will not contain valid/useful data, because the variable for total run-time was not read correctly.
Related Issue
none
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.