Vulkan: Avoid INT_MAX resource limits
dEQP queries resource limits in all formats, including float. When
INT_MAX is queried as float, the resulting value is INT_MAX+1 due to
floating point imprecision. dEQP casts this value back to int for
verification, and trips up on the resulting negative number.
This change limits every ridiculously-large limit to INT_MAX/2 instead
of INT_MAX.
Bug: angleproject:4309
Change-Id: I11018c2c5a0c8bfb410928b0a4c34c526fab2269
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2006813
Commit-Queue: Ian Elliott <ianelliott@google.com>
Reviewed-by:
Jamie Madill <jmadill@chromium.org>
Reviewed-by:
Ian Elliott <ianelliott@google.com>
Showing
Please
register
or
sign in
to comment