Use markdown style lists
This commit is contained in:
parent
2091516544
commit
307b59584f
17 changed files with 120 additions and 120 deletions
10
08-02.md
10
08-02.md
|
|
@ -119,14 +119,14 @@ More on this shortly.
|
|||
To recap, here are some things to look for when striving to convert C
|
||||
code into optimized assembly language:
|
||||
|
||||
- Move the entire performance-critical section into a single assembly
|
||||
* Move the entire performance-critical section into a single assembly
|
||||
language function.
|
||||
- Don't use calls or stack frame accesses inside the critical code, if
|
||||
* Don't use calls or stack frame accesses inside the critical code, if
|
||||
possible, and avoid unnecessary memory accesses of any kind.
|
||||
- Change segments as infrequently as possible.
|
||||
- Optimize in terms of what assembly does well, *not* in terms of
|
||||
* Change segments as infrequently as possible.
|
||||
* Optimize in terms of what assembly does well, *not* in terms of
|
||||
fine-tuning compiled C code.
|
||||
- Change the rules to the benefit of assembly, if necessary; for
|
||||
* Change the rules to the benefit of assembly, if necessary; for
|
||||
example, reorganize data structto allow efficient assembly language
|
||||
processing.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue