We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Since we don't have a convention on register usage, how about making one, like for x86?
A convention on register naming would make writing libraries and creating calling conventions easier.
What do I propose:
B is always pushed when calling a subroutine. Other registers (except for Z) are preserved if needed.
The text was updated successfully, but these errors were encountered:
I think we can use the A register for the return value
Sorry, something went wrong.
Why not Z? Z is the last Latin letter, symbolizes end of a function. A looks more general-purpose.
There is already a register convention in the coding style guide line. I don't see why we would need to be more strict in this area.
On Sunday, September 9, 2012, SiPlus notifications@github.com wrote:
Why not Z? Z is the last English letter, symbolizes end of a function. — Reply to this email directly or view it on GitHub.
Why not Z? Z is the last English letter, symbolizes end of a function.
— Reply to this email directly or view it on GitHub.
Regards, James Rhodes. Redpoint Software
http://about.me/james.rhodes
No branches or pull requests
Since we don't have a convention on register usage, how about making one, like for x86?
A convention on register naming would make writing libraries and creating calling conventions easier.
What do I propose:
B is always pushed when calling a subroutine. Other registers (except for Z) are preserved if needed.
The text was updated successfully, but these errors were encountered: