From 41b49893536a367313867d95afedf9260078c441 Mon Sep 17 00:00:00 2001
From: Pau Cabre <pau.cabre@metempsy.com>
Date: Sat, 10 Nov 2018 00:12:30 +0100
Subject: 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 | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/cpu/pred/ltage.cc b/src/cpu/pred/ltage.cc
index 874fbe41e..8d20d5056 100644
--- a/src/cpu/pred/ltage.cc
+++ b/src/cpu/pred/ltage.cc
@@ -579,6 +579,7 @@ LTAGE::update(ThreadID tid, Addr branch_pc, bool taken, void* bp_history,
                     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;
                 }
             }
         }
-- 
cgit v1.2.3