diff options
author | Alejandro PiƱeiro <[email protected]> | 2015-12-19 12:15:00 +0100 |
---|---|---|
committer | Eduardo Lima Mitev <[email protected]> | 2016-03-03 15:14:06 +0100 |
commit | e976a30db8f24ec81259140f157a224c49aa373e (patch) | |
tree | fc4d62b14931673228436000f4d907d9e529edf0 /VERSION | |
parent | c5cf16a4fcf64eb1f6b5923e0d46b3f7dfee23a9 (diff) |
mesa/formatquery: support for MAX_COMBINED_DIMENSIONS
It is implemented combining the values returned by calls to the 32-bit
query _mesa_GetInternalformati32v.
The main reason is simplicity. The other option would be C&P how we
implemented the support of GL_MAX_{WIDTH/HEIGHT/DEPTH} and GL_SAMPLES.
Additionally, doing this way, we avoid adding checks on the code, as
are done by the call to the query itself.
MAX_COMBINED_DIMENSIONS is the only pname pointed on the spec of
needing a 64-bit query. We handle that possibility by packing the
returning value on the two first 32-bit integers of params. This
would work on the 32-bit query as far as the value is not greater
that INT_MAX. On the 64-bit query wrapper we unpack those values
in order to get the final value.
Reviewed-by: Dave Airlie <[email protected]>
Diffstat (limited to 'VERSION')
0 files changed, 0 insertions, 0 deletions