diff options
author | Brian Paul <[email protected]> | 2010-01-26 10:53:34 -0700 |
---|---|---|
committer | Brian Paul <[email protected]> | 2010-01-26 10:53:40 -0700 |
commit | af1e9403e732651fe2cedde230ac7010f2f1a649 (patch) | |
tree | a3a3f50e7b82fa40bd1bed8fda8cda438ed1245f /src/mesa/main/state.c | |
parent | 1d8b308cbf6e17f2703807152deaa1ee075882e2 (diff) |
mesa: remove redundant _MaxElement computation
Eric added some new code to check if offset < obj_size before computing
_MaxElement but my original code was still present afterward and it
clobbered the _MaxElement value.
Not sure if this came from a bad merge or what.
Diffstat (limited to 'src/mesa/main/state.c')
-rw-r--r-- | src/mesa/main/state.c | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/src/mesa/main/state.c b/src/mesa/main/state.c index 904ad012052..5e07d1d2f15 100644 --- a/src/mesa/main/state.c +++ b/src/mesa/main/state.c @@ -82,12 +82,6 @@ compute_max_element(struct gl_client_array *array) } else { array->_MaxElement = 0; } - /* Compute the max element we can access in the VBO without going - * out of bounds. - */ - array->_MaxElement = ((GLsizeiptrARB) array->BufferObj->Size - - (GLsizeiptrARB) array->Ptr + array->StrideB - - array->_ElementSize) / array->StrideB; } else { /* user-space array, no idea how big it is */ |