Skip to content

[MachinePipeliner] Skip reserved registers when computing register pressure #120694

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

Merged
merged 1 commit into from
Dec 20, 2024

Conversation

wangpc-pp
Copy link
Contributor

We used to skip fixed registers, but fixed registers are not enough
because there are some runtime unusable registers like registers
reserved by -ffixed-xxx options.

Here we change to use reserved registers so that the estimated
pressure is more accurate.

…essure

We used to skip fixed registers, but fixed registers are not enough
because there are some runtime unusable registers like registers
reserved by `-ffixed-xxx` options.

Here we change to use reserved registers so that the estimated
pressure is more accurate.
Copy link
Contributor

@kasuga-fj kasuga-fj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

@wangpc-pp wangpc-pp merged commit d66f653 into llvm:main Dec 20, 2024
9 checks passed
@wangpc-pp wangpc-pp deleted the main-machine-pipeliner-fixed-reg branch December 20, 2024 10:32
@mikaelholmen
Copy link
Collaborator

Hello @wangpc-pp

After this patch the MF member seem to be unused:

../lib/CodeGen/MachinePipeliner.cpp:1219:26: error: private field 'MF' is not used [-Werror,-Wunused-private-field]
 1219 |   const MachineFunction &MF;
      |                          ^
1 error generated.

@mikaelholmen
Copy link
Collaborator

And now I see it was just fixed in d7ddc97
[MachinePipeliner] Remove unused private field MF

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants