Skip to content

[pred-memopt] Replace remaining occurances of prefix DI with PMO prefix. #16774

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

Conversation

gottesmm
Copy link
Contributor

I am going to DI and predictable mem opts have been split for a long time and
their subroutines aren't going to be joined in the future... so replace the DI
prefixes in pred-mem-opts impl with PMO and rename DIMemoryUseCollector =>
PMOUseCollector.

Been sitting on this for a long time... just happy to get it in.


@atrick this is a pretty straight forward conversion. Can you take a look and make sure I didn't miss anything? I think eventually we will want to re-unify some parts of the implementations (for instance I think we could unify DIMemoryInfo and PMOMemoryInfo).

I ran into this in my local git repo while looking at some other stuff... I just wanted to get it into GitHub. So there isn't a rush with this, but can you take a look sooner rather than later?

I am going to DI and predictable mem opts have been split for a long time and
their subroutines aren't going to be joined in the future... so replace the DI
prefixes in pred-mem-opts impl with PMO and rename DIMemoryUseCollector =>
PMOUseCollector.

Been sitting on this for a long time... just happy to get it in.
@gottesmm gottesmm requested a review from atrick May 22, 2018 19:55
@gottesmm
Copy link
Contributor Author

@swift-ci smoke test

@@ -11,22 +11,22 @@
//===----------------------------------------------------------------------===//
Copy link
Contributor

Choose a reason for hiding this comment

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

How about a file comment explaining what PMO means, and how this differs from DIMemoryUseCollectorOwnership. Are you going to rename DIMemoryUseCollectorOwnership to DIMemoryUseCollector now? Otherwise, it looks like this is all reformatting. Seems fine to me.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes. I can add a comment calling out that this PMO means Predictable Memory Operations. The main thing I am trying to do is finish that transition so I am going to rename do DIMemoryUseCollector.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I am going to do that in a follow up commit.

@gottesmm gottesmm merged commit ed6bcde into swiftlang:master May 29, 2018
@gottesmm gottesmm deleted the pr-e9a2e719f8fe7c5d31d0258bc42e15ae56d59fb0 branch May 29, 2018 00:06
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.

2 participants