So what actually happens inside the computer when you compile and execute a program
I COME FROM THE NET
>>107749715
>>107749715your executable is loaded into memory, the instruction pointer is pointed to wherever the EXE file header directs it, and then execution of your program starts
>>107749715Executing a program tells the computer which transitors to switch in which order so that some data ends up in the correct place in the RAM or registers of the cpu. Different CPU architectures use different circuits, so the instructions have to change which is why you need to recompile a program if you want to use it on a different CPU architecture.Think of it like this: you have machine and someone tells you to flick the switch, turn a knob and then press the start button. Then you get another machine and want to use the same instructions, but then you realize that this machine doesn't even have a knob so you have to ask for new instructions.
the transistors flip from off to on and it looks something like this
>>107751631But wounl But wouldn't t haBut wouldn't that result in a lot of BUGS?!? Hahaha ho ho ho
>>107749715something something jews something something adolf hitler
>>107749715electrons move back and forthhow detailed do you want?
>>107749715Electrons race around the circuitry in logic-based patterns encoded by the symbols that represent the program that was compiled and executed.
>>107749715Learn assembly and find out
the elves carry the program sir
>>107749715For every file loaded, the OS running in the CPU will tell the SSD and DMA to work in tandem and copy certain specific sectors from the disk to the RAM, and they will eventually do it.So the OS will do the above to load the compiler and the compiler will do it to every source file.Then it will scan the source files line by line creating several tables based on it that will later be used to construct a program (that is basically a list of instructions). the compiler will also do tricks such as copy pasting the content of functions to places calling these functions to make the program run faster, and unroll loops.This will normally generate a file per source file, and finally, the compiler (or a dedicated linker program) will get all the files and connect all the functions and such into a single cohesive package that you call a program.Then when you tell the OS to load the program, it will do the process above but for the file of the program.
>>107752999>shrinks that shit
>>107752999A little messy with the opcode jumpers but still better than the original. GG anon. Now can you please fix the dogpile that is reprogramming the firmware? TIA.
>>107749715>So what actually happens inside the computer when you compile and execute a programThe "compile" part is outside the scope of this thread. But the execute part is accessible to any White man of modest diligence.https://archive.org/details/jclarkscottbuthowdoitknowthebasicprinciplesofcomputersforeveryonejohnc.scott2009https://www.youtube.com/playlist?list=PLYE0XunAbwfDvfabOlNWLViRcMI54M6CR
>>107749715it's a series of tubes
>>107749715You commune with the demonic realm.
