-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
What’s the reasoning behind memoryCopy()?
It looks pretty much like memcpy
Is it to avoid 16bit n and to avoid putting the arguments on the stack?
Edit:
I think it was mostly for reusing n and to avoid the stack.
I kept n in a variable with the new calling convention, that generates smaller code than memcpy, but I didn’t look at speed.
Metadata
Metadata
Assignees
Labels
No labels