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

[NFC] update print functions for PSV #6887

Closed
wants to merge 1 commit into from

Conversation

python3kgae
Copy link
Contributor

@python3kgae python3kgae commented Aug 28, 2024

Update print functions to share with validation.
This change is part of a big change for #6817 where the print function is shared between the DxilPipelineStateValidation::Print and the psv content validation.

Move this change out of the big change to help review.

For #6817

Update print functions to share with validation.

For microsoft#6817
@python3kgae python3kgae requested a review from a team as a code owner August 28, 2024 22:13
@damyanp
Copy link
Member

damyanp commented Sep 4, 2024

I don't understand why this change is being made. Can you add some explanation please to the description? Is this just refactoring? If so, why? Or is there actually some functional change in here?

Comment on lines +363 to +366
Print(OS, GetSemanticName());
}

void PSVSignatureElement::Print(raw_ostream &OS, const char *Name) const {
Copy link
Member

Choose a reason for hiding this comment

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

I'm trying to figure out the motivation for this change? Is there some place now where we want a name other than what GetSemanticName() returns to be displayed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is for validation to print Signature Element where SemanticName is not in StringTable.

Copy link
Member

Choose a reason for hiding this comment

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

I guess I don't have enough context to understand what that means. So sometimes PSVSignatureElement doesn't contain the data it needs?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is for emit error message on a PSVSignatureElement generated from DxilSiginatureElement which doesn't have SemanticName setup. The SemanticName will be get from the DxilSiginatureElement.

Copy link
Member

Choose a reason for hiding this comment

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

This may be a case of PR being sliced too far away from the code that makes it possible to understand the change.

@python3kgae python3kgae closed this Sep 4, 2024
@python3kgae python3kgae deleted the psv_dump_update branch September 4, 2024 23:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants