Liste des Groupes | Revenir à c theory |
On 6/4/2025 10:55 PM, Mike Terry wrote:Hierarchies can be compared side-by-side. In the case of these traces, the hierarchy can be "flattened" into one stream of nested simulations. You do this yourself every time you present one of your nested simulation traces. Such a trace should include a simulation depth (or equivalent) for each entry.On 05/06/2025 02:39, olcott wrote:It can include nested simulations yet nestedOn 6/4/2025 8:28 PM, dbush wrote:>On 6/4/2025 9:08 PM, olcott wrote:>On 6/4/2025 7:41 PM, dbush wrote:On 6/4/2025 8:32 PM, olcott wrote:>>
Show me this side-by-side trace and I will point out your mistake.
See below, which shows that the simulations performed by HHH and HHH1 are identical up to the point that HHH aborts, as you have agreed on the record.
>>>
False. The correct trace is the one I posted, which shows all levels of emulation performed by HHH and HHH1. See the corrections I made to your comments
It is not supposed to do that.
Are you saying it's not supposed to include /nested/ emulations? It is perfectly sensible to include nested emulations.
>
simulations are in a hierarchy thus not side-by-side.
A side-by-side analysis must be side-by-side.
So you were doing it wrong. No problem, but now you (hopefully) understand you can do it right.No, that is not the way I was doing it.>>
It is supposed to show
the emulation of DDD by HHH1 and
the emulation of DDD by HHH
side-by-side to show the point where these
emulations diverge.
Just to be perfectly clear:
>
It is supposed to show
the emulation of DDD by *OUTER* HHH1 and
the emulation of DDD by *OUTER* HHH
side-by-side to show the point where these
emulations diverge.
>
I wasI.e. You were doing it wrong.
doing it all in the execution trace of HHH1(DDD).
Les messages affichés proviennent d'usenet.