/explore
|
You are here 
|
cs.lmu.edu | ||
| | | | |
gpfault.net
|
|
| | | | | [AI summary] The provided text is a detailed explanation of how to write a simple 64-bit Windows application in assembly language that calls the ExitProcess function from the KERNEL32.DLL library. It covers the following key topics: 1. **Memory and Register Basics**: Explains how memory and registers work in 64-bit Windows, including the use of the stack pointer (RSP), registers like RCX, RDX, R8, and R9 for passing arguments, and the importance of stack alignment for performance. 2. **Calling Conventions**: Details the 64-bit Windows calling convention, including how the first four integer or pointer arguments are passed in registers (RCX, RDX, R8, R9), how additional arguments are passed on the stack, and the requirement for the stack to be aligned to ... | |
| | | | |
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. | |
| | | | |
www.cs.virginia.edu
|
|
| | | | | [AI summary] This comprehensive guide explains the fundamentals of 32-bit x86 assembly language programming, including registers, memory addressing, instructions, and calling conventions. | |
| | | | |
konradreiche.com
|
|
| | | Writing a generic protobuf writer in Go is straightforward. We simply use proto.Marshal with the protobuf message because proto.Marshal expects the proto.Message interface, which all generated protobuf messages implement. However, when it comes to reading serialized protobuf data into a specific Go type, historically, we had to specify the type explicitly: var post pb.Post if err := proto.Unmarshal(b, &post); err != nil { return nil, err } This approach is clear and explicit: what you see is what you get. But what if you need a more generic solution? You might encounter a scenario similar to mine: a cache abstraction designed to handle different kinds of protobuf messages generically. My initial attempt looked like this: | ||
