Timeline for Why use MOV R0, R3 and then MOV R3, R0 (thus back and forth)
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 4, 2022 at 23:43 | answer | added | MicroservicesOnDDD | timeline score: 1 | |
| May 21, 2020 at 11:41 | answer | added | Igor Skochinsky♦ | timeline score: 6 | |
| May 21, 2020 at 6:00 | history | tweeted | twitter.com/StackReverseEng/status/1263348856869265409 | ||
| May 20, 2020 at 21:33 | history | edited | JoHu | CC BY-SA 4.0 |
edited title
|
| May 20, 2020 at 21:08 | comment | added | Jongware |
The interface to external library functions needs r0 to contain the data to process, and it returns its result in r0 as well. The compiler doesn't know (or doesn't care), so it sets up the call, calls the library function, then restores the registers to resume what it was doing. It's just some not optimized stuff.
|
|
| May 20, 2020 at 19:19 | comment | added | 0xC0000022L♦ | Hi and welcome to RE.SE! Could you show the surroundings of the code you gave? Perhaps four more lines before and after ... | |
| May 20, 2020 at 16:04 | review | First posts | |||
| May 26, 2020 at 23:34 | |||||
| May 20, 2020 at 16:03 | history | asked | JoHu | CC BY-SA 4.0 |