Re: D correctly simulated by H proved for THREE YEARS --- rewritten

On 6/15/24 8:12 AM, olcott wrote:

On 6/15/2024 4:03 AM, Fred. Zwarts wrote:

Op 14.jun.2024 om 22:46 schreef olcott:

On 6/14/2024 3:03 PM, Fred. Zwarts wrote:

Op 14.jun.2024 om 21:18 schreef olcott:

On 6/14/2024 2:00 PM, Fred. Zwarts wrote:

Op 14.jun.2024 om 14:49 schreef olcott:

I ran the actual code to verify the facts.
HH1(DD,DD) does not have a pathological relationship to its input
thus this input terminates normally.

>
Your terminology is confusing. What you call a "pathological relationship" is that H must simulate itself.
>

>
*CONVENTIONAL TERMINOLOGY*
For any program H that might determine whether programs halt, a
"pathological" program D, called with some input, can pass its own
source and its input to H and then specifically do the opposite of what
H predicts D will do. No H can exist that handles this case.
https://en.wikipedia.org/wiki/Halting_problem

>
The problem is that your simulator does not even reach the "pathological" part of D.

>
That is not the problem that is the criterion measure of a solution.

>
You are using the wrong criterion, because this wrong criterion also also applies to other programs, without a "pathological" part.
>
        int main()
        {
          return H(main, 0);
        }
>
where you proved that H reports a false negative.
>
So, your criterion has no relation with "pathological" programs.
>

 This criteria works correctly for ALL input, including pathological
main(). Maybe if you were a PhD computer science professor you would
understand this.
 <MIT Professor Sipser agreed to ONLY these verbatim words 10/13/2022>
   If simulating halt decider H correctly simulates its input D
   until H correctly determines that its simulated D would never
   stop running unless aborted then
    H can abort its simulation of D and correctly report that D
   specifies a non-halting sequence of configurations.
</MIT Professor Sipser agreed to ONLY these verbatim words10/13/2022>
 

But since Professor Sipser mens by "A correct simulaiton: a simulation that actually reflects the behavior of the direct execution of the input, which means a simulation that NEVER aborts its operation until it reaches a final state, and H doesn't show that, or correctly that that sort of simulation of *THIS* input wouldn't halt (since D(D) Halts since H(D,D) returns 0) H can't use the first paragraph (whose conditions are not satisfied) to do the operations of the second, which it does anyway, and thus makes itself wrong.
And shows you to be an ignorant liar.

 

>
_D()
[00000cfc](01) 55          push ebp
[00000cfd](02) 8bec        mov ebp,esp
[00000cff](03) 8b4508      mov eax,[ebp+08]
[00000d02](01) 50          push eax       ; push D
[00000d03](03) 8b4d08      mov ecx,[ebp+08]
[00000d06](01) 51          push ecx       ; push D
[00000d07](05) e800feffff  call 00000b0c  ; call H
[00000d0c](03) 83c408      add esp,+08
[00000d0f](02) 85c0        test eax,eax
[00000d11](02) 7404        jz 00000d17
[00000d13](02) 33c0        xor eax,eax
[00000d15](02) eb05        jmp 00000d1c
[00000d17](05) b801000000  mov eax,00000001
[00000d1c](01) 5d          pop ebp
[00000d1d](01) c3          ret
Size in bytes:(0034) [00000d1d]

>
Nice try, but completely beside the point.
Are you really unable to see this has no relation with a "pathological" program that contradicts the result of H?
>
The only thing you have done so far is proving that no H exists that correctly simulates itself up to its final state and therefore it is unable to see the full behaviour of its input, because it always prematurely aborts the simulation one cycle too early.
>
If you don't understand such simple facts, discussion makes no sense.