If you remember when we talked about the operating system ABI and calling conventions earlier, you probably remember that each architecture and OS have different requirements. This is especially important
Before we start, I want to make sure you understand that the code we write is quite unsafe and is not a “best practice” when writing Rust. I want to
Note The actual addresses you get will be different every time you run the program. In other words, the values 240, 205, 252, 56, 67, 86, 0, 0 represent the
Tip As we end the program in an endless loop, you’ll have to exit by pressing Ctrl + C. OK, so what happened? We didn’t call the function hello at
There seems to be an issue in macOS using such a small stack. The minimum for this code to run is a stack size of 624 bytes. The code works
Note We will use the Intel dialect in our examples. Assembly has strong backward compatibility guarantees. That’s why you will see that the same registers are addressed in different ways.
To find the architecture on your current system, run one of the following commands in your terminal: On Linux and MacOS: arch or uname -m On Windows PowerShell: $env:PROCESSOR_ARCHITECTURE On