Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: olcott <polcott333@gmail.com>
Newsgroups: comp.theory
Subject: Re: Overcoming the proof of undecidability of the Halting Problem by
 a simple example in C
Date: Thu, 15 May 2025 18:25:36 -0500
Organization: A noiseless patient Spider
Lines: 80
Message-ID: <1005t5g$3chps$1@dont-email.me>
References: <1005jsk$3akrk$1@dont-email.me>
 <FAsVP.790302$BFJ.344089@fx13.ams4> <1005la7$3akrk$3@dont-email.me>
 <tSsVP.790303$BFJ.255821@fx13.ams4> <1005mms$3akrk$4@dont-email.me>
 <rBtVP.134541$0ia.111399@fx11.ams4>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 16 May 2025 01:25:37 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="a793c50ac46b1404361ae4f1062ef558";
	logging-data="3557180"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19rkrhgGzcQgYi3Qf744oR4"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:bHoyTrxKokkQRCEXm22AVZk84eM=
Content-Language: en-US
X-Antivirus: Norton (VPS 250515-4, 5/15/2025), Outbound message
In-Reply-To: <rBtVP.134541$0ia.111399@fx11.ams4>
X-Antivirus-Status: Clean

On 5/15/2025 5:08 PM, Mr Flibble wrote:
> On Thu, 15 May 2025 16:35:24 -0500, olcott wrote:
> 
>> On 5/15/2025 4:18 PM, Mr Flibble wrote:
>>> On Thu, 15 May 2025 16:11:35 -0500, olcott wrote:
>>>
>>>> On 5/15/2025 3:59 PM, Mr Flibble wrote:
>>>>> On Thu, 15 May 2025 15:47:16 -0500, olcott wrote:
>>>>>
>>>>>> I overcome the proof of undecidability of the Halting Problem in
>>>>>> that the code that "does the opposite of whatever value that HHH
>>>>>> returns" becomes unreachable to DD correctly simulated by HHH.
>>>>>>
>>>>>> int DD()
>>>>>>      {
>>>>>>       int Halt_Status = HHH(DD);
>>>>>>       if (Halt_Status)
>>>>>>         HERE: goto HERE;
>>>>>>       return Halt_Status;
>>>>>>      }
>>>>>>
>>>>>> HHH simulates DD that calls HHH(DD) to simulate itself again over
>>>>>> and over until HHH sees this repeating pattern and aborts or both
>>>>>> HHH and DD crash due to OOM error.
>>>>>     
>>>>> It is not possible for HHH to simulate DD because we are already
>>>>> inside DD when we call HHH:
>>>>
>>>> Since HHH does correctly simulate itself simulating DD we have
>>>> complete proof that you are wrong.
>>>>
>>>> I had to write the whole x86utm operating system to make this work.
>>>
>>> It is not possible to make this work even by "writing an operating
>>> system"
>>> so whatever you think you are doing it isn't addressing my core point:
>>> you are NOT *fully* simulating DD by HHH because you are already inside
>>> DD when you are calling HHH.
>>>
>>> /Flibble
>>
>> Anyone that is intimately familiar with how multi-tasking operating
>> systems work will understand how HHH could emulate itself emulating its
>> input.
> 
> What has multi-tasking got to do with it?  You are talking out of your
> arse, Peter. :)
> 

Anyone that is intimately familiar with multi-tasking
operating systems will know the details of how HHH
emulates itself emulating DDD.

Whenever any HHH is about to begin emulating an input
it requests a separate process context with its own
virtual registers and stack from the x86utm operating
system. Then HHH calls the x86utm operating system
to execute

u32  DebugStep(Registers* master_state,
                Registers* slave_state, Decoded_Line_Of_Code* decoded)

each instruction one-at-a-time as cooperative multi-tasking.

>>
>> Mike already verified that HHH does correctly emulate itself emulating
>> DDD. He verified this by carefully studying the source-code.
> 
> The source code is the C code you posted in this thread, and it has the
> problem I described.
> 
> /Flibble

https://github.com/plolcott/x86utm/blob/master/Halt7.c
Mike verified that the HHH in the above file
does correctly emulate itself emulating DDD.

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