/explore
|
You are here 
|
venam.net | ||
| | | | |
venam.nixers.net
Computer architecture can be considered a boring topic, one that is studied during CS education, then put aside, and leaves place to the shiny new toys that capture the attention. I've recently revisited it, and I'd like to summarize some takeaways. |
|
| | | | | ||
| | | | |
cpu.land
Curious exactly what happens when you run a program on your computer? Learn how multiprocessing works, what system calls really are, how computers manage memory with hardware interrupts, and how Linux loads executables. |
|
| | | | | ||
| | | | |
www.nayuki.io
[AI summary] The user has provided a comprehensive overview of the x86 architecture, covering topics such as basic arithmetic operations, control flow with jumps and conditionals, memory addressing modes, the stack and calling conventions, advanced instructions like SSE, virtual memory, and differences between x86-32 and x86-64. The user is likely looking for a summary or clarification of the x86 architecture, possibly for learning purposes or to reinforce their understanding. |
|
| | | | | ||
| | | | |
blog.stephenmarz.com
[AI summary] The text provides an in-depth explanation of how C programs are compiled into assembly and machine code, focusing on various aspects such as data types, memory sections, control structures, and the role of the compiler in making decisions about load/store operations and shifts. It covers topics like data type conversions, padding in structures, global variables, and branch instructions for conditions and loops. The text also mentions the importance of understanding assembly for learning how compilers work and the use of tools like objdump for analyzing compiled code. |
|
| | | |||
