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.

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

[RyuJIT][LSRA] Consider pre-allocating high-frequency lclVars #8019

Open
CarolEidt opened this issue May 5, 2017 · 2 comments
Open

[RyuJIT][LSRA] Consider pre-allocating high-frequency lclVars #8019

CarolEidt opened this issue May 5, 2017 · 2 comments
Assignees
Labels
area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI enhancement Product code improvement that does NOT require public API changes/additions optimization tenet-performance Performance related issue
Milestone

Comments

@CarolEidt
Copy link
Contributor

This would require the use of a different data structure for the RegRecord, at least for the non-MinOpts case, as the current data structure only tracks the register contents for the Location currently being allocated or written-back.
Consideration would need to be given to JIT throughput, possibly using an alternate representation or approach for MinOpts.
category:cq
theme:register-allocator
skill-level:expert
cost:medium

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
@ghost
Copy link

ghost commented Feb 10, 2023

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

@ghost ghost added backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity labels Feb 10, 2023
@ghost
Copy link

ghost commented Feb 24, 2023

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

@ghost ghost closed this as completed Feb 24, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Mar 26, 2023
@kunalspathak kunalspathak reopened this Sep 23, 2023
@ghost ghost removed no-recent-activity backlog-cleanup-candidate An inactive issue that has been marked for automated closure. labels Sep 23, 2023
@kunalspathak kunalspathak self-assigned this Oct 9, 2023
@dotnet dotnet unlocked this conversation Nov 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI enhancement Product code improvement that does NOT require public API changes/additions optimization tenet-performance Performance related issue
Projects
None yet
Development

No branches or pull requests

3 participants