Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
According to Wikipedia the Intel ABI allows using EAX, ECX and EDX without preserving them in a function.
I am not sure what “Intel ABI” means. Does this mean it is enforced/followed by all compilers targeting Intel CPUs? I am writing an assembly function that will be called from C code. Can I assume this for all compilers? (I am only targeting x86 at the moment)
The Intel ABI is just a calling convention established by Intel.
In general, how parameters are passed and which registers are saved or trashed during a function call is defined by the Calling convention of the function:
http://en.wikipedia.org/wiki/Calling_convention
In particular for __cdecl, __stdcall and __fastcall you should expect EAX, ECX and EDX to be trashed, and your function should preserve other registers and return on EAX (or EDX:EAX for 64-bit returns).
If you don’t know what the calling convention that you should be using is, you shouldn’t be writing in assembly, since messing up the calling convention can lead to exploitable bugs in your application.
In C, the default calling convention is normally __cdecl and for Windows exported APIs it is normally __stdcall.