Re: DDD correctly emulated by H0 -- Ben agrees that Sipser approved criteria is met

On 6/26/2024 6:02 AM, Richard Damon wrote:

On 6/25/24 11:42 PM, olcott wrote:

>
That is not the way that it actually works.
That the the way that lies are defined.

 Source for you claim?
 Where is you finite set of steps from the truthmakers of the system to that claim?
 

_DDD()
[00002172] 55               push ebp      ; housekeeping
[00002173] 8bec             mov ebp,esp   ; housekeeping
[00002175] 6872210000       push 00002172 ; push DDD
[0000217a] e853f4ffff       call 000015d2 ; call H0(DDD)
[0000217f] 83c404           add esp,+04
[00002182] 5d               pop ebp
[00002183] c3               ret
Size in bytes:(0018) [00002183]
The call from DDD to H0(DDD) when DDD is correctly emulated
by H0 cannot possibly return.
When DDD is correctly emulated by an 86 emulator at
machine address 00002175 this is the sequence defined
by the semantics of the x86 language:
*REPEAT UNTIL OUT-OF-MEMORY ERROR*
[00002172] 55               push ebp      ; housekeeping
[00002173] 8bec             mov ebp,esp   ; housekeeping
[00002175] 6872210000       push 00002172 ; push DDD
[0000217a] e853f4ffff       call 000015d2 ; call H0(DDD)
The finite string input to H0 DOES SPECIFY THAT THE CALL
FROM DDD TO H0(DDD) CANNOT POSSIBLY RETURN IN EVERY SINGLE
CASE WHERE DDD IS CORRECTLY EMULATED BY THE DIRECTLY EXECUTED
H0 AND THIS H0 IS A PURE FUNCTION OF ITS INPUTS.
--
Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer