From 3dc7e4f496ad3ddab3010f8e7fdfce683ffdbdfb Mon Sep 17 00:00:00 2001 From: Erik Tomusk Date: Thu, 6 Dec 2012 09:31:06 -0600 Subject: TournamentBP: Fix some bugs with table sizes and counters globalHistoryBits, globalPredictorSize, and choicePredictorSize are decoupled. globalHistoryBits controls how much history is kept, global and choice predictor sizes control how much of that history is used when accessing predictor tables. This way, global and choice predictors can actually be different sizes, and it is no longer possible to walk off the predictor arrays and cause a seg fault. There are now individual thresholds for choice, global, and local saturating counters, so that taken/not taken decisions are correct even when the predictors' counters' sizes are different. The interface for localPredictorSize has been removed from TournamentBP because the value can be calculated from localHistoryBits. Committed by: Nilay Vaish --- configs/common/O3_ARM_v7a.py | 1 - 1 file changed, 1 deletion(-) (limited to 'configs') diff --git a/configs/common/O3_ARM_v7a.py b/configs/common/O3_ARM_v7a.py index c971df7fb..2c640badb 100644 --- a/configs/common/O3_ARM_v7a.py +++ b/configs/common/O3_ARM_v7a.py @@ -90,7 +90,6 @@ class O3_ARM_v7a_FUP(FUPool): class O3_ARM_v7a_3(DerivO3CPU): predType = "tournament" - localPredictorSize = 64 localCtrBits = 2 localHistoryTableSize = 64 localHistoryBits = 6 -- cgit v1.2.3