projects / gem5.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 439b68a) | patch
cpu: Fix LTAGE max number of allocations on update
authorPau Cabre <pau.cabre@metempsy.com>
Fri, 9 Nov 2018 23:12:30 +0000 (00:12 +0100)
committerPau Cabre <pau.cabre@metempsy.com>
Sat, 17 Nov 2018 16:59:31 +0000 (16:59 +0000)
commit41b49893536a367313867d95afedf9260078c441
tree3f36deb042c14aff589caeca3af1a390c582b51ctree
parent439b68a21e5122df2e6d1b9aad7ac46af619cc75commit | diff
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 | blob | history