diff options
author | Erik Faye-Lund <[email protected]> | 2019-03-06 12:18:28 +0100 |
---|---|---|
committer | Erik Faye-Lund <[email protected]> | 2019-04-29 10:28:38 +0000 |
commit | be110ba2e4d5f8e5c71294d29dc991f4b6600e79 (patch) | |
tree | 34cc4fa27f30fa6a0750585ce6ac95994d03f3e6 /src/mesa/state_tracker/st_cb_flush.c | |
parent | ef13691e0c07d909a4f14280ca4fefbd79a9865b (diff) |
mesa/st: accept NULL and empty buffer objects
It's prefectly legal and well-defined to render using a non-existing
or empty buffer object. The data coming out of the buffer object isn't
well defined unless we have the robustness flag set on the context, but
that's a different matter, and up to the shader hardware; it's the same
as out-of-bounds reads.
Signed-off-by: Erik Faye-Lund <[email protected]>
Reviewed-by: Marek Olšák <[email protected]>
Diffstat (limited to 'src/mesa/state_tracker/st_cb_flush.c')
0 files changed, 0 insertions, 0 deletions