From 0eef1069cbef303db5614a41a27c503cbaa55a85 Mon Sep 17 00:00:00 2001 From: Matt Sinclair Date: Tue, 27 Apr 2021 16:04:41 -0500 Subject: [PATCH] ruby: fix typo in VIPER TCC triggerQueue The GPU VIPER TCC protocol accidentally used "TiggerMsg" instead of "TriggerMsg" for the triggerQueue_in port. This was a benign bug beacuse the msg type is not used in the in_port implementation but still makes the SLICC harder to understand, so fixing it is worthwhile. Change-Id: I88cbc72bac93bcc58a66f057a32f7bddf821cac9 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/44905 Reviewed-by: Jason Lowe-Power Reviewed-by: Matthew Poremba Maintainer: Jason Lowe-Power Tested-by: kokoro --- src/mem/ruby/protocol/GPU_VIPER-TCC.sm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/mem/ruby/protocol/GPU_VIPER-TCC.sm b/src/mem/ruby/protocol/GPU_VIPER-TCC.sm index e21ba99fbe..6c07416a2d 100644 --- a/src/mem/ruby/protocol/GPU_VIPER-TCC.sm +++ b/src/mem/ruby/protocol/GPU_VIPER-TCC.sm @@ -252,7 +252,7 @@ machine(MachineType:TCC, "TCC Cache") // ** IN_PORTS ** - in_port(triggerQueue_in, TiggerMsg, triggerQueue) { + in_port(triggerQueue_in, TriggerMsg, triggerQueue) { if (triggerQueue_in.isReady(clockEdge())) { peek(triggerQueue_in, TriggerMsg) { TBE tbe := TBEs.lookup(in_msg.addr);