C Compilation Architecture: Preprocessor, Compiler, Assembler, Linker0%

Setting up GCC, MinGW, and VS Code for C Development

C Compilation Architecture: Preprocessor, Compiler, Assembler, Linker

Beginner10 min read•Updated: 2026-10-22

⚙️ C Compilation Architecture: The 4-Stage Pipeline

Introduction

Unlike interpreted languages like Python or JavaScript, C is an ahead-of-time (AOT) compiled language. Before your computer can execute a .c source file, it must be transformed into binary machine code through a strict 4-stage compilation pipeline.

🔄 The 4 Stages of Compilation

1[ Source Code: main.c ]
2         │
3         ▼ (1) Preprocessor (gcc -E)
4[ Preprocessed Code: main.i ]
5         │
6         ▼ (2) Compiler (gcc -S)
7[ Assembly Code: main.s ]
8         │
9         ▼ (3) Assembler (gcc -c)
10[ Object Code: main.o ]
11         │
12         ▼ (4) Linker (gcc -o)
13[ Executable Binary: main.exe / a.out ]

Stage 1: Preprocessing (`gcc -E`)

The preprocessor scans the source file and handles all lines beginning with the hash symbol (#):

Macro Replacement: Replaces all #define macro instances with their values.
Header File Inclusion: Replaces #include <stdio.h> with the actual contents of the header file.
Comment Stripping: Removes all single-line (//) and multi-line (/* */) comments.
Conditional Compilation: Evaluates #ifdef, #ifndef, and #endif guards.

Command to inspect:

1gcc -E main.c -o main.i

Stage 2: Compilation (`gcc -S`)

The compiler takes the preprocessed .i text and converts it into hardware-specific Assembly Language (.s):

Checks syntax, static types, and semantic rules.
Generates architecture-specific instructions (x86_64 or ARM).

Command to inspect:

1gcc -S main.i -o main.s

Stage 3: Assembly (`gcc -c`)

The assembler translates human-readable assembly instructions into raw Object Code (machine code binary .o / .obj):

Creates binary bytes that the CPU understands.
Leaves external function references (such as printf) unresolved.

Command to inspect:

1gcc -c main.s -o main.o

Stage 4: Linking (`gcc -o`)

The linker combines your object file with standard C runtime libraries (libc) and other object files:

Resolves external references (finds where printf actually lives in the compiled C library).
Emits the final standalone executable binary (main.exe on Windows, main or a.out on Linux).

Command:

1gcc main.o -o main.exe

📝 Practice Quiz

1
Which compilation stage replaces #include directives with header contents?

- A) Compiler - B) Preprocessor (Correct) - C) Linker - D) Assembler

1
What is the file extension of compiled assembly output from GCC?

- A) .i - B) .o - C) .s (Correct) - D) .exe

Next Lesson

Setting up GCC, MinGW, and VS Code for C Development

Continue learning with hands-on practice, examples, and exercises in the upcoming topic.

Related Lessons

Previous Lesson	Next Lesson
History and Evolution of C Programming	Setting up GCC, MinGW, and VS Code for C Development

Practice Quiz

Test your understanding of this lesson with 1 questions. Each question has one correct answer.

Previous Next

PreviousPrevNext

MSK Institute • Shikohabad

Loading Page Content...

Preparing courses, live labs, and learning resources.सामग्री लोड हो रही है, कृपया प्रतीक्षा करें...

Connecting serverPlease wait...

💻 Practical Labs🚀 Free Demo📜 Verified Certificates

Setting up GCC, MinGW, and VS Code for C Development

C Compilation Architecture: Preprocessor, Compiler, Assembler, Linker

Beginner10 min read•Updated: 2026-10-22

Study Materials

⚙️ C Compilation Architecture: The 4-Stage Pipeline

Introduction

🔄 The 4 Stages of Compilation

1[ Source Code: main.c ]
2         │
3         ▼ (1) Preprocessor (gcc -E)
4[ Preprocessed Code: main.i ]
5         │
6         ▼ (2) Compiler (gcc -S)
7[ Assembly Code: main.s ]
8         │
9         ▼ (3) Assembler (gcc -c)
10[ Object Code: main.o ]
11         │
12         ▼ (4) Linker (gcc -o)
13[ Executable Binary: main.exe / a.out ]

Stage 1: Preprocessing (`gcc -E`)

The preprocessor scans the source file and handles all lines beginning with the hash symbol (#):

Macro Replacement: Replaces all #define macro instances with their values.
Header File Inclusion: Replaces #include <stdio.h> with the actual contents of the header file.
Comment Stripping: Removes all single-line (//) and multi-line (/* */) comments.
Conditional Compilation: Evaluates #ifdef, #ifndef, and #endif guards.

Command to inspect:

1gcc -E main.c -o main.i

Stage 2: Compilation (`gcc -S`)

The compiler takes the preprocessed .i text and converts it into hardware-specific Assembly Language (.s):

Checks syntax, static types, and semantic rules.
Generates architecture-specific instructions (x86_64 or ARM).

Command to inspect:

1gcc -S main.i -o main.s

Stage 3: Assembly (`gcc -c`)

The assembler translates human-readable assembly instructions into raw Object Code (machine code binary .o / .obj):

Creates binary bytes that the CPU understands.
Leaves external function references (such as printf) unresolved.

Command to inspect:

1gcc -c main.s -o main.o

Stage 4: Linking (`gcc -o`)

The linker combines your object file with standard C runtime libraries (libc) and other object files:

Resolves external references (finds where printf actually lives in the compiled C library).
Emits the final standalone executable binary (main.exe on Windows, main or a.out on Linux).

Command:

1gcc main.o -o main.exe

📝 Practice Quiz

1
Which compilation stage replaces #include directives with header contents?

- A) Compiler - B) Preprocessor (Correct) - C) Linker - D) Assembler

1
What is the file extension of compiled assembly output from GCC?

- A) .i - B) .o - C) .s (Correct) - D) .exe

Next Lesson

Setting up GCC, MinGW, and VS Code for C Development

Continue learning with hands-on practice, examples, and exercises in the upcoming topic.

Related Lessons

Previous Lesson	Next Lesson
History and Evolution of C Programming	Setting up GCC, MinGW, and VS Code for C Development

Practice Quiz

Test your understanding of this lesson with 1 questions. Each question has one correct answer.

Previous Next

⚙️ C Compilation Architecture: The 4-Stage Pipeline

Introduction

🔄 The 4 Stages of Compilation

Stage 1: Preprocessing (gcc -E)

Stage 2: Compilation (gcc -S)

Stage 3: Assembly (gcc -c)

Stage 4: Linking (gcc -o)

📝 Practice Quiz

Setting up GCC, MinGW, and VS Code for C Development

Related Lessons

Practice Quiz

Loading Page Content...

⚙️ C Compilation Architecture: The 4-Stage Pipeline

Introduction

🔄 The 4 Stages of Compilation

Stage 1: Preprocessing (gcc -E)

Stage 2: Compilation (gcc -S)

Stage 3: Assembly (gcc -c)

Stage 4: Linking (gcc -o)

📝 Practice Quiz

Setting up GCC, MinGW, and VS Code for C Development

Related Lessons

Practice Quiz

Stage 1: Preprocessing (`gcc -E`)

Stage 2: Compilation (`gcc -S`)

Stage 3: Assembly (`gcc -c`)

Stage 4: Linking (`gcc -o`)

Stage 1: Preprocessing (`gcc -E`)

Stage 2: Compilation (`gcc -S`)

Stage 3: Assembly (`gcc -c`)

Stage 4: Linking (`gcc -o`)