Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: olcott <polcott333@gmail.com>
Newsgroups: comp.theory
Subject: Re: Defining a correct simulating halt decider
Date: Mon, 2 Sep 2024 16:06:24 -0500
Organization: A noiseless patient Spider
Lines: 54
Message-ID: <vb59cg$3057o$1@dont-email.me>
References: <vb4plc$2tqeg$1@dont-email.me> <vb4u1g$2u7sn$4@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 02 Sep 2024 23:06:25 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="a2fe8748f6382997edaeece42547d6b5";
	logging-data="3151096"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/i5+7NN8anisyFltxFB57t"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:pmQVt6q30Yy21cZsWR3urm2EcZc=
In-Reply-To: <vb4u1g$2u7sn$4@dont-email.me>
Content-Language: en-US
Bytes: 3094

On 9/2/2024 12:52 PM, Fred. Zwarts wrote:
> Op 02.sep.2024 om 18:38 schreef olcott:
>> A halt decider is a Turing machine that computes
>> the mapping from its finite string input to the
>> behavior that this finite string specifies.
>>
>> If the finite string machine string machine
>> description specifies that it cannot possibly
>> reach its own final halt state then this machine
>> description specifies non-halting behavior.
>>
>> A halt decider never ever computes the mapping
>> for the computation that itself is contained within.
>>
>> Unless there is a pathological relationship between
>> the halt decider H and its input D the direct execution
>> of this input D will always have identical behavior to
>> D correctly simulated by simulating halt decider H.
>>
>> *Simulating Termination Analyzer H Not Fooled by Pathological Input D*
>> https://www.researchgate.net/ 
>> publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D
>>
>> A correct emulation of DDD by HHH only requires that HHH
>> emulate the instructions of DDD** including when DDD calls
>> HHH in recursive emulation such that HHH emulates itself
>> emulating DDD.
> 
> Indeed, it should simulate *itself* and not a hypothetical other HHH 
> with different behaviour.

It is emulating the exact same freaking machine code
that the x86utm operating system is emulating.

> If HHH includes code to see a 'special condition' and aborts and halts, 
> then it should also simulate the HHH that includes this same code and 


DDD has itself and the emulated HHH stuck in recursive emulation.

IS THE CONCEPT OF UNREACHABLE CODE OVER YOUR HEAD?
IS THE CONCEPT OF UNREACHABLE CODE OVER YOUR HEAD?
IS THE CONCEPT OF UNREACHABLE CODE OVER YOUR HEAD?

void Infinite_Recursion()
{
   Infinite_Recursion();
   printf("Fred is too dumb to know this code is never reached!\n");
}


-- 
Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer