Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: Richard Damon <richard@damon-family.org>
Newsgroups: comp.theory,sci.logic
Subject: Re: Can D simulated by H terminate normally?
Date: Sat, 27 Apr 2024 21:39:36 -0400
Organization: i2pn2 (i2pn.org)
Message-ID: <v0k9co$2djoe$11@i2pn2.org>
References: <v0k4jc$laej$1@dont-email.me> <v0k6eo$2djoe$10@i2pn2.org>
 <v0k70f$lpet$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 28 Apr 2024 01:39:36 -0000 (UTC)
Injection-Info: i2pn2.org;
	logging-data="2543374"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="diqKR1lalukngNWEqoq9/uFtbkm5U+w3w6FQ0yesrXg";
User-Agent: Mozilla Thunderbird
Content-Language: en-US
X-Spam-Checker-Version: SpamAssassin 4.0.0
In-Reply-To: <v0k70f$lpet$1@dont-email.me>
Bytes: 3978
Lines: 82

On 4/27/24 8:58 PM, olcott wrote:
> On 4/27/2024 7:49 PM, Richard Damon wrote:
>> On 4/27/24 8:17 PM, olcott wrote:
>>> Can D simulated by H terminate normally?
>>>
>>> The x86utm operating system based on an open source x86 emulator.
>>> This system enables one C function to execute another C function
>>> in debug step mode. When H simulates D it creates a separate process
>>> context for D with its own memory, stack and virtual registers. H
>>> is able to simulate D simulating itself, thus the only limit to
>>> recursive simulations is RAM.
>>>
>>> // The following is written in C
>>> //
>>> 01 typedef int (*ptr)(); // pointer to int function
>>> 02 int H(ptr x, ptr y)    // uses x86 emulator to simulate its input
>>> 03
>>> 04 int D(ptr x)
>>> 05 {
>>> 06   int Halt_Status = H(x, x);
>>> 07   if (Halt_Status)
>>> 08     HERE: goto HERE;
>>> 09   return Halt_Status;
>>> 10 }
>>> 11
>>> 12 void main()
>>> 13 {
>>> 14   D(D);
>>> 15 }
>>>
>>> Execution Trace
>>> Line 14: main() invokes D(D)
>>>
>>> keeps repeating (unless aborted)
>>> Line 06: simulated D(D) invokes simulated H(D,D) that simulates D(D)
>>>
>>> Simulation invariant
>>> D correctly simulated by H cannot possibly reach its own line 09.
>>>
>>> Is it dead obvious to everyone here when examining the execution
>>> trace of lines 14 and 06 above that D correctly simulated by H cannot
>>> possibly terminate normally by reaching its own line 09?
>>>
>>>
>>
>> Except that you fail to mention that you have admitted that you are 
>> NOT working on the Halting Problem, despite trying to use terminology 
>> similar to it, but having stipulated definition that are in conflict 
>> with computaiton theory.
>>
>> Note, "keeps repeating (unless aborted)" is a misleading statement, as 
>> your H will ALWAYS abort this input, and thus it NEVER will "Keep 
>> repeating".
>>
>> You don't like me pointing out the problem because you prefer to be 
>> able to LIE to people about what you are doing.
>>
>> You work has NOTHING to do with Halting, as your H/D are not even 
>> turing equivalenet to their namesakes in the proof you like to mention.
> 
> That is the exact verbatim post and the first respondent agreed
> and immediately noticed that I was referring to the halting problem.
> 
> So I will go with what I said, you just don't know C very
> well and want to keep that hidden behind rhetoric and denigration.
> 
> 


Yes, you couch it to SOUND like the halting problem, but it isn't as you 
have FUNDAMENTALLY CHANGED the meaning of terms.

And thus, to act like it is, just makes you a LIAR.

Halting is NOT about H being able to simulate it input to the final 
state. PERIOD.

You are just showing that you are NOT out to promote truth, but to try 
to infiltrate logic with your ERRORS and LIES to allow you to claim 
things that are just not true, just like those you try to put down, like 
the election denyers.

You are WORSE than them.