Skip to content

memoryCopy() #5

@basxto

Description

@basxto

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

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions