Register storage class - Step-by-Step Execution

Concept Flow - Register storage class

Declare variable with 'register'

↓

Compiler tries to store variable in CPU register

↓

Variable used in code

↓

Fast access to variable

↓

End of scope: variable destroyed

The 'register' keyword suggests the compiler to store the variable in CPU register for faster access during its scope.

Execution Sample

C

#include <stdio.h>

void func() {
  register int count = 5;
  count = count + 1;
  printf("%d", count);
}

This code declares a register variable 'count', increments it, and prints the result.

Execution Table

Step	Action	Variable 'count' Value	Note
1	Declare 'count' as register int with value 5	5	Compiler tries to store 'count' in CPU register
2	Increment 'count' by 1	6	'count' updated to 6
3	Print 'count'	6	Output: 6
4	End of function scope	N/A	'count' destroyed, register freed

💡 Function ends, 'count' goes out of scope and register is freed

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
count	5	6	6	Destroyed

Key Moments - 2 Insights

Does 'register' guarantee the variable is stored in CPU register?

No, 'register' is a hint to the compiler. The compiler may ignore it if registers are limited, as shown in Step 1 of the execution_table.

Can we get the address of a 'register' variable using '&' operator?

No, you cannot take the address of a 'register' variable because it may not have a memory address, as it might be stored in a CPU register.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'count' after Step 2?

A 6

B 5

C 7

D Undefined

💡 Hint

Check the 'Variable 'count' Value' column in row for Step 2 in execution_table.

At which step does the variable 'count' get destroyed?

A Step 2

B Step 3

C Step 4

D Never

💡 Hint

Look at the 'Note' column in execution_table for when the function scope ends.

If we remove 'register' keyword, how would the execution_table change?

A Variable 'count' would not be initialized

B Variable 'count' would be stored in memory, but values and output remain same

C Output would change to 5

D Variable 'count' would not be destroyed

💡 Hint

Removing 'register' affects storage location, not the logic or output, as seen in variable_tracker.

Concept Snapshot

register storage class in C:
- Suggests compiler to store variable in CPU register
- Used for fast access to frequently used variables
- Cannot take address of register variables
- Compiler may ignore this hint
- Variable lifetime is limited to its scope

Full Transcript

This visual trace shows how a variable declared with the 'register' storage class behaves in C. The variable 'count' is declared with 'register' and initialized to 5. The compiler tries to store it in a CPU register for faster access. Then 'count' is incremented to 6 and printed. Finally, when the function ends, 'count' is destroyed and the register is freed. Note that 'register' is only a suggestion to the compiler and does not guarantee register storage. Also, you cannot take the address of a register variable. Removing 'register' changes storage location but not the program output.

Practice

1. What is the main purpose of the register storage class in C?

easy

A. To suggest storing the variable in CPU registers for faster access

B. To allocate memory on the heap

C. To make the variable global

D. To allow the variable to be accessed outside the function

Solution

1. Step 1: Understand the role of register keyword

   The register keyword suggests to the compiler that the variable should be stored in CPU registers for faster access.

2. Step 2: Compare with other storage classes

   Unlike global or heap variables, register variables are local and optimized for speed, not for scope or memory allocation.

3. Final Answer:

   To suggest storing the variable in CPU registers for faster access -> Option A

4. Quick Check:

   register means fast access [OK]

Hint: Remember: register means fast access in CPU registers [OK]

Common Mistakes:

• Thinking register allocates memory on the heap
• Assuming register variables are global
• Believing register variables can be accessed outside functions

2. Which of the following is the correct syntax to declare a register variable in C?

easy

A. int count register;

B. int register count;

C. register = int count;

D. register int count;

Solution

1. Step 1: Recall correct syntax for register declaration

   The correct syntax places the keyword register before the type: register int count;.

2. Step 2: Check other options for syntax errors

   Options A, B, and C have incorrect order or invalid assignment syntax.

3. Final Answer:

   register int count; -> Option D

4. Quick Check:

   Keyword before type = correct syntax [OK]

Hint: Put 'register' before the type name [OK]

Common Mistakes:

• Placing 'register' after the variable name
• Using assignment '=' in declaration
• Mixing order of type and storage class

3. What will be the output of the following C code?

void func() {
    register int x = 5;
    // printf("%p", &x); // Uncommenting this line causes error
    printf("%d", x);
}
int main() {
    func();
    return 0;
}

medium

A. Garbage value

B. Compilation error due to &x

C. 5

D. Runtime error

Solution

1. Step 1: Understand register variable usage

   The variable x is declared as register int, so it cannot have its address taken.

2. Step 2: Analyze the code behavior

   The commented line with &x would cause a compilation error if uncommented. But as is, the code prints the value of x, which is 5.

3. Final Answer:

   5 -> Option C

4. Quick Check:

   Printing register variable value works fine [OK]

Hint: Register variables can't use & but can print value [OK]

Common Mistakes:

• Trying to print address of register variable
• Expecting runtime error instead of compile error
• Confusing garbage value with initialized value

4. Identify the error in the following code snippet:

void example() {
    register int a = 10;
    int *p = &a;
    printf("%d", *p);
}

medium

A. Register variable cannot be initialized

B. Cannot take address of register variable

C. Pointer declaration is invalid

D. No error, code runs fine

Solution

1. Step 1: Check usage of register variable

   The variable a is declared as register int, so its address cannot be taken.

2. Step 2: Identify the error in pointer assignment

   The line int *p = &a; tries to take the address of a register variable, which causes a compilation error.

3. Final Answer:

   Cannot take address of register variable -> Option B

4. Quick Check:

   Address of register variable forbidden [OK]

Hint: Register variables have no address, so & operator causes error [OK]

Common Mistakes:

• Thinking register variables can't be initialized
• Assuming pointer declaration is wrong
• Believing code runs without error

5. Consider this code snippet:

void count() {
    register int i;
    for(i = 0; i < 3; i++) {
        printf("%d ", i);
    }
}
int main() {
    count();
    return 0;
}

What is the main advantage of using register for variable i here?

hard

A. It suggests faster access to i since it is frequently used

B. It allows taking the address of i inside the loop

C. It makes i a global variable

D. It automatically initializes i to zero

Solution

1. Step 1: Analyze the role of register in loops

   Loop variables like i are used repeatedly, so storing them in CPU registers speeds up access.

2. Step 2: Check other options for correctness

   It allows taking the address of i inside the loop is wrong because you cannot take the address of a register variable. It makes i a global variable is wrong because i is local, not global. It automatically initializes i to zero is wrong because register does not initialize variables.

3. Final Answer:

   It suggests faster access to i since it is frequently used -> Option A

4. Quick Check:

   Register = fast access for frequent vars [OK]

Hint: Register speeds up frequent variable access like loop counters [OK]

Common Mistakes:

• Thinking register allows & operator
• Assuming register makes variable global
• Believing register initializes variables automatically