Re: How Partial Simulations correctly determine non-halting ---Ben's 10/2022 analysis

On 6/7/24 11:40 AM, olcott wrote:

On 6/7/2024 10:32 AM, joes wrote:

Am Fri, 07 Jun 2024 10:20:09 -0500 schrieb olcott:

On 6/7/2024 10:09 AM, Python wrote:

Le 07/06/2024 à 17:05, olcott a écrit :

On 6/7/2024 9:55 AM, Python wrote:

Le 07/06/2024 à 16:47, olcott a écrit :

Anyway, you're wrong : a Turing machine can take its own description as
part of its input, as it is finite.

That is what I said. They cannot however take actual Turing machines as
inputs it must always be a finite string machine description.

Of course. That is not a restriction.
>

The issue here is that I proved that DD correctly simulated by HH
has different behavior than the directly executed DD(DD) and
everyone's "rebuttal" to this proof is to simply ignore it.

When you actually try to form a rebuttal of the above you will see
that I am correct. So far everyone simply ignores the proof that I am
correct as their only rebuttal.

A {correct simulation} means that each instruction of the above x86
machine language of DD is correctly simulated by HH and simulated in the
correct order.

And to the end. Thus it can't behave differently than direct execution.
>

 void Infinite_Recursion(u32 N)
{
   Infinite_Recursion(N);
}
 You must not be very good at programming if you believe
that Infinite_Recursion must be simulated "to the end"

And you must not be very good at all at programming (or logic) if you believe that shows anything about your case.
We can PROVE from a partial simulation of Infinite_Recursion that a complete simulation would never end. We can't do that for D.

 

Anyone claiming that HH should report on the behavior of the directly
executed DD(DD) is requiring a violation of the above definition of
correct simulation.

But those are the same. How does simulating something change it?
>

 It seems to boil down to you just don't know enough about
programming otherwise it would occur to you that there
cannot possibly exist any correct rebuttal to the following:
 Try to show how this DD correctly simulated by any HH ever
stops running without having its simulation aborted by HH.

Which is the wrong question, as has been pointed out to you for years.
But you have been caught in the briar patch by your own strawman, and thus fallen off the path you were tring to get to.

 _DD()
[00001e12] 55         push ebp
[00001e13] 8bec       mov  ebp,esp
[00001e15] 51         push ecx
[00001e16] 8b4508     mov  eax,[ebp+08]
[00001e19] 50         push eax      ; push DD
[00001e1a] 8b4d08     mov  ecx,[ebp+08]
[00001e1d] 51         push ecx      ; push DD
[00001e1e] e85ff5ffff call 00001382 ; call HH
 A {correct simulation} means that each instruction of the
above x86 machine language of DD is correctly simulated
by HH and simulated in the correct order.
 Anyone claiming that HH should report on the behavior
of the directly executed DD(DD) is requiring a violation
of the above definition of correct simulation.
 

And thus, you have proved that you are not talking about halting. as halting *IS* about the directly execute DD(DD), so if your definition of "correct simulation" can't map to it, it isn't applicable for the problem.
You are just admitting to trying to feed the world your POOP as a substitue for Halting, but the world doesn't what your POOP, it generally needs to know about actual Halting.