| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
going in here (at least eventually, and potentially soon-ish)
|
| |
|
| |
|
|
|
|
| |
instruction scheduling
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Switch the remaining MOV() macros to ASSIGN()
Clean up the macro definitions a little
|
|
|
|
| |
Use the ASSIGN() macro in a couple of places that I hadn't touched
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
macros.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to memory for it.
|
|
|
|
| |
lot of work.
|
|
|
|
| |
easily rearrange things for better scheduling.
|
| |
|
|
|
|
| |
incrementing the pointer
|
| |
|
| |
|
|
|
|
| |
instruction scheduling and code cleanup.
|
|
|
|
| |
macros in an attempt to keep the code reasonably clean.
|
| |
|
|
|
|
| |
for performing operations.
|
|
|