From ae409b75bf72d2462020d33c20c84d970b3a6f10 Mon Sep 17 00:00:00 2001 From: Steve Gou Date: Thu, 9 Jun 2022 12:06:21 +0800 Subject: [PATCH] ftq: should use jmpOffset instead of cfiIndex when assigning (#1561) last_may_be_rvi_call in case that a call comes after a taken branch --- src/main/scala/xiangshan/frontend/NewFtq.scala | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/scala/xiangshan/frontend/NewFtq.scala b/src/main/scala/xiangshan/frontend/NewFtq.scala index e8d36b850..a92843722 100644 --- a/src/main/scala/xiangshan/frontend/NewFtq.scala +++ b/src/main/scala/xiangshan/frontend/NewFtq.scala @@ -308,7 +308,7 @@ class FTBEntryGen(implicit p: Parameters) extends XSModule with HasBackendRedire init_entry.isCall := new_jmp_is_call init_entry.isRet := new_jmp_is_ret // that means fall thru points to the middle of an inst - init_entry.last_may_be_rvi_call := io.cfiIndex.bits === (PredictWidth-1).U && !pd.rvcMask(pd.jmpOffset) + init_entry.last_may_be_rvi_call := pd.jmpOffset === (PredictWidth-1).U && !pd.rvcMask(pd.jmpOffset) // if hit, check whether a new cfi(only br is possible) is detected val oe = io.old_entry -- GitLab