[Bug 54150] New: d3dcompiler_43:hlsl_d3d11 & d3dcompiler_43:hlsl_d3d11 - test_trig() fails on w11pro64_nv

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=54150

Bug ID: 54150
           Summary: d3dcompiler_43:hlsl_d3d11 & d3dcompiler_43:hlsl_d3d11
                    - test_trig() fails on w11pro64_nv
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: d3d
          Assignee: [e-mail]
          Reporter: [e-mail]

d3dcompiler_43:hlsl_d3d11 & d3dcompiler_43:hlsl_d3d11 - test_trig() fails on
w11pro64_nv:

hlsl_d3d11.c:504: Test failed: Test 300: Got {-9.99755323e-001,
-2.21209023e-002, 0.00000000e+000, 0.00000000e+000}, expected
{-9.99755859e-001, -2.20966193e-002, 0.00000000e+000, 0.00000000e+000}.
hlsl_d3d11.c:504: Test failed: Test 600: Got {4.42310758e-002,
-9.99021292e-001, 0.00000000e+000, 0.00000000e+000}, expected {4.41824496e-002,
-9.99023479e-001, 0.00000000e+000, 0.00000000e+000}.

See https://test.winehq.org/data/patterns.html#d3dcompiler_43:hlsl_d3d11
    https://test.winehq.org/data/patterns.html#d3dcompiler_47:hlsl_d3d11

This test only fails on w11pro64_nv: there is no issue on the other test
configurations, particularly on  w11pro64_amd.

(-2.21209023e-002 - -2.20966193e-002) / -2.20966193e-002 = ~ 0.0011

Should the test should allow for a larger imprecision? But the first y result
feels like it's off by a lot already.