Tobias Tebbi b76c27bfe9 [torque] fix bug in Stack::DeleteRange ... This bug does not affect the Torque run on tip-of-tree, but surfaced in https://crrev.com/c/1196693. The logic in Stack::DeleteRange was completely wrong and does not work if the number of moved elements is bigger than the number of deleted elements. Change-Id: I5433b3b06e2e54646104493e9bc5e77b9763a521 Reviewed-on: https://chromium-review.googlesource.com/c/1282103 Reviewed-by: Michael Stanton <mvstanton@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#56676}		2018-10-16 09:24:45 +00:00
..
earley-parser-unittest.cc
torque-unittest.cc	[torque] fix bug in Stack::DeleteRange	2018-10-16 09:24:45 +00:00