XeLabs/asm_book
2
0
Fork 0
mirror of https://github.com/pkivolowitz/asm_book.git synced 2026-06-24 16:06:45 +08:00
Code Issues Projects Releases Packages Wiki Activity

making markdown lint happier

Browse source
This commit is contained in:
Perry Kivolowitz 2022-06-07 15:19:19 -05:00
parent 42e79c31dc
commit d99e803796
2 changed files with 6 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
section_1/hello_world/README.md
View file

@ -463,7 +463,6 @@ That is, subtract 8 from the stack pointer and copy `x21` to that location. Then
**The stack pointer in ARM V8 can only be manipulated in multiples of 16.**
### Line 4
When a function is passed parameters, up to 8 of them can be found in the first 8 scratch registers (`x0` through `x7`). For example, recall:

4
section_1/if/README.md
View file

@ -20,7 +20,6 @@ For simplicity, let us assume that both `a` and `b` are defined as
language. If `a` or `b` are not pointers and are not longs, `w` registers would sneak
in somewhere. See [Interlude - Registers](./section_1/regs/README.md) for more information.
## `if` in `AARCH64`
Here is the above `if` statement rendered into ARM V8 assembly language:
@ -67,7 +66,8 @@ Handling of `>=` and `<=` follow from the above.
Using the state of the condition bits (which are set by the faux subtraction of `x1`
from `x0` performed by `cmp`), branch (a jump or goto) if the previous computation shows
`less than or equal to` zero. Notice
the use of the *opposite* condition as found in the `C` code. This use of the opposite condition is not a hard and fast rule. In this case, it allows the body of the `if`
the use of the *opposite* condition as found in the `C` code.
This use of the opposite condition is not a hard and fast rule. In this case, it allows the body of the `if`
statement to be written directly below the branch so as to emulate the skipping of
the code block contained between the `if` statement's braces.