Register storage class - Time & Space Complexity

Time Complexity: Register storage class

O(n)

Understanding Time Complexity

Let's see how using the register storage class affects how fast a program runs.

We want to know if it changes how the program's speed grows when input gets bigger.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

void countToN(int n) {
    register int i;
    for (i = 0; i < n; i++) {
        // do something simple
    }
}
    

This code counts from 0 up to n-1 using a register variable for the loop counter.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop runs a simple operation inside.
• How many times: It runs exactly n times, where n is the input size.

How Execution Grows With Input

As n grows, the loop runs more times, so the total work grows in a straight line with n.

Input Size (n)	Approx. Operations
10	10
100	100
1000	1000

Pattern observation: The work grows evenly as n grows; doubling n doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows directly in proportion to the input size.

Common Mistake

[X] Wrong: "Using register makes the loop run faster and changes the time complexity."

[OK] Correct: Register may speed up access but does not change how many times the loop runs, so the overall growth stays the same.

Interview Connect

Understanding how storage classes affect performance helps you explain code efficiency clearly and confidently.

Self-Check

"What if we replaced the register variable with a normal variable? How would the time complexity change?"

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