Don't assume c++11 std::map::erase in invalidateRange.

We were using the c++11 iterator return value from std::map::erase. Instead use the post-increment operator to keep a valid iterator after the call to erase, even on older stl. BUG=angle:773 Change-Id: Ieaa21a2b5a3fcd5ca229a31d40bdf9b8f3283a3c Reviewed-on: https://chromium-review.googlesource.com/238440Tested-by: Jamie Madill <jmadill@chromium.org> Reviewed-by: Geoff Lang <geofflang@chromium.org>

Don't assume c++11 std::map::erase in invalidateRange.
2bd2a42d · Jamie Madill · 22bcf7cf · 2bd2a42d
Commit 2bd2a42d authored Jan 05, 2015 by Jamie Madill
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

IndexRangeCache.cpp src/libANGLE/renderer/IndexRangeCache.cpp +1 -1

No files found.
--- a/src/libANGLE/renderer/IndexRangeCache.cpp
+++ b/src/libANGLE/renderer/IndexRangeCache.cpp
@@ -71,7 +71,7 @@ void IndexRangeCache::invalidateRange(unsigned int offset, unsigned int size)
        }
        else
        {
-            i = mIndexRangeCache.erase(i);
+            mIndexRangeCache.erase(i++);
        }
    }
 }