Go compilation and execution flow - Step-by-Step Execution

Concept Flow - Go compilation and execution flow

Write Go source code

↓

Run 'go build' or 'go run'

↓

Compiler parses code

↓

Compiler checks syntax and types

↓

Compiler generates machine code

↓

Linker combines code and libraries

↓

Executable file created

↓

Run executable

↓

Program starts at main.main()

↓

Program executes statements

↓

Program ends and exits

This flow shows how Go source code is compiled into an executable and then run, starting from writing code to program exit.

Execution Sample

Go

package main
import "fmt"
func main() {
    fmt.Println("Hello, Go!")
}

This simple Go program prints 'Hello, Go!' when compiled and run.

Execution Table

Step	Action	Details	Result
1	Write source code	Create main.go with package main and main function	Source code file main.go created
2	Run 'go build'	Compiler reads main.go	Source code parsed successfully
3	Syntax and type check	Check for errors in code	No errors found
4	Generate machine code	Translate Go code to machine instructions	Object files created
5	Linking	Combine object files and libraries	Executable file created (main.exe or main)
6	Run executable	Start program execution	Program starts at main.main()
7	Execute statements	Call fmt.Println with "Hello, Go!"	Output: Hello, Go!
8	Program ends	main function returns	Program exits with code 0

💡 Program ends after main.main() returns, execution stops.

Variable Tracker

Variable	Start	After Step 7	Final
Output buffer	""	"Hello, Go!\n"	"Hello, Go!\n"

Key Moments - 3 Insights

Why does the program start at main.main()?

In Go, the main package's main function is the entry point. The execution_table step 6 shows the program starting there.

What happens if there is a syntax error during compilation?

The compiler stops at step 3 with an error, so no executable is created. This is why syntax checking is important before linking.

Why do we need linking after generating machine code?

Linking combines all compiled parts and libraries into one executable file, as shown in step 5 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the executable file created?

A Step 4

B Step 6

C Step 5

D Step 7

💡 Hint

Check the 'Result' column in step 5 for 'Executable file created'.

According to variable_tracker, what is the output buffer content after step 7?

A ""

B "Hello, Go!\n"

C "Hello, Go!"

D No output yet

💡 Hint

Look at the 'After Step 7' column for 'Output buffer' in variable_tracker.

If a syntax error occurs, which step in execution_table will fail?

A Step 3

B Step 2

C Step 5

D Step 7

💡 Hint

Step 3 is 'Syntax and type check' where errors are detected.

Concept Snapshot

Go compilation flow:
1. Write source code (package main, func main)
2. Run 'go build' or 'go run'
3. Compiler parses and checks code
4. Generates machine code
5. Linker creates executable
6. Run executable starting at main.main()
7. Program executes and ends

Full Transcript

This visual execution shows how Go code is compiled and run. First, you write Go source code with a main package and main function. Then, running 'go build' compiles the code: the compiler parses and checks syntax and types. If no errors, it generates machine code and links it with libraries to create an executable file. Running this executable starts the program at main.main(), which executes statements like printing text. Finally, the program ends and exits. The variable tracker shows the output buffer changes when printing. Key moments include understanding the entry point at main.main(), the importance of syntax checking, and the linking step. The quizzes test your knowledge of these steps and outputs.

Practice

1. What does the go build command do in Go programming?

easy

A. It compiles the code and creates an executable file.

B. It runs the code without compiling.

C. It only checks the code for errors without compiling.

D. It deletes the executable file.

Solution

1. Step 1: Understand the purpose of go build

   The go build command compiles Go source code into an executable binary file.

2. Step 2: Differentiate from other commands

   Unlike go run, go build does not run the program immediately but creates a file you can run later.

3. Final Answer:

   It compiles the code and creates an executable file. -> Option A

4. Quick Check:

   go build creates executable [OK]

Hint: Remember: build = compile and save executable [OK]

Common Mistakes:

• Confusing go build with go run
• Thinking go build runs the program immediately
• Believing go build only checks syntax

2. Which of the following is the correct way to compile and run a Go program in one step?

easy

A. go execute main.go

B. go build main.go

C. go run main.go

D. go compile main.go

Solution

1. Step 1: Identify the command that compiles and runs

   go run compiles the code and runs it immediately without creating an executable file.

2. Step 2: Check other options

   go build only compiles; go execute and go compile are not valid Go commands.

3. Final Answer:

   go run main.go -> Option C

4. Quick Check:

   go run compiles and runs [OK]

Hint: Use go run to compile and run instantly [OK]

Common Mistakes:

• Using go build to run directly
• Typing invalid commands like go execute
• Confusing compile-only and run commands

3. What will happen if you run the command go run main.go on a valid Go source file?

medium

A. It compiles the code, creates an executable file, and runs it.

B. It deletes the source file after running.

C. It only checks the code for errors but does not run it.

D. It compiles the code and runs it without creating an executable file.

Solution

1. Step 1: Understand go run behavior

   go run compiles the source code in memory and runs it immediately without saving an executable file.

2. Step 2: Eliminate incorrect options

   It compiles the code, creates an executable file, and runs it. is wrong because no executable file is saved. It only checks the code for errors but does not run it. is wrong because it runs the program. It deletes the source file after running. is incorrect as source files are never deleted.

3. Final Answer:

   It compiles the code and runs it without creating an executable file. -> Option D

4. Quick Check:

   go run compiles & runs, no file saved [OK]

Hint: Run with go run to skip saving executable [OK]

Common Mistakes:

• Assuming go run saves an executable
• Thinking go run only checks syntax
• Believing source files get deleted

4. You run go build on your Go program, but no executable file appears. What is the most likely reason?

medium

A. Go automatically deletes the executable after building.

B. The source file has syntax errors preventing compilation.

C. The executable is created but hidden in a different directory.

D. The go build command only runs the program, not build it.

Solution

1. Step 1: Understand go build behavior on errors

   If the source code has syntax errors, go build will fail and not create an executable file.

2. Step 2: Check other options

   go build does not run the program, executables are created in the current directory by default, and Go does not delete executables automatically.

3. Final Answer:

   The source file has syntax errors preventing compilation. -> Option B

4. Quick Check:

   Syntax errors block build, no executable made [OK]

Hint: Check for syntax errors if no executable appears [OK]

Common Mistakes:

• Expecting go build to run the program
• Looking in wrong directories without checking errors
• Assuming Go deletes executables automatically

5. You want to quickly test a small Go program without creating an executable file. Which command should you use and why?

hard

A. Use go run because it compiles and runs the program without saving an executable.

B. Use go build because it compiles and runs the program immediately.

C. Use go install because it runs the program without compiling.

D. Use go test because it compiles and runs the program.

Solution

1. Step 1: Identify the command for quick testing

   go run compiles and runs the program immediately without creating an executable file, perfect for quick tests.

2. Step 2: Understand why other commands don't fit

   go build creates an executable but does not run it. go install compiles and installs packages, not for quick runs. go test runs tests, not general programs.

3. Final Answer:

   Use go run because it compiles and runs the program without saving an executable. -> Option A

4. Quick Check:

   Quick test = go run [OK]

Hint: Use go run for quick compile-and-run tests [OK]

Common Mistakes:

• Using go build expecting immediate run
• Confusing go install with running code
• Trying go test for normal program execution