From Newsgroup: comp.ai.philosophy
On 8/5/2025 2:14 AM, Mikko wrote:
On 2025-08-04 21:55:28 +0000, olcott said:
Simulating Termination Analyzer HHH correctly simulates its input until:
(a) Detects a non-terminating behavior pattern: abort simulation and
return 0.
(b) Simulated input reaches its simulated "return" statement: return 1.
int DD()
{
int Halt_Status = HHH(DD);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
Can you see that DD correctly simulated by HHH demonstrates the
recursive simulation non halting behavior pattern that cannot possibly
reach its own "if" statement?
No, we can't hallucinate that. HHH does not demostrate. It simply reports incorrectly.
*This process is known as cooperative multi-tasking*
The master process saves its own state and loads
the state of its slave from its slave's process context.
Then it emulates one x86 instruction of its slave,
saves the updated slave state and restores its own state.
// *x86utm operating system function call stubs*
void SaveState(Registers* state) {}
void LoadState(Registers* state) {}
u32 DebugStep(Registers* master_state,
Registers* slave_state,
Decoded_Line_Of_Code* decoded) { return 0; }
HHH(DD) is executed and creates a separate process
context for DD then simulates DD in this process context.
This simulated DD calls another instance of HHH(DD)
in its own process context.
This instance of HHH creates another separate process
context for its own instance of DD then simulates DD.
This simulated DD calls HHH(DD) again.
--
Copyright 2025 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer
--- Synchronet 3.21a-Linux NewsLink 1.2