Compilation process in C - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the first step in the C compilation process?

The first step is Preprocessing. It handles directives like #include and #define, preparing the code for compilation.

beginner

What does the compiler do in the compilation process?

The compiler translates the preprocessed C code into assembly language, which is a low-level human-readable code.

intermediate

Explain the role of the assembler in the C compilation process.

The assembler converts the assembly code into machine code, which is a binary format the computer's processor understands.

intermediate

What is linking in the C compilation process?

Linking combines the machine code from your program with other code libraries to create a complete executable file.

advanced

Why is the compilation process divided into multiple steps?

Dividing compilation into steps like preprocessing, compiling, assembling, and linking helps organize the work, making it easier to find errors and optimize the program.

Which step handles #include directives in C?

A Preprocessing

B Compiling

C Assembling

D Linking

Preprocessing processes directives like #include before actual compilation.

What does the assembler produce?

A Machine code

B Source code

C Assembly code

D Executable file

The assembler converts assembly code into machine code.

Which step combines code with libraries to make an executable?

A Preprocessing

B Compiling

C Linking

D Assembling

Linking combines machine code with libraries to create the executable.

What is the output of the compiler step?

A Preprocessed code

B Assembly code

C Machine code

D Executable file

The compiler outputs assembly code from preprocessed source.

Why is preprocessing important?

A It links libraries

B It converts code to machine language

C It runs the program

D It handles directives like #define and #include

Preprocessing handles directives such as #define and #include before compilation.

Describe the four main steps of the C compilation process and what each step does.

Think about how the code changes from source to executable.

Why is linking necessary after assembling in the C compilation process?

Consider what happens when your program uses external functions.

Practice

1. Which of the following is the correct order of steps in the C compilation process?

easy

A. Preprocessing, Compilation, Assembly, Linking

B. Compilation, Preprocessing, Linking, Assembly

C. Linking, Assembly, Compilation, Preprocessing

D. Assembly, Linking, Preprocessing, Compilation

Solution

1. Step 1: Understand the compilation stages

   The C compilation process starts with preprocessing, where directives like #include are handled.

2. Step 2: Follow the correct sequence

   After preprocessing, the code is compiled into assembly, then assembled into machine code, and finally linked to create an executable.

3. Final Answer:

   Preprocessing, Compilation, Assembly, Linking -> Option A

4. Quick Check:

   Compilation steps order = A [OK]

Hint: Remember: Preprocess first, then compile, assemble, and link [OK]

Common Mistakes:

• Mixing up the order of compilation steps
• Thinking linking happens before assembly
• Confusing preprocessing with compilation

2. Which of the following commands runs the preprocessor only in GCC?

easy

A. gcc -o file file.c

B. gcc -c file.c

C. gcc -S file.c

D. gcc -E file.c

Solution

1. Step 1: Identify GCC flags for compilation steps

   The flag '-E' tells GCC to run only the preprocessor and output the result.

2. Step 2: Understand other flags

   '-c' compiles to object code, '-S' compiles to assembly, and '-o' specifies output file name.

3. Final Answer:

   gcc -E file.c -> Option D

4. Quick Check:

   Preprocessor only = gcc -E [OK]

Hint: Use gcc -E to run only the preprocessor [OK]

Common Mistakes:

• Confusing -E with -c or -S
• Using -o without understanding its purpose
• Assuming -c runs the preprocessor only

3. What will be the output of the following commands sequence?

gcc -c file.c
gcc file.o -o program
./program

Assuming file.c contains a valid main function that prints "Hello".

medium

A. Compilation error

B. Hello

C. Linker error

D. No output

Solution

1. Step 1: Understand the commands

   'gcc -c file.c' compiles source to object file without linking. 'gcc file.o -o program' links object file to create executable.

2. Step 2: Run the executable

   Running './program' executes the compiled program, which prints "Hello" as per the source code.

3. Final Answer:

   Hello -> Option B

4. Quick Check:

   Compile, link, run = Hello output [OK]

Hint: Compile with -c, then link and run to see output [OK]

Common Mistakes:

• Expecting output without linking
• Confusing compile-only with full build
• Not running the executable after linking

4. Given the code int main() { printf("Hi"); return 0; }, which error occurs if you compile with gcc file.c but forget to include #include <stdio.h>?

medium

A. Preprocessing error

B. Linker error

C. Compilation warning or error about implicit declaration

D. No error, program runs fine

Solution

1. Step 1: Identify missing header impact

   Without #include <stdio.h>, the compiler does not know the prototype of printf, causing implicit declaration warning or error.

2. Step 2: Understand error type

   This is a compilation warning or error, not a linker or preprocessing error.

3. Final Answer:

   Compilation warning or error about implicit declaration -> Option C

4. Quick Check:

   Missing stdio.h = compilation warning/error [OK]

Hint: Always include stdio.h for printf to avoid compile errors [OK]

Common Mistakes:

• Thinking it's a linker error
• Assuming no error occurs
• Confusing preprocessing errors with compilation errors

5. You have two C files: main.c and utils.c. You compile them separately with gcc -c main.c and gcc -c utils.c. What is the correct command to create an executable named app linking both object files?

hard

A. gcc main.o utils.o -o app

B. gcc main.c utils.c -c -o app

C. gcc -o app main.c utils.c

D. gcc -c main.o utils.o -o app

Solution

1. Step 1: Understand separate compilation

   Compiling with '-c' creates object files (.o) without linking.

2. Step 2: Link object files to create executable

   Use 'gcc main.o utils.o -o app' to link object files into executable named 'app'.

3. Final Answer:

   gcc main.o utils.o -o app -> Option A

4. Quick Check:

   Link object files with gcc -o app [OK]

Hint: Link .o files with gcc -o executable_name [OK]

Common Mistakes:

• Using -c flag during linking
• Trying to compile .o files directly
• Mixing source and object files incorrectly