⚙️Compilers & Runtimes
How written code becomes something a computer runs · 36 terms
Compilation
10The ways source code is turned into steps a chip can run.
Translators
3The tools that turn written code into something a machine runs, all at once or line by line.
A tool that turns all your code into one file you can run.
A program that reads your code and runs it straight away, line by line.
The parts that run most are made fast while the program runs.
Code Forms
4The shapes code takes after it is translated, from the bytes a chip reads to code for a virtual machine.
The raw steps a chip runs on its own. Compilers make it for you.
A halfway form of code. A virtual machine runs it on any computer.
Fast code that browsers run. Code in other languages is turned into it.
A file that holds a program. You can start it and it runs.
Build Steps
3The steps inside a build, from reading the text to joining the finished pieces.
A program that reads text and finds how its parts fit.
A tree that shows how the parts of a piece of code fit together.
A tool that joins built pieces of code into one program.
Runtimes
7The software that runs a program and helps it while it runs, from the JVM to the .NET runtime.
The software that runs a program. It helps the program the whole time.
The runtime that runs Java bytecode. It works on any machine that has one.
The .NET runtime. It runs C#, F# and Visual Basic code as one kind of code.
The program that runs JavaScript code. V8 is the best known.
JavaScript Runtimes
3Programs that run JavaScript outside the browser, on servers and laptops.
Memory
7Where a running program keeps its data, and how that memory is taken and given back.
How a program gets room for its data. Then it gives the room back.
A small, fast part of memory. It holds the values of running functions.
A big part of memory. Its data can last longer than one function.
A value that points to where other data is kept.
The language finds memory no one uses now. Then it frees it.
Memory a program still holds but does not need now.
A guard that stops code from using memory it does not own.
Concurrency
8Doing many things in one program over the same time, and the bugs that come from sharing data.
A running program. It has its own memory, kept apart from the rest.
One line of work in a running program. It shares the program's memory.
Handling many tasks in the same stretch of time by taking turns.
Doing many tasks at once, each on its own core.
A bug where the result depends on which task gets there first.
A lock that lets only one thread at a time touch shared data.
A lock in Python that lets one thread run Python code at a time.
Two tasks each wait for the other. So neither can ever go on.
Performance
4Measuring where a program spends its time, and keeping copies so the same work is not done twice.
Finding the parts of a program that take the most time.
A test that measures how fast code runs, so you can compare.
A fast store of copies. The same data loads quicker next time.
Clearing an old copy once the real data changes. Then no one sees old data.