From 7c6454e5c1ccdcc64fc56d1fd707ed04e09e9677 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ciro=20Santilli=20=E5=85=AD=E5=9B=9B=E4=BA=8B=E4=BB=B6=20?= =?UTF-8?q?=E6=B3=95=E8=BD=AE=E5=8A=9F?= Date: Thu, 19 Dec 2019 00:00:00 +0000 Subject: [PATCH] readme: fix some c++ -> that expands to crazy char --- README.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.adoc b/README.adoc index 9b6eed0..18ae2e6 100644 --- a/README.adoc +++ b/README.adoc @@ -13043,15 +13043,15 @@ if (curStaticInst && curStaticInst->isMemRef()) { Fault fault = curStaticInst->execute(&t_info, traceData); .... -* `curStaticInst->isMemRef()` is true, and there is no instruction `execute` call in that part of the branch, only for instructions that don't touch memory +* `+curStaticInst->isMemRef()+` is true, and there is no instruction `execute` call in that part of the branch, only for instructions that don't touch memory * `_status` is `BaseSimpleCPU::Status::DcacheWaitResponse` and `advanceInst` is not yet called So, where is the `execute` happening? Well, I'll satisfy myself with a quick source grep and guess: -* `curStaticInst->initiateAcc` sets up some memory request events +* `+curStaticInst->initiateAcc+` sets up some memory request events * which likely lead up to: `TimingSimpleCPU::completeDataAccess`, which off the bat ends in `advanceInst`. + -It also calls `curStaticInst->completeAcc`, which pairs up with the `initiateAcc` call. +It also calls `+curStaticInst->completeAcc+`, which pairs up with the `initiateAcc` call. ===== gem5 event queue TimingSimpleCPU syscall emulation freestanding example analysis with caches