Volatile variables in ISR context in Embedded C - Time & Space Complexity

Time Complexity: Volatile variables in ISR context

O(n)

Understanding Time Complexity

When using volatile variables in interrupt service routines (ISRs), it's important to understand how often the code accesses these variables.

We want to see how the number of operations changes as the program runs and interrupts occur.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

volatile int flag = 0;

void ISR() {
    flag = 1;  // Set flag when interrupt occurs
}

int main() {
    while (1) {
        if (flag) {
            flag = 0;  // Clear flag
            // Handle event
        }
    }
}
    

This code sets a volatile flag in an ISR and checks it repeatedly in the main loop.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The infinite while loop in main repeatedly checks the volatile flag.
• How many times: The loop runs continuously, checking the flag many times per second.

How Execution Grows With Input

As the program runs longer, the number of flag checks grows proportionally with time.

Input Size (time units)	Approx. Operations (flag checks)
10	10 checks
100	100 checks
1000	1000 checks

Pattern observation: The number of operations grows linearly with time spent running the loop.

Final Time Complexity

Time Complexity: O(n)

This means the number of operations grows directly with the length of time the program runs.

Common Mistake

[X] Wrong: "The volatile keyword makes the flag check faster or reduces how often it runs."

[OK] Correct: Volatile only tells the compiler not to optimize away the variable; it does not change how often the code runs or how many times the flag is checked.

Interview Connect

Understanding how volatile variables behave in loops and ISRs helps you write reliable embedded code and shows you can reason about how code runs over time.

Self-Check

"What if we replaced the volatile flag with a non-volatile variable? How would the time complexity and behavior change?"

Practice

1. Why should a variable shared between an ISR (Interrupt Service Routine) and the main program be declared volatile?

easy

A. To allocate extra memory for the variable.

B. To tell the compiler the variable can change unexpectedly and prevent optimization errors.

C. To make the variable constant and unchangeable.

D. To speed up the program by caching the variable.

Solution

1. Step 1: Understand the role of volatile

   The volatile keyword tells the compiler that the variable's value can change at any time, outside the normal program flow.

2. Step 2: Apply to ISR context

   Since ISRs can change variables asynchronously, the compiler must always read the variable fresh, not use cached values.

3. Final Answer:

   To tell the compiler the variable can change unexpectedly and prevent optimization errors. -> Option B

4. Quick Check:

   Volatile prevents optimization errors in ISR variables = C [OK]

Hint: Volatile means 'may change anytime' to compiler [OK]

Common Mistakes:

• Thinking volatile makes variable constant
• Assuming volatile allocates more memory
• Believing volatile speeds up code

2. Which of the following is the correct way to declare a variable flag that is modified inside an ISR?

easy

A. const int flag;

B. int flag;

C. volatile int flag;

D. static int flag;

Solution

1. Step 1: Identify the need for volatile

   Since flag is changed inside an ISR, it must be declared volatile to prevent compiler optimizations.

2. Step 2: Check declaration syntax

   The correct syntax is volatile int flag; which tells the compiler to always read the variable fresh.

3. Final Answer:

   volatile int flag; -> Option C

4. Quick Check:

   ISR-modified variable needs volatile keyword = A [OK]

Hint: Use volatile before type for ISR-shared variables [OK]

Common Mistakes:

• Forgetting volatile keyword
• Using const which prevents changes
• Using static without volatile

3. Consider this code snippet:

volatile int flag = 0;

void ISR() {
    flag = 1;
}

int main() {
    while(flag == 0) {
        // wait for flag to change
    }
    return 0;
}

What will happen if flag was NOT declared volatile?

medium

A. The program will immediately exit the loop.

B. The program will crash at runtime.

C. The program will cause a compile-time error.

D. The program may loop forever because the compiler caches flag value.

Solution

1. Step 1: Understand compiler optimization without volatile

   Without volatile, the compiler may assume flag does not change in the loop and cache its value.

2. Step 2: Effect on the loop

   The loop condition flag == 0 may never be rechecked from memory, causing an infinite loop.

3. Final Answer:

   The program may loop forever because the compiler caches flag value. -> Option D

4. Quick Check:

   Missing volatile causes infinite loop due to caching = B [OK]

Hint: No volatile means compiler caches variable, causing infinite loops [OK]

Common Mistakes:

• Thinking program crashes without volatile
• Assuming compile error occurs
• Believing loop exits immediately

4. Given this code, what is the main problem?

int flag = 0;

void ISR() {
    flag = 1;
}

int main() {
    while(flag == 0) {
        // wait
    }
    return 0;
}

medium

A. flag should be declared volatile to avoid optimization issues.

B. ISR function must return a value.

C. flag should be declared as const.

D. main() should not have a while loop.

Solution

1. Step 1: Identify variable shared with ISR

   The variable flag is modified inside the ISR and read in main.

2. Step 2: Check declaration for optimization safety

   Since flag is shared, it must be declared volatile to prevent the compiler from caching its value.

3. Final Answer:

   flag should be declared volatile to avoid optimization issues. -> Option A

4. Quick Check:

   Shared ISR variable needs volatile keyword = D [OK]

Hint: Always declare ISR-shared variables volatile [OK]

Common Mistakes:

• Thinking ISR must return a value
• Declaring shared variable const
• Removing the loop instead of fixing volatile

5. You have a variable counter incremented inside an ISR and read in the main loop. Which of these is the best way to safely read counter in main without race conditions?

hard

A. Declare volatile int counter and disable interrupts briefly while reading it in main.

B. Declare volatile int counter and read it directly in main.

C. Declare int counter without volatile and read it directly.

D. Declare const int counter and read it in main.

Solution

1. Step 1: Understand volatile role

   Declaring counter volatile ensures main reads fresh value, but does not prevent partial updates during read.

2. Step 2: Prevent race conditions

   Disabling interrupts briefly while reading counter prevents ISR from changing it mid-read, avoiding inconsistent values.

3. Final Answer:

   Declare volatile int counter and disable interrupts briefly while reading it in main. -> Option A

4. Quick Check:

   Volatile + interrupt disable ensures safe multi-byte read = A [OK]

Hint: Disable interrupts briefly when reading multi-byte volatile variables [OK]

Common Mistakes:

• Assuming volatile alone prevents race conditions
• Not disabling interrupts during read
• Using const which prevents changes