Sujet : Re: 197 page execution trace of DDD correctly simulated by HHH
De : F.Zwarts (at) *nospam* HetNet.nl (Fred. Zwarts)
Groupes : comp.theoryDate : 01. Jul 2024, 15:27:14
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v5uec2$12qkb$2@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
User-Agent : Mozilla Thunderbird
Op 01.jul.2024 om 14:57 schreef olcott:
On 7/1/2024 3:27 AM, Fred. Zwarts wrote:
Op 30.jun.2024 om 19:25 schreef olcott:
On 6/30/2024 3:42 AM, joes wrote:
>
No, I mean: why does the inner simulator repeat instead of aborting,
the same as the outer one does?
>
Technically it is called detecting a repeating state.
Yeah, I know. My point is: all recursive calls both enter and detect
a repeating state.
>
>
The inner ones always see one less execution trace
than the next outer one, thus could only meet their
abort criteria after they have already been aborted.
>
>
Which indicates that they were aborted too soon, showing that the emulation was incorrect.
Unless the outer HHH aborts its simulation after some
fixed number of correct emulations or none of the HHH
ever aborts and HHH never stops running.
But that does not make the result of the abort correct.
Not aborting will loop infinitely. Aborting will abort too soon. Both cases are incorrect.
There is no passing the guy in front of you if you both
continue to run at the exact same speed, he will always
be ahead of you.
But shooting his tyres is also incorrect.