-
Notifications
You must be signed in to change notification settings - Fork 712
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
[DXIL] Null pointer exception due to double floating-point literals in fmod intrinsic (in 1.8.2403 release) #6419
Milestone
Comments
tex3d
added a commit
that referenced
this issue
Mar 14, 2024
tex3d
added a commit
that referenced
this issue
Mar 21, 2024
Certain HL ops with no double overload will generate double overloads for literal types. These are lowered to double DXIL overloads, some of which are not legal for these ops. We currently rely on illegal intermediate DXIL op overloads for constant evaluation. If constant evaluation fails, we end up with illegal DXIL overloads in final DXIL, which is caught by the validator. The prior revert restored the ability to run these scenarios (with asserts disabled). This change adds tests for #6419 so automated testing will test across configurations and prevent regressions of this scenario in this branch.
Fixed by #6418 |
pow2clk
pushed a commit
to pow2clk/DirectXShaderCompiler
that referenced
this issue
Jul 17, 2024
…soft#6437) Certain HL ops with no double overload will generate double overloads for literal types. These are lowered to double DXIL overloads, some of which are not legal for these ops. We currently rely on illegal intermediate DXIL op overloads for constant evaluation. If constant evaluation fails, we end up with illegal DXIL overloads in final DXIL, which is caught by the validator. The prior revert restored the ability to run these scenarios (with asserts disabled). This change adds tests for microsoft#6419 so automated testing will test across configurations and prevent regressions of this scenario in this branch. (cherry picked from commit 9c2b828)
pow2clk
added a commit
that referenced
this issue
Jul 17, 2024
#6799) Certain HL ops with no double overload will generate double overloads for literal types. These are lowered to double DXIL overloads, some of which are not legal for these ops. We currently rely on illegal intermediate DXIL op overloads for constant evaluation. If constant evaluation fails, we end up with illegal DXIL overloads in final DXIL, which is caught by the validator. The prior revert restored the ability to run these scenarios (with asserts disabled). This change adds tests for #6419 so automated testing will test across configurations and prevent regressions of this scenario in this branch. (cherry picked from commit 9c2b828) Co-authored-by: Tex Riddell <texr@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue tracks #6410, but specifically in the release branch. See the main issue for full information.
The text was updated successfully, but these errors were encountered: