From b44c4271e3f97f1d0a94b6e412e9880a2bfa821d Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Mon, 26 Jul 2021 15:38:57 +0100 Subject: [PATCH] whitespace --- docs/firststeps.mdwn | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/firststeps.mdwn b/docs/firststeps.mdwn index 50bf205f9..991dfc145 100644 --- a/docs/firststeps.mdwn +++ b/docs/firststeps.mdwn @@ -166,13 +166,16 @@ method called `run_tst_program`. This method, in turn, calls `run_tst`, and this is the place where the magic happens. In `process` nested function, we actually simulate that our instructions are executed one-by-one, literally calling `yield from simulator.execute_one()`. And this method inside the -simulator instance belongs to [`src/openpower/decoder/isa/caller.py`](https://git.libre-soc.org/?p=openpower-isa.git;a=blob;f=src/openpower/decoder/isa/caller.py;hb=HEAD) script. +simulator instance belongs to +[`src/openpower/decoder/isa/caller.py`](https://git.libre-soc.org/?p=openpower-isa.git;a=blob;f=src/openpower/decoder/isa/caller.py;hb=HEAD) +script. Inside `execute_one` method, the most crucial part is `yield from self.call(opname)` call; and, if we take a look inside of the `call` method, we will see that, aside of the aforementioned log (`log("call", ins_name, asmop)`), this function also takes care of the rest of the magic. This includes a lot of manipulations before and after executing instruction, but the crucial part is quite simple: + ``` # execute actual instruction here (finally) log("inputs", inputs) -- 2.30.2