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

incr.comp.: Do per-MonoItem dependency tracking in order to collect data about granularity fallout. #48211

Open
michaelwoerister opened this issue Feb 14, 2018 · 0 comments
Labels
A-incr-comp Area: Incremental compilation C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@michaelwoerister
Copy link
Member

Currently the compiler only allocates a single DepNode per CGU. This is enough for implementing object file re-use but we are losing information about what items within an object file exactly caused it to be re-compiled. In order to gather more information about how CGU partitioning affects re-use, it would be good to know which MonoItems within a CGU were changed and which were not.

Before making this the default though, we should check how it affects the number of DepNodes and edges in the graph.

@michaelwoerister michaelwoerister added the A-incr-comp Area: Incremental compilation label Feb 14, 2018
@XAMPPRocky XAMPPRocky added C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Apr 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-incr-comp Area: Incremental compilation C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

2 participants