FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [August 2009 Threads] Volatile variablesPosted by miikalo on August 27, 2009 Hi,
Is it necessary or encouraged to use volatile variables when a global variable is shared by a lower priority and a higher priority task? Thanks for your replies.
RE: Volatile variablesPosted by dave m on August 27, 2009 "Sometimes," or "it depends." It's a compiler question, not a FreeRTOS issue. If a task that uses the variable does not call any subroutines (or if the compiler can prove that the subroutines it does call never alter the variable), then the optimizer may put the variable in a register temporary, or move the test outside a loop, or something like that. The "volatile" keyword tells the compiler that it must read (and write) the variable every time the program says to do so. (The precise requirements that the compiler must meet are quite a bit more complex -- I think it may also have to ensure that volatile reads and writes happen in the same order as the program, and possibly that other memory accesses, even non-volatile ones, have completed before [or begin after] the volatile access.)
Task priority does not come into it at all. Compilers usually don't do anything different for threaded/tasked programs, and the RTOS ensures that each task can't detect context switches (registers & stack never change in ways that the compiler doesn't expect).
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|