Hash :
dccc0f8c
Author :
Date :
2021-10-05T09:22:19
Add docs for DXGI and D3D11 format tables. Bug: angleproject:1691 Change-Id: I7a07228853aaf8f1536b145657a737dcf3e0e1f1 Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/3205798 Commit-Queue: Jamie Madill <jmadill@chromium.org> Reviewed-by: Geoff Lang <geofflang@chromium.org>
The D3D11 back-end uses a code generator to initialize D3D11 format info.
The generator is gen_texture_format_table.py
and uses data stored in texture_format_data.json
and texture_format_map.json. The “format map”
maps from a GLES front-end format to the ANGLE format which represents the
format we use in D3D11. The “format data” indicates which DXGI formats we
use to represent an ANGLE format in the D3D11 back-end.
Note that the “format data” can also encode support for fallback formats.
The supportTest attribute indicates a runtime check we can use to determine
if we should use the fallbackFormat instead of the default format.
# D3D11 back-end format tables
The D3D11 back-end uses a code generator to initialize D3D11 format info.
The generator is [`gen_texture_format_table.py`](gen_texture_format_table.py)
and uses data stored in [`texture_format_data.json`](texture_format_data.json)
and [`texture_format_map.json`](texture_format_map.json). The "format map"
maps from a GLES front-end format to the ANGLE format which represents the
format we use in D3D11. The "format data" indicates which DXGI formats we
use to represent an ANGLE format in the D3D11 back-end.
Note that the "format data" can also encode support for fallback formats.
The `supportTest` attribute indicates a runtime check we can use to determine
if we should use the `fallbackFormat` instead of the default format.