commit 41b49893536a367313867d95afedf9260078c441
author Pau Cabre <pau.cabre@metempsy.com> Sat Nov 10 00:12:30 2018 +0100
committer Pau Cabre <pau.cabre@metempsy.com> Sat Nov 17 16:59:31 2018 +0000
tree 3f36deb042c14aff589caeca3af1a390c582b51c
parent 439b68a21e5122df2e6d1b9aad7ac46af619cc75

cpu: Fix LTAGE max number of allocations on update

The LTAGE paper states that only one TAGE entry can be
allocated when updating

Change-Id: I6cfb4d80ce835e93d4bf5099ef88a7d425abaddd
Signed-off-by: Pau Cabre <pau.cabre@metempsy.com>
Reviewed-on: https://gem5-review.googlesource.com/c/14195
Reviewed-by: Andreas Sandberg <andreas.sandberg@arm.com>
Reviewed-by: Ilias Vougioukas <ilias.vougioukas@arm.com>
Maintainer: Andreas Sandberg <andreas.sandberg@arm.com>

src/cpu/pred/ltage.cc

diff --git a/src/cpu/pred/ltage.cc b/src/cpu/pred/ltage.cc
index 874fbe4..8d20d50 100644
--- a/src/cpu/pred/ltage.cc
+++ b/src/cpu/pred/ltage.cc
@@ -579,6 +579,7 @@
                     gtable[i][bi->tableIndices[i]].tag = bi->tableTags[i];
                     gtable[i][bi->tableIndices[i]].ctr = (taken) ? 0 : -1;
                     gtable[i][bi->tableIndices[i]].u = 0; //?
+                    break;
                 }
             }
         }