cli/q
Code Issues 1 Pull Requests Activity

Improved documentation

Browse Source
This commit is contained in:
Eduard Urbach
2025-01-28 14:04:30 +01:00
parent 9a8cffe2f4
commit 92e4175bbd
4 changed files with 58 additions and 71 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
src/build/readme.md Normal file
View File

@ -0,0 +1,19 @@
### [Build.go](Build.go)
The `Build` type defines all the information needed to start building an executable file.
The name of the executable will be equal to the name of the build directory.
`Run` starts the build which will scan all `.q` source files in the build directory.
Every source file is scanned in its own goroutine for performance reasons.
Parallelization here is possible because the order of files in a directory is not significant.
The main thread is meanwhile waiting for new function objects to arrive from the scanners.
Once a function has arrived, it will be stored for compilation later.
We need to wait with the compilation step until we have enough information about all identifiers from the scan.
Then all the functions that were scanned will be compiled in parallel.
We create a separate goroutine for each function compilation.
Each function will then be translated to generic assembler instructions.
All the functions that are required to run the program will be added to the final assembler.
The final assembler resolves label addresses, optimizes the performance and generates the specific machine code from the generic instruction set.