Skip to content
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

cmd/compile: don't use REP prefix for reverse-order copying on amd64, 386 #7681

Open
randall77 opened this issue Apr 1, 2014 · 2 comments
Open

cmd/compile: don't use REP prefix for reverse-order copying on amd64, 386 #7681

randall77 opened this issue Apr 1, 2014 · 2 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Unplanned

Comments

@randall77
Copy link
Contributor 

REP prefixes have a high startup cost.  Most were eliminated with CL 81370046.  For
overlapping source/destinations when we have to copy in descending address order, they
are still used.  Fix that.
@ianlancetaylor
Copy link
Member

Comment 1:

Labels changed: added repo-main, release-go1.4.

@rsc
Copy link
Contributor

rsc commented Sep 15, 2014

Comment 2:

Labels changed: added release-go1.5, removed release-go1.4.

Status changed to Accepted.

@bradfitz bradfitz modified the milestone: Go1.5 Dec 16, 2014
@rsc rsc removed accepted labels Apr 14, 2015
@rsc rsc modified the milestones: Unplanned, Go1.5 Apr 26, 2015
@rsc rsc changed the title cmd/6g, cmd/8g: don't use REP prefix for reverse-order copying cmd/compile: don't use REP prefix for reverse-order copying on amd64, 386 Jun 8, 2015
@seankhliao seankhliao added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
5 participants
@bradfitz @rsc @ianlancetaylor @randall77 @seankhliao