Re: [PATCH 0/1] MR5061: d3d10/tests: Avoid implicit cast changing value.

[Matteo Bruni (＠Mystral)]

So, what's happening is that UINT_MAX can't be represented exactly as a float and the closest integer number happens to be UINT_MAX + 1? If so, I'd expect the same happens in the implementation (including native) and I think I'd rather lean the same way with the test e.g. by explicitly casting UINT_MAX to float instead.