Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

Thanks! I'm reading the links. I've readed that argument about the varargs, but i think it could be implemented using registers, am i missing something?

Nande
– Nande

2015-10-21 04:53:21 +00:00
Commented Oct 21, 2015 at 4:53
Your goal should be to not do something exotic. The closer you are to a generally-accepted standard, the better.

Robert Harvey
– Robert Harvey

2015-10-21 05:08:04 +00:00
Commented Oct 21, 2015 at 5:08
1

That's not my objective. I'm trying to learn (about the other calling conventions).

Nande
– Nande

2015-10-21 05:14:35 +00:00
Commented Oct 21, 2015 at 5:14
That link is cool. i like the first 3 sentences in your post. also it says "The user-stack is not touched, so you needn't have a valid one when doing a syscall." is that a pro? i don't need to set up a proper stack?

Nande
– Nande

2015-10-21 05:28:26 +00:00
Commented Oct 21, 2015 at 5:28

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »