Explore >> Select a destination
|
You are here 
|
gpfault.net | ||
| | | | |
nfraprado.net
|
|
| | | | | ||
| | | | |
patshaughnessy.net
|
|
| | | | | [AI summary] The article discusses the process of learning to read x86 assembly language, focusing on how it can be a useful skill for understanding low-level operations of microprocessors. It outlines the challenges of reading assembly, especially in debugging scenarios, and provides an example of translating Ruby code into x86 assembly using Crystal. The article also explains the syntax and structure of x86 assembly, including register usage, instruction suffixes, and the differences between AT&T and Intel syntax. It highlights the complexity of x86 assembly due to its historical evolution and the need for understanding register sizes and operand notation. | |
| | | | |
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. | |
| | | | |
jborza.com
|
|
| | | Closer to the machine I started my way with programming with Microsoft QBASIC on DOS, I did try (and succeed) to copy code for a game from a BASIC book, and it did run, but I didnt really get development back then. I didnt really understand how and why it works, and most importantly, how to write my own code to implement a different game. Later I was playing higher level languages such as Pascal and C in the high school and PHP at home. | ||
