|
You are here |
www.cs.virginia.edu | ||
| | | | |
gpfault.net
|
|
| | | | | [AI summary] The text provides an in-depth exploration of various x86-64 instruction set architectures, focusing on arithmetic operations (ADD, SUB, MUL, SMUL, DIV, SDIV), logical operations (AND, OR, XOR, NOT), and control flow instructions. It details the implementation of these instructions in the QBX virtual machine, emphasizing how they emulate real x86-64 instructions while managing the flags register and handling different operand sizes (8-bit and 16-bit). The text also discusses the nuances of flag handling, register operations, and macro-based code generation to streamline instruction implementation. | |
| | | | |
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. | |
| | | | |
0x44.cc
|
|
| | | | | [AI summary] The article provides an in-depth explanation of reverse engineering concepts, including CPU operations, memory representation, data structures, and disassembly techniques. It guides readers through understanding machine code, endianness, signed integers, and how to analyze C code using tools like Visual Studio and disassemblers. | |
| | | | |
andreabergia.com
|
|
| | | This post is part of the Writing a JVM in Rust series. In this post, I will discuss how rjvm parses .class files. The code I will discuss today is contained in the reader crate. A warning before you read: this is the earliest part of the project and, since I have written this project to learn Rust, it is also the one that contains the least idiomatic code. Don't take this as an example of the best Rust ever written! | ||