Skip to content

cmd/compile: call memmove on amd64 for large OpMove #25317

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
TocarIP opened this issue May 9, 2018 · 0 comments
Open

cmd/compile: call memmove on amd64 for large OpMove #25317

TocarIP opened this issue May 9, 2018 · 0 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Performance
Milestone
Unplanned

Comments

@TocarIP
Copy link
Contributor

TocarIP commented May 9, 2018

Currently we lower OpMove with large size into REP MOV.
Memmove has optional AVX&co codepath, so it should be faster than REP MOV, or at least as fast if REP MOV is optimal (call overhead is insignificant for large sizes). We should probably generate a call to memmove for really big OpMove.
@agnivade agnivade added this to the Unplanned milestone May 13, 2018
@ALTree ALTree added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jul 22, 2020
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Performance
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
4 participants
@agnivade @ALTree @gopherbot @TocarIP