mesa/st: accept NULL and empty buffer objects
authorErik Faye-Lund <erik.faye-lund@collabora.com>
Wed, 6 Mar 2019 11:18:28 +0000 (12:18 +0100)
committerErik Faye-Lund <erik.faye-lund@collabora.com>
Mon, 29 Apr 2019 10:28:38 +0000 (10:28 +0000)
commitbe110ba2e4d5f8e5c71294d29dc991f4b6600e79
tree34cc4fa27f30fa6a0750585ce6ac95994d03f3e6
parentef13691e0c07d909a4f14280ca4fefbd79a9865b
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 <erik.faye-lund@collabora.com>
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
src/mesa/state_tracker/st_atom_array.c