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

[pull] main from microsoft:main #19

Merged
merged 4 commits into from
Feb 15, 2024
Merged

[pull] main from microsoft:main #19

merged 4 commits into from
Feb 15, 2024

Conversation

pull[bot]
Copy link

@pull pull bot commented Feb 15, 2024

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

vdwtanner and others added 4 commits February 14, 2024 13:04
…_translateRcp_change"

This reverts commit 991ddfe, reversing
changes made to 2e3016a.
This is technically not to spec, as we should be using FLT_MAX here.
However, since CSGO (d3d9 version) was found to expect non-FLT_MAX
values when doing an rcp of 0, we're going to keep the out of spec
approach.

We do need the special handling for when src0 has modifiers on it though
as movc doesn't support that.
Co-authored-by: Jesse Natalie <jenatali@microsoft.com>
[Translate_RCP] Handle modifiers on src0 before performing movc

The rcp instruction is allowed to have modifiers on src0, such as _abs. When we perform the translation, src0 gets passed as the comparison param for movc, which is not allowed to have modifiers. When we detect that src0 has modifiers present, we need to handle that by doign a mov into a temp register. This was actually done in #51 , but when CSGO was found to have rendering issues after the changes the movc fix got reverted too (#55 ).

This PR brings back the movc fixes from those earlier PRs, but doesn't pick up the change to use FLT_MAX.

This is technically not to spec, as we should be using FLT_MAX here.
However, since CSGO (d3d9 version) was found to expect non-FLT_MAX
values when doing an rcp of 0, we're going to keep the out of spec
approach in case other apps have the same expectation.
@pull pull bot added the ⤵️ pull label Feb 15, 2024
@pull pull bot merged commit 423115b into ehtick:main Feb 15, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant