Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

The only thing necessary for the triumph of evil is for good men to do nothing. -- Edmund Burke


devel / comp.theory / Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

SubjectAuthor
* Conquering the last rebuttal to H(P,P)==0 refutation of the haltingolcott
+* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
|`* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| +* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |`* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| | `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |  `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |   `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |    `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     +* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |+* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     ||+* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||`* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     ||| `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||  +* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||  |`* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||  | `- Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||  `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||   `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||    `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||     `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      +* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      |`* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | +* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | |`* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | +* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | |+- Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | |`* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | +* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | |`* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | +* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |`* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | | `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |  `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   +* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |`* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   | `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |  `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |   `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |    `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |     `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |      `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |       +* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |+- Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem prooBen Bacarisse
| |     |||      | | | | |   |       |+* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |       ||+- Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       ||`- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| |     |||      | | | | |   |       |`* Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem prooolcott
| |     |||      | | | | |   |       | `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |  `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |       |   +- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| |     |||      | | | | |   |       |   `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |    `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |       |     `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |      `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |       |       `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |        +* Conquering the last rebuttal to H(P,P)==0 refutation of theMr Flibble
| |     |||      | | | | |   |       |        |`- Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |       |        `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |       |         `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |          `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |       |           `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |            `* Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem prooolcott
| |     |||      | | | | |   |       |             `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |              `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |       |               `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |                `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |       |                 `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |                  `* Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem prooolcott
| |     |||      | | | | |   |       |                   `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |                    `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |       |                     +* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |                     |`* Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem prooolcott
| |     |||      | | | | |   |       |                     | +* Conquering the last rebuttal to H(P,P)==0 refutation of thePython
| |     |||      | | | | |   |       |                     | |`* Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem prooolcott
| |     |||      | | | | |   |       |                     | | `- Conquering the last rebuttal to H(P,P)==0 refutation of thePython
| |     |||      | | | | |   |       |                     | `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |                     |  `* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |       |                     |   +* Conquering the last rebuttal to H(P,P)==0 refutation of thePython
| |     |||      | | | | |   |       |                     |   |`- Conquering the last rebuttal to H(P,P)==0 refutation of theElvi Ikina
| |     |||      | | | | |   |       |                     |   `* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |                     |    `* Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem prooolcott
| |     |||      | | | | |   |       |                     |     +* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |                     |     |`* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | | |   |       |                     |     | +- Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | | |   |       |                     |     | `- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| |     |||      | | | | |   |       |                     |     `- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| |     |||      | | | | |   |       |                     `- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| |     |||      | | | | |   |       +- Conquering the last rebuttal to H(P,P)==0 refutation of theMr Flibble
| |     |||      | | | | |   |       `- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| |     |||      | | | | |   `- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| |     |||      | | | | `- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| |     |||      | | | +* Conquering the last rebuttal to H(P,P)==0 refutation of thewij
| |     |||      | | | |+* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | ||`* Conquering the last rebuttal to H(P,P)==0 refutation of thewij
| |     |||      | | | || +* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | || |+* Conquering the last rebuttal to H(P,P)==0 refutation of theMr Flibble
| |     |||      | | | || ||`- Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | || |`* Conquering the last rebuttal to H(P,P)==0 refutation of thePython
| |     |||      | | | || | +- Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     |||      | | | || | `- Conquering the last rebuttal to H(P,P)==0 refutation of theJd Akechi
| |     |||      | | | || `* Conquering the last rebuttal to H(P,P)==0 refutation of thedklei...@gmail.com
| |     |||      | | | |`* Conquering the last rebuttal to H(P,P)==0 refutation of theDennis Bush
| |     |||      | | | `- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| |     |||      | | `- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| |     |||      | `- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| |     |||      `- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| |     ||`- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| |     |`* Conquering the last rebuttal to H(P,P)==0 refutation of theolcott
| |     `- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
| `- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon
+* Conquering the last rebuttal to H(P,P)==0 refutation of the haltingolcott
+* Conquering the last rebuttal to H(P,P)==0 refutation of theMalcolm McLean
+- Conquering the last rebuttal to H(P,P)==0 refutation of thePete
`- Conquering the last rebuttal to H(P,P)==0 refutation of theRichard Damon

Pages:123456789
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<jsidnZdTjLdsZST_nZ2dnUU7_8zNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35023&group=comp.theory#35023

  copy link   Newsgroups: comp.theory sci.logic sci.math
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 27 Jun 2022 13:37:37 -0500
Date: Mon, 27 Jun 2022 13:37:36 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
Content-Language: en-US
Newsgroups: comp.theory,sci.logic,sci.math
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com>
<j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com>
<qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com>
<YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com>
<f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com>
<Sv-dnX5Vh499eyT_nZ2dnUU7_8zNnZ2d@giganews.com>
<fc96a583-3a51-45fd-8275-4bc8aaca8fc0n@googlegroups.com>
<Lfudna-pu95HbyT_nZ2dnUU7_83NnZ2d@giganews.com>
<8bca30ba-3f3f-4b76-b401-504b4873e55en@googlegroups.com>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <8bca30ba-3f3f-4b76-b401-504b4873e55en@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <jsidnZdTjLdsZST_nZ2dnUU7_8zNnZ2d@giganews.com>
Lines: 247
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-pnTSSZBg2o9QRcI8QM26SZcbEKyJfCKMfWejLizqNrtCGF1BJMMiO/6E35QG/UE/ZFA+86bwayTUKyi!pvtBZi+9N3+cXlwt4/l4uxWNZAeruZo4uA6SKH6mV/zXC2EGFsrv6eiJfvWrcVu852kFHkb2v0U2
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 14219
 by: olcott - Mon, 27 Jun 2022 18:37 UTC

On 6/27/2022 1:13 PM, Dennis Bush wrote:
> On Monday, June 27, 2022 at 2:11:45 PM UTC-4, olcott wrote:
>> On 6/27/2022 1:03 PM, Dennis Bush wrote:
>>> On Monday, June 27, 2022 at 1:20:39 PM UTC-4, olcott wrote:
>>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
>>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
>>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
>>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
>>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
>>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
>>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
>>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
>>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
>>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>> *This is the outline of the complete refutation*
>>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
>>>>>>>>>>>>>> never reaches the "ret" instruction of P.
>>>>>>>>>>>>>
>>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>>>>>>>>>>>
>>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>>>>>>>>>>>>>
>>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
>>>>>>>>>>>>>> the semantics of the x86 language.
>>>>>>>>>>>>>
>>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
>>>>>>>>>>>>>
>>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
>>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
>>>>>>>>>>>>>
>>>>>>>>>>>>> H does not perform this mapping.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
>>>>>>>>>>>>>
>>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> void P(u32 x)
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>> if (H(x, x))
>>>>>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>>>>>> return;
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>> P(P);
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _P()
>>>>>>>>>>>>>> [000011f0](01) 55 push ebp
>>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
>>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>> [000011f6](01) 50 push eax
>>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>> [000011fa](01) 51 push ecx
>>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
>>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
>>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
>>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
>>>>>>>>>>>>>> [00001209](01) 5d pop ebp
>>>>>>>>>>>>>> [0000120a](01) c3 ret
>>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _main()
>>>>>>>>>>>>>> [00001210](01) 55 push ebp
>>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
>>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
>>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
>>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
>>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
>>>>>>>>>>>>>> [00001222](01) 5d pop ebp
>>>>>>>>>>>>>> [00001223](01) c3 ret
>>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> machine stack stack machine assembly
>>>>>>>>>>>>>> address address data code language
>>>>>>>>>>>>>> ======== ======== ======== ========= =============
>>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
>>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
>>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
>>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
>>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
>>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
>>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
>>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
>>>>>>>>>>>>>> Address_of_H:1020
>>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
>>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
>>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
>>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
>>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
>>>>>>>>>>>>>> recursive emulation.
>>>>>>>>>>>>>
>>>>>>>>>>>>> FALSE. P contains these instructions:
>>>>>>>>>>>>>
>>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
>>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
>>>>>>>>>>>>> goto END_OF_CODE;
>>>>>>>>>>>>> return 0; // Does not halt
>>>>>>>>>>>>> END_OF_CODE:
>>>>>>>>>>>>> return 1; // Input has normally terminated
>>>>>>>>>>>>>
>>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
>>>>>>>>>>>>>
>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
>>>>>>>>>>>>>
>>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
>>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
>>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
>>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
>>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
>>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
>>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
>>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
>>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
>>>>>>>>>>>> input never reaches the the "ret" instruction of P.
>>>>>>>>>>>
>>>>>>>>>>> Repeating your original point.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
>>>>>>>>>>>>
>>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Again, repeating your original point.
>>>>>>>>>>>
>>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>> Therefore H(P,P)==0 is correct.
>>>>>>>>>>>
>>>>>>>>>>> And again, repeating your original point.
>>>>>>>>>>>
>>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
>>>>>>>>>>>
>>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
>>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
>>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
>>>>>>>>>> never reach the final state "ret" instruction of this input.
>>>>>>>>>
>>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>> First of all I am not talking about UTM's.
>>>>>>>> I am talking about x86 emulation.
>>>>>>>> Try to encode what you mean, here is my guess:
>>>>>>>>
>>>>>>>> void P(u32 x)
>>>>>>>> {
>>>>>>>> if (emulate_x86(x, x))
>>>>>>>> HERE: goto HERE;
>>>>>>>> return;
>>>>>>>> }
>>>>>>>>
>>>>>>>> int main()
>>>>>>>> {
>>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
>>>>>>>> }
>>>>>>>
>>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
>>>>>>>
>>>>>>> void UTM(u32 x, u32 y)
>>>>>>> {
>>>>>>> x(y)
>>>>>>> }
>>>>>>>
>>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
>>>>>>>
>>>>>> A simulating halt decider correctly simulates its input until it
>>>>>> correctly determines that this simulated input would never reach its
>>>>>> final state.
>>>>>
>>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
>>>>>
>>>> Every simulating decider that correctly simulates its input until it
>>>> correctly determines that this simulated input would never reach its
>>>> final state correctly determines the halt status of this input.
>>>
>>> And H isn't such a decider, because it does not correctly determine that the input to H(P,P) would never halt as demonstrated by UTM(P,P) halting.
>>>
>>> The specification for H:
>>>
>>> H(x,y)==0 if and only if x(y) does not halt, and
>>> H(x,y)==1 if and only if x(y) halts.
>>>
>>> H does not meet the specification.
>>>
>> The spec is provably incorrect in this case:
>
> A spec can't be incorrect. It just is. If it can't be satisfied, then that validates the halting problem proofs that say it can't be satisfied.


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<68ednUyP7tp6ZCT_nZ2dnUU7_8zNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35024&group=comp.theory#35024

  copy link   Newsgroups: comp.theory sci.logic sci.math
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 27 Jun 2022 13:41:43 -0500
Date: Mon, 27 Jun 2022 13:41:42 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
Content-Language: en-US
Newsgroups: comp.theory,sci.logic,sci.math
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com>
<j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com>
<qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com>
<YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com>
<f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com>
<q4CdnWm9zL2KbST_nZ2dnUU7_8zNnZ2d@giganews.com>
<9f0c8dcb-ae3a-47bf-9093-4e4d9377dc47n@googlegroups.com>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <9f0c8dcb-ae3a-47bf-9093-4e4d9377dc47n@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <68ednUyP7tp6ZCT_nZ2dnUU7_8zNnZ2d@giganews.com>
Lines: 251
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-z0kkfJt12JUU4HaRdh5DNzEt38mU14i80MDojoqgIFSm3YW2X3VTng7UjpWRYEZl/llPIIKdirHsk0g!nJyzTMcypqSN1QmL+TYFHJIfMjIJnB7VHyafh6x8GJRqb8kufU2rTi+3wIhlzFGfhb/NZUVzGOfz
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 14125
 by: olcott - Mon, 27 Jun 2022 18:41 UTC

On 6/27/2022 1:08 PM, Dennis Bush wrote:
> On Monday, June 27, 2022 at 1:59:58 PM UTC-4, olcott wrote:
>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
>>>>>>>>>>>> *This is the outline of the complete refutation*
>>>>>>>>>>>> *of the only rebuttal that anyone has left*
>>>>>>>>>>>>
>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
>>>>>>>>>>>> never reaches the "ret" instruction of P.
>>>>>>>>>>>
>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>>>>>>>>>
>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>>>>>>>>>>>
>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
>>>>>>>>>>>>
>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
>>>>>>>>>>>> the semantics of the x86 language.
>>>>>>>>>>>
>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>
>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
>>>>>>>>>>>
>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
>>>>>>>>>>>
>>>>>>>>>>> H does not perform this mapping.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
>>>>>>>>>>>
>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> void P(u32 x)
>>>>>>>>>>>> {
>>>>>>>>>>>> if (H(x, x))
>>>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>>>> return;
>>>>>>>>>>>> }
>>>>>>>>>>>>
>>>>>>>>>>>> int main()
>>>>>>>>>>>> {
>>>>>>>>>>>> P(P);
>>>>>>>>>>>> }
>>>>>>>>>>>>
>>>>>>>>>>>> _P()
>>>>>>>>>>>> [000011f0](01) 55 push ebp
>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>> [000011f6](01) 50 push eax
>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>> [000011fa](01) 51 push ecx
>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
>>>>>>>>>>>>
>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
>>>>>>>>>>>> [00001209](01) 5d pop ebp
>>>>>>>>>>>> [0000120a](01) c3 ret
>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
>>>>>>>>>>>>
>>>>>>>>>>>> _main()
>>>>>>>>>>>> [00001210](01) 55 push ebp
>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
>>>>>>>>>>>> [00001222](01) 5d pop ebp
>>>>>>>>>>>> [00001223](01) c3 ret
>>>>>>>>>>>> Size in bytes:(0020) [00001223]
>>>>>>>>>>>>
>>>>>>>>>>>> machine stack stack machine assembly
>>>>>>>>>>>> address address data code language
>>>>>>>>>>>> ======== ======== ======== ========= =============
>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
>>>>>>>>>>>>
>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
>>>>>>>>>>>> Address_of_H:1020
>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
>>>>>>>>>>>>
>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
>>>>>>>>>>>> recursive emulation.
>>>>>>>>>>>
>>>>>>>>>>> FALSE. P contains these instructions:
>>>>>>>>>>>
>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
>>>>>>>>>>> goto END_OF_CODE;
>>>>>>>>>>> return 0; // Does not halt
>>>>>>>>>>> END_OF_CODE:
>>>>>>>>>>> return 1; // Input has normally terminated
>>>>>>>>>>>
>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
>>>>>>>>>>>
>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
>>>>>>>>>>>
>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
>>>>>>>>>>>> executed P
>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
>>>>>>>>>>>> executed P
>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
>>>>>>>>>>>
>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
>>>>>>>>>> input never reaches the the "ret" instruction of P.
>>>>>>>>>
>>>>>>>>> Repeating your original point.
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> This is the actual behavior of the input to H(P,P).
>>>>>>>>>>
>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Again, repeating your original point.
>>>>>>>>>
>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>> specified by these inputs.
>>>>>>>>>> Therefore H(P,P)==0 is correct.
>>>>>>>>>
>>>>>>>>> And again, repeating your original point.
>>>>>>>>>
>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
>>>>>>>>>
>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
>>>>>>>> halt decider correctly predicts that its correctly simulated input will
>>>>>>>> never reach the final state "ret" instruction of this input.
>>>>>>>
>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>> First of all I am not talking about UTM's.
>>>>>> I am talking about x86 emulation.
>>>>>> Try to encode what you mean, here is my guess:
>>>>>>
>>>>>> void P(u32 x)
>>>>>> {
>>>>>> if (emulate_x86(x, x))
>>>>>> HERE: goto HERE;
>>>>>> return;
>>>>>> }
>>>>>>
>>>>>> int main()
>>>>>> {
>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
>>>>>> }
>>>>>
>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
>>>>>
>>>>> void UTM(u32 x, u32 y)
>>>>> {
>>>>> x(y)
>>>>> }
>>>>>
>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
>>>>>
>>>> A simulating halt decider correctly simulates its input until it
>>>> correctly determines that this simulated input would never reach its
>>>> final state.
>>>
>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
>>>
>> The semantics of the x86 language conclusively proves that H(P,P)
>> correctly determines/predicts that its complete and correct x86
>> emulation of its input would never reach the "ret" instruction of P.
>
> As previously stated, this is nonsense. Failure to explain *in detail* why the below is wrong will be taken as an admission that it is correct.
>
> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>
> To state that H aborts *and* does a complete and correct simulation is simply nonsense.


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs [V2]

<O8OdnerVE-Y_ZyT_nZ2dnUU7_8zNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35025&group=comp.theory#35025

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 27 Jun 2022 13:44:50 -0500
Date: Mon, 27 Jun 2022 13:44:49 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs [V2]
Content-Language: en-US
Newsgroups: comp.theory
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<kJKdnTmzKJCBACT_nZ2dnUU7_8zNnZ2d@giganews.com>
<20220627192020.00005278@reddwarf.jmc>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <20220627192020.00005278@reddwarf.jmc>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <O8OdnerVE-Y_ZyT_nZ2dnUU7_8zNnZ2d@giganews.com>
Lines: 144
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-4HTlPpVQ2UpZImndNV41I9Rzt/JFTSlFtBVXh6Atk0V62gTzra3F+MKmZsYimOKd2dLvXqn74UmDrDI!s06N5GEY4XTQ1OesIwluL/AhV+g4r7f2wBAZ674p1PX/SkssSkEdxdlllSvrdVwTUzUjufM1VR8u
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 7271
 by: olcott - Mon, 27 Jun 2022 18:44 UTC

On 6/27/2022 1:20 PM, Mr Flibble wrote:
> On Mon, 27 Jun 2022 07:05:46 -0500
> olcott <NoOne@NoWhere.com> wrote:
>
>> *This is the outline of the complete refutation*
>> *of the only rebuttal that anyone has left*
>>
>> (a) The complete and correct x86 emulation of the input to H(P,P) by
>> H never reaches the "ret" instruction of P.
>>
>> (b) The direct execution of P(P) does reach its "ret" instruction.
>>
>> The above two are proven to be verified facts entirely on the basis
>> of the semantics of the x86 language.
>>
>> A halt decider must compute the mapping from its inputs to an accept
>> or reject state on the basis of the actual behavior that is actually
>> specified by these inputs.
>>
>> P(P) is provably not the actual behavior of the actual input.
>>
>>
>>
>> void P(u32 x)
>> {
>> if (H(x, x))
>> HERE: goto HERE;
>> return;
>> }
>>
>> int main()
>> {
>> Output("Input_Halts = ", H1((u32)P, (u32)P));
>> }
>>
>> _P()
>> [0000163a](01) 55 push ebp
>> [0000163b](02) 8bec mov ebp,esp
>> [0000163d](03) 8b4508 mov eax,[ebp+08]
>> [00001640](01) 50 push eax
>> [00001641](03) 8b4d08 mov ecx,[ebp+08]
>> [00001644](01) 51 push ecx
>> [00001645](05) e8f0fdffff call 0000143a // call H
>> [0000164a](03) 83c408 add esp,+08
>> [0000164d](02) 85c0 test eax,eax
>> [0000164f](02) 7402 jz 00001653
>> [00001651](02) ebfe jmp 00001651
>> [00001653](01) 5d pop ebp
>> [00001654](01) c3 ret
>> Size in bytes:(0027) [00001654]
>>
>> _main()
>> [0000165a](01) 55 push ebp
>> [0000165b](02) 8bec mov ebp,esp
>> [0000165d](05) 683a160000 push 0000163a // push P
>> [00001662](05) 683a160000 push 0000163a // push P
>> [00001667](05) e8cef9ffff call 0000103a // call H1
>> [0000166c](03) 83c408 add esp,+08
>> [0000166f](01) 50 push eax // push return value
>> [00001670](05) 689b040000 push 0000049b // "Input_Halts = "
>> [00001675](05) e870eeffff call 000004ea // call Output
>> [0000167a](03) 83c408 add esp,+08
>> [0000167d](02) 33c0 xor eax,eax
>> [0000167f](01) 5d pop ebp
>> [00001680](01) c3 ret
>> Size in bytes:(0039) [00001680]
>>
>> machine stack stack machine assembly
>> address address data code language
>> ======== ======== ======== ========= =============
>> [0000165a][001026a9][00000000] 55 push ebp
>> [0000165b][001026a9][00000000] 8bec mov ebp,esp
>> [0000165d][001026a5][0000163a] 683a160000 push 0000163a // push P
>> [00001662][001026a1][0000163a] 683a160000 push 0000163a // push P
>> [00001667][0010269d][0000166c] e8cef9ffff call 0000103a // call H1
>>
>> H1: Begin Simulation Execution Trace Stored at:21275d
>> Address_of_H1:103a
>> [0000163a][00212749][0021274d] 55 push ebp
>> [0000163b][00212749][0021274d] 8bec mov ebp,esp
>> [0000163d][00212749][0021274d] 8b4508 mov eax,[ebp+08]
>> [00001640][00212745][0000163a] 50 push eax // push P
>> [00001641][00212745][0000163a] 8b4d08 mov ecx,[ebp+08]
>> [00001644][00212741][0000163a] 51 push ecx // push P
>> [00001645][0021273d][0000164a] e8f0fdffff call 0000143a // call H
>>
>> H: Begin Simulation Execution Trace Stored at:2285c5
>> Address_of_H:143a
>> [0000163a][002285b1][002285b5] 55 push ebp
>> [0000163b][002285b1][002285b5] 8bec mov ebp,esp
>> [0000163d][002285b1][002285b5] 8b4508 mov eax,[ebp+08]
>> [00001640][002285ad][0000163a] 50 push eax // push P
>> [00001641][002285ad][0000163a] 8b4d08 mov ecx,[ebp+08]
>> [00001644][002285a9][0000163a] 51 push ecx // push P
>> [00001645][002285a5][0000164a] e8f0fdffff call 0000143a // call H
>> H: Infinitely Recursive Simulation Detected Simulation Stopped
>>
>> [0000164a][00212749][0021274d] 83c408 add esp,+08
>> [0000164d][00212749][0021274d] 85c0 test eax,eax
>> [0000164f][00212749][0021274d] 7402 jz 00001653
>> [00001653][0021274d][0000111e] 5d pop ebp
>> [00001654][00212751][0000163a] c3 ret
>> H1: End Simulation Input Terminated Normally
>>
>> [0000166c][001026a9][00000000] 83c408 add esp,+08
>> [0000166f][001026a5][00000001] 50 push eax // return
>> value [00001670][001026a1][0000049b] 689b040000 push 0000049b //
>> "Input_Halts = " [00001675][001026a1][0000049b] e870eeffff call
>> 000004ea // call Output Input_Halts = 1
>> [0000167a][001026a9][00000000] 83c408 add esp,+08
>> [0000167d][001026a9][00000000] 33c0 xor eax,eax
>> [0000167f][001026ad][00100000] 5d pop ebp
>> [00001680][001026b1][00000004] c3 ret
>> Number of Instructions Executed(409590) == 6113 Pages
>
> Why the new H/H1 dichotomy? Are you finally admitting that the decider
> that main() calls is different to the decider that P would call if you
> weren't erroneously aborting the simulation?
>
> /Flibble
>

The above example proves the following:

(a) The complete and correct x86 emulation of the input to H(P,P) by H
never reaches the "ret" instruction of P.

(b) The direct execution of P(P) does reach its "ret" instruction.

The above two are proven to be verified facts entirely on the basis of
the semantics of the x86 language.

A halt decider must compute the mapping from its inputs to an accept or
reject state on the basis of the actual behavior that is actually
specified by these inputs.

P(P) is provably not the actual behavior of the actual input.

--
Copyright 2022 Pete Olcott

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

Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<6172f5eb-df88-4aaa-bdc9-fdea01454478n@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35026&group=comp.theory#35026

  copy link   Newsgroups: comp.theory
X-Received: by 2002:a05:600c:681:b0:3a0:2da6:d173 with SMTP id a1-20020a05600c068100b003a02da6d173mr21501416wmn.68.1656355505082;
Mon, 27 Jun 2022 11:45:05 -0700 (PDT)
X-Received: by 2002:a0d:f285:0:b0:31b:c2d6:2ce9 with SMTP id
b127-20020a0df285000000b0031bc2d62ce9mr7497106ywf.172.1656355504451; Mon, 27
Jun 2022 11:45:04 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.128.87.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.theory
Date: Mon, 27 Jun 2022 11:45:04 -0700 (PDT)
In-Reply-To: <jsidnZdTjLdsZST_nZ2dnUU7_8zNnZ2d@giganews.com>
Injection-Info: google-groups.googlegroups.com; posting-host=71.168.165.242; posting-account=ejFcQgoAAACAt5i0VbkATkR2ACWdgADD
NNTP-Posting-Host: 71.168.165.242
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com> <j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com> <qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com> <YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com> <f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com> <Sv-dnX5Vh499eyT_nZ2dnUU7_8zNnZ2d@giganews.com>
<fc96a583-3a51-45fd-8275-4bc8aaca8fc0n@googlegroups.com> <Lfudna-pu95HbyT_nZ2dnUU7_83NnZ2d@giganews.com>
<8bca30ba-3f3f-4b76-b401-504b4873e55en@googlegroups.com> <jsidnZdTjLdsZST_nZ2dnUU7_8zNnZ2d@giganews.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <6172f5eb-df88-4aaa-bdc9-fdea01454478n@googlegroups.com>
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
From: dbush.mo...@gmail.com (Dennis Bush)
Injection-Date: Mon, 27 Jun 2022 18:45:05 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Dennis Bush - Mon, 27 Jun 2022 18:45 UTC

On Monday, June 27, 2022 at 2:37:44 PM UTC-4, olcott wrote:
> On 6/27/2022 1:13 PM, Dennis Bush wrote:
> > On Monday, June 27, 2022 at 2:11:45 PM UTC-4, olcott wrote:
> >> On 6/27/2022 1:03 PM, Dennis Bush wrote:
> >>> On Monday, June 27, 2022 at 1:20:39 PM UTC-4, olcott wrote:
> >>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
> >>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
> >>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
> >>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
> >>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
> >>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
> >>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
> >>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
> >>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
> >>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>> *This is the outline of the complete refutation*
> >>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
> >>>>>>>>>>>>>> never reaches the "ret" instruction of P.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
> >>>>>>>>>>>>>> the semantics of the x86 language.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
> >>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> H does not perform this mapping.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> void P(u32 x)
> >>>>>>>>>>>>>> {
> >>>>>>>>>>>>>> if (H(x, x))
> >>>>>>>>>>>>>> HERE: goto HERE;
> >>>>>>>>>>>>>> return;
> >>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> int main()
> >>>>>>>>>>>>>> {
> >>>>>>>>>>>>>> P(P);
> >>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> _P()
> >>>>>>>>>>>>>> [000011f0](01) 55 push ebp
> >>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>> [000011f6](01) 50 push eax
> >>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>> [000011fa](01) 51 push ecx
> >>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
> >>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
> >>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
> >>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
> >>>>>>>>>>>>>> [00001209](01) 5d pop ebp
> >>>>>>>>>>>>>> [0000120a](01) c3 ret
> >>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> _main()
> >>>>>>>>>>>>>> [00001210](01) 55 push ebp
> >>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
> >>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
> >>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
> >>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
> >>>>>>>>>>>>>> [00001222](01) 5d pop ebp
> >>>>>>>>>>>>>> [00001223](01) c3 ret
> >>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> machine stack stack machine assembly
> >>>>>>>>>>>>>> address address data code language
> >>>>>>>>>>>>>> ======== ======== ======== ========= =============
> >>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
> >>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
> >>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
> >>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
> >>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
> >>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
> >>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
> >>>>>>>>>>>>>> Address_of_H:1020
> >>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
> >>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
> >>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
> >>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
> >>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
> >>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
> >>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
> >>>>>>>>>>>>>> recursive emulation.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> FALSE. P contains these instructions:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
> >>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
> >>>>>>>>>>>>> goto END_OF_CODE;
> >>>>>>>>>>>>> return 0; // Does not halt
> >>>>>>>>>>>>> END_OF_CODE:
> >>>>>>>>>>>>> return 1; // Input has normally terminated
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
> >>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
> >>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
> >>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
> >>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
> >>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
> >>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
> >>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
> >>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
> >>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
> >>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
> >>>>>>>>>>>> input never reaches the the "ret" instruction of P.
> >>>>>>>>>>>
> >>>>>>>>>>> Repeating your original point.
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
> >>>>>>>>>>>>
> >>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Again, repeating your original point.
> >>>>>>>>>>>
> >>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
> >>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>> Therefore H(P,P)==0 is correct.
> >>>>>>>>>>>
> >>>>>>>>>>> And again, repeating your original point.
> >>>>>>>>>>>
> >>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
> >>>>>>>>>>>
> >>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
> >>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
> >>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
> >>>>>>>>>> never reach the final state "ret" instruction of this input.
> >>>>>>>>>
> >>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>> First of all I am not talking about UTM's.
> >>>>>>>> I am talking about x86 emulation.
> >>>>>>>> Try to encode what you mean, here is my guess:
> >>>>>>>>
> >>>>>>>> void P(u32 x)
> >>>>>>>> {
> >>>>>>>> if (emulate_x86(x, x))
> >>>>>>>> HERE: goto HERE;
> >>>>>>>> return;
> >>>>>>>> }
> >>>>>>>>
> >>>>>>>> int main()
> >>>>>>>> {
> >>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
> >>>>>>>> }
> >>>>>>>
> >>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
> >>>>>>>
> >>>>>>> void UTM(u32 x, u32 y)
> >>>>>>> {
> >>>>>>> x(y)
> >>>>>>> }
> >>>>>>>
> >>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
> >>>>>>>
> >>>>>> A simulating halt decider correctly simulates its input until it
> >>>>>> correctly determines that this simulated input would never reach its
> >>>>>> final state.
> >>>>>
> >>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
> >>>>>
> >>>> Every simulating decider that correctly simulates its input until it
> >>>> correctly determines that this simulated input would never reach its
> >>>> final state correctly determines the halt status of this input.
> >>>
> >>> And H isn't such a decider, because it does not correctly determine that the input to H(P,P) would never halt as demonstrated by UTM(P,P) halting.
> >>>
> >>> The specification for H:
> >>>
> >>> H(x,y)==0 if and only if x(y) does not halt, and
> >>> H(x,y)==1 if and only if x(y) halts.
> >>>
> >>> H does not meet the specification.
> >>>
> >> The spec is provably incorrect in this case:
> >
> > A spec can't be incorrect. It just is. If it can't be satisfied, then that validates the halting problem proofs that say it can't be satisfied.
>
> A halt decider must compute the mapping from its inputs to an accept or
> reject state on the basis of the actual behavior that is actually
> specified by these inputs.


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<2fudnU_akqZGZiT_nZ2dnUU7_8zNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35027&group=comp.theory#35027

  copy link   Newsgroups: comp.theory sci.logic sci.math
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 27 Jun 2022 13:50:03 -0500
Date: Mon, 27 Jun 2022 13:50:02 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
Content-Language: en-US
Newsgroups: comp.theory,sci.logic,sci.math
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com>
<j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com>
<qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com>
<YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com>
<f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com>
<Sv-dnX5Vh499eyT_nZ2dnUU7_8zNnZ2d@giganews.com>
<fc96a583-3a51-45fd-8275-4bc8aaca8fc0n@googlegroups.com>
<Lfudna-pu95HbyT_nZ2dnUU7_83NnZ2d@giganews.com>
<8bca30ba-3f3f-4b76-b401-504b4873e55en@googlegroups.com>
<jsidnZdTjLdsZST_nZ2dnUU7_8zNnZ2d@giganews.com>
<6172f5eb-df88-4aaa-bdc9-fdea01454478n@googlegroups.com>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <6172f5eb-df88-4aaa-bdc9-fdea01454478n@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <2fudnU_akqZGZiT_nZ2dnUU7_8zNnZ2d@giganews.com>
Lines: 121
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-fprJntwnl+BIA+RWSrATiOTriqY/B++X2I7zLMVksPh4rv29PLNBCBCyDGesxO8iDMWKr6Df6lRFGtR!2IK3sOEKlix+jszunEUWxWH5pA/tNosY5byUAok/DZ+wm+Bu2PaEe4eujYfdUELiy5NQ8KtPDLIo
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 6796
 by: olcott - Mon, 27 Jun 2022 18:50 UTC

On 6/27/2022 1:45 PM, Dennis Bush wrote:
> On Monday, June 27, 2022 at 2:37:44 PM UTC-4, olcott wrote:
>> On 6/27/2022 1:13 PM, Dennis Bush wrote:
>>> On Monday, June 27, 2022 at 2:11:45 PM UTC-4, olcott wrote:

void P(u32 x)
{ if (H(x, x))
HERE: goto HERE;
return;
}

int main()
{ P(P);
}

_P()
[000011f0](01) 55 push ebp
[000011f1](02) 8bec mov ebp,esp
[000011f3](03) 8b4508 mov eax,[ebp+08]
[000011f6](01) 50 push eax
[000011f7](03) 8b4d08 mov ecx,[ebp+08]
[000011fa](01) 51 push ecx
[000011fb](05) e820feffff call 00001020

[00001200](03) 83c408 add esp,+08
[00001203](02) 85c0 test eax,eax
[00001205](02) 7402 jz 00001209
[00001207](02) ebfe jmp 00001207
[00001209](01) 5d pop ebp
[0000120a](01) c3 ret
Size in bytes:(0027) [0000120a]

_main()
[00001210](01) 55 push ebp
[00001211](02) 8bec mov ebp,esp
[00001213](05) 68f0110000 push 000011f0
[00001218](05) e8d3ffffff call 000011f0
[0000121d](03) 83c404 add esp,+04
[00001220](02) 33c0 xor eax,eax
[00001222](01) 5d pop ebp
[00001223](01) c3 ret
Size in bytes:(0020) [00001223]

machine stack stack machine assembly
address address data code language
======== ======== ======== ========= =============
[00001210][00101fba][00000000] 55 push ebp
[00001211][00101fba][00000000] 8bec mov ebp,esp
[00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
[00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
[000011f0][00101fae][00101fba] 55 push ebp // enter executed P
[000011f1][00101fae][00101fba] 8bec mov ebp,esp
[000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
[000011f6][00101faa][000011f0] 50 push eax // push P
[000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
[000011fa][00101fa6][000011f0] 51 push ecx // push P
[000011fb][00101fa2][00001200] e820feffff call 00001020 // call H

Begin Simulation Execution Trace Stored at:21206e
Address_of_H:1020
[000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
[000011f1][0021205a][0021205e] 8bec mov ebp,esp
[000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
[000011f6][00212056][000011f0] 50 push eax // push P
[000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
[000011fa][00212052][000011f0] 51 push ecx // push P
[000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
Infinitely Recursive Simulation Detected Simulation Stopped

H knows its own machine address and on this basis it can easily
examine its stored execution_trace of P (see above) to determine:
(a) P is calling H with the same arguments that H was called with.
(b) No instructions in P could possibly escape this otherwise infinitely
recursive emulation.
(c) H aborts its emulation of P before its call to H is emulated.

[00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
executed P
[00001203][00101fae][00101fba] 85c0 test eax,eax
[00001205][00101fae][00101fba] 7402 jz 00001209
[00001209][00101fb2][0000121d] 5d pop ebp
[0000120a][00101fb6][000011f0] c3 ret // return from
executed P
[0000121d][00101fba][00000000] 83c404 add esp,+04
[00001220][00101fba][00000000] 33c0 xor eax,eax
[00001222][00101fbe][00100000] 5d pop ebp
[00001223][00101fc2][00000000] c3 ret // ret from main
Number of Instructions Executed(878) / 67 = 13 pages

>> A halt decider must compute the mapping from its inputs to an accept or
>> reject state on the basis of the actual behavior that is actually
>> specified by these inputs.
>
> Which is DEFINED to be the behavior of P(P)
>
>>
>> P(P) is provably not the actual behavior of the actual input.
>
> Only if H performed an incorrect simulation.

In other words you disagree with the semantics of the x86 language.

(a) The complete and correct x86 emulation of the input to H(P,P) by H
never reaches the "ret" instruction of P.

(b) The direct execution of P(P) does reach its "ret" instruction.

The above two are proven to be verified facts entirely on the basis of
the semantics of the x86 language and the execution trace shown above.

--
Copyright 2022 Pete Olcott

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

Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<995fecc1-7fc4-4b40-8d68-fd74df13efefn@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35028&group=comp.theory#35028

  copy link   Newsgroups: comp.theory
X-Received: by 2002:a5d:4308:0:b0:219:e5a4:5729 with SMTP id h8-20020a5d4308000000b00219e5a45729mr14477670wrq.210.1656355894848;
Mon, 27 Jun 2022 11:51:34 -0700 (PDT)
X-Received: by 2002:a81:3ac6:0:b0:31b:d731:f03c with SMTP id
h189-20020a813ac6000000b0031bd731f03cmr4435316ywa.461.1656355893508; Mon, 27
Jun 2022 11:51:33 -0700 (PDT)
Path: i2pn2.org!i2pn.org!paganini.bofh.team!pasdenom.info!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!209.85.128.88.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.theory
Date: Mon, 27 Jun 2022 11:51:33 -0700 (PDT)
In-Reply-To: <68ednUyP7tp6ZCT_nZ2dnUU7_8zNnZ2d@giganews.com>
Injection-Info: google-groups.googlegroups.com; posting-host=71.168.165.242; posting-account=ejFcQgoAAACAt5i0VbkATkR2ACWdgADD
NNTP-Posting-Host: 71.168.165.242
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com> <j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com> <qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com> <YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com> <f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com> <q4CdnWm9zL2KbST_nZ2dnUU7_8zNnZ2d@giganews.com>
<9f0c8dcb-ae3a-47bf-9093-4e4d9377dc47n@googlegroups.com> <68ednUyP7tp6ZCT_nZ2dnUU7_8zNnZ2d@giganews.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <995fecc1-7fc4-4b40-8d68-fd74df13efefn@googlegroups.com>
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
From: dbush.mo...@gmail.com (Dennis Bush)
Injection-Date: Mon, 27 Jun 2022 18:51:34 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Dennis Bush - Mon, 27 Jun 2022 18:51 UTC

On Monday, June 27, 2022 at 2:41:50 PM UTC-4, olcott wrote:
> On 6/27/2022 1:08 PM, Dennis Bush wrote:
> > On Monday, June 27, 2022 at 1:59:58 PM UTC-4, olcott wrote:
> >> On 6/27/2022 12:03 PM, Dennis Bush wrote:
> >>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
> >>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
> >>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
> >>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
> >>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
> >>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
> >>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
> >>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
> >>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
> >>>>>>>>>>>> *This is the outline of the complete refutation*
> >>>>>>>>>>>> *of the only rebuttal that anyone has left*
> >>>>>>>>>>>>
> >>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
> >>>>>>>>>>>> never reaches the "ret" instruction of P.
> >>>>>>>>>>>
> >>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> >>>>>>>>>>>
> >>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> >>>>>>>>>>>
> >>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
> >>>>>>>>>>>>
> >>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
> >>>>>>>>>>>> the semantics of the x86 language.
> >>>>>>>>>>>
> >>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise..
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>
> >>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
> >>>>>>>>>>>
> >>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
> >>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
> >>>>>>>>>>>
> >>>>>>>>>>> H does not perform this mapping.
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input..
> >>>>>>>>>>>
> >>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> void P(u32 x)
> >>>>>>>>>>>> {
> >>>>>>>>>>>> if (H(x, x))
> >>>>>>>>>>>> HERE: goto HERE;
> >>>>>>>>>>>> return;
> >>>>>>>>>>>> }
> >>>>>>>>>>>>
> >>>>>>>>>>>> int main()
> >>>>>>>>>>>> {
> >>>>>>>>>>>> P(P);
> >>>>>>>>>>>> }
> >>>>>>>>>>>>
> >>>>>>>>>>>> _P()
> >>>>>>>>>>>> [000011f0](01) 55 push ebp
> >>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
> >>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>> [000011f6](01) 50 push eax
> >>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>> [000011fa](01) 51 push ecx
> >>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
> >>>>>>>>>>>>
> >>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
> >>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
> >>>>>>>>>>>> [00001205](02) 7402 jz 00001209
> >>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
> >>>>>>>>>>>> [00001209](01) 5d pop ebp
> >>>>>>>>>>>> [0000120a](01) c3 ret
> >>>>>>>>>>>> Size in bytes:(0027) [0000120a]
> >>>>>>>>>>>>
> >>>>>>>>>>>> _main()
> >>>>>>>>>>>> [00001210](01) 55 push ebp
> >>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
> >>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
> >>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
> >>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
> >>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
> >>>>>>>>>>>> [00001222](01) 5d pop ebp
> >>>>>>>>>>>> [00001223](01) c3 ret
> >>>>>>>>>>>> Size in bytes:(0020) [00001223]
> >>>>>>>>>>>>
> >>>>>>>>>>>> machine stack stack machine assembly
> >>>>>>>>>>>> address address data code language
> >>>>>>>>>>>> ======== ======== ======== ========= =============
> >>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
> >>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
> >>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
> >>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
> >>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
> >>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
> >>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
> >>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
> >>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
> >>>>>>>>>>>>
> >>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
> >>>>>>>>>>>> Address_of_H:1020
> >>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
> >>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
> >>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
> >>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
> >>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
> >>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
> >>>>>>>>>>>>
> >>>>>>>>>>>> H knows its own machine address and on this basis it can easily
> >>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
> >>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
> >>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
> >>>>>>>>>>>> recursive emulation.
> >>>>>>>>>>>
> >>>>>>>>>>> FALSE. P contains these instructions:
> >>>>>>>>>>>
> >>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
> >>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
> >>>>>>>>>>> goto END_OF_CODE;
> >>>>>>>>>>> return 0; // Does not halt
> >>>>>>>>>>> END_OF_CODE:
> >>>>>>>>>>> return 1; // Input has normally terminated
> >>>>>>>>>>>
> >>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
> >>>>>>>>>>>
> >>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
> >>>>>>>>>>>
> >>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
> >>>>>>>>>>>> executed P
> >>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
> >>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
> >>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
> >>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
> >>>>>>>>>>>> executed P
> >>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
> >>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
> >>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
> >>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
> >>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
> >>>>>>>>>>>
> >>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
> >>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
> >>>>>>>>>> input never reaches the the "ret" instruction of P.
> >>>>>>>>>
> >>>>>>>>> Repeating your original point.
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> This is the actual behavior of the input to H(P,P).
> >>>>>>>>>>
> >>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Again, repeating your original point.
> >>>>>>>>>
> >>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
> >>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>> specified by these inputs.
> >>>>>>>>>> Therefore H(P,P)==0 is correct.
> >>>>>>>>>
> >>>>>>>>> And again, repeating your original point.
> >>>>>>>>>
> >>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
> >>>>>>>>>
> >>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
> >>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
> >>>>>>>> halt decider correctly predicts that its correctly simulated input will
> >>>>>>>> never reach the final state "ret" instruction of this input.
> >>>>>>>
> >>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>> First of all I am not talking about UTM's.
> >>>>>> I am talking about x86 emulation.
> >>>>>> Try to encode what you mean, here is my guess:
> >>>>>>
> >>>>>> void P(u32 x)
> >>>>>> {
> >>>>>> if (emulate_x86(x, x))
> >>>>>> HERE: goto HERE;
> >>>>>> return;
> >>>>>> }
> >>>>>>
> >>>>>> int main()
> >>>>>> {
> >>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
> >>>>>> }
> >>>>>
> >>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
> >>>>>
> >>>>> void UTM(u32 x, u32 y)
> >>>>> {
> >>>>> x(y)
> >>>>> }
> >>>>>
> >>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
> >>>>>
> >>>> A simulating halt decider correctly simulates its input until it
> >>>> correctly determines that this simulated input would never reach its
> >>>> final state.
> >>>
> >>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
> >>>
> >> The semantics of the x86 language conclusively proves that H(P,P)
> >> correctly determines/predicts that its complete and correct x86
> >> emulation of its input would never reach the "ret" instruction of P.
> >
> > As previously stated, this is nonsense. Failure to explain *in detail* why the below is wrong will be taken as an admission that it is correct.
> >
> > It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> >
> > To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> I NEVER SAID that H does a complete and correct simulation of its input.


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs [V2]

<20220627195334.0000091d@reddwarf.jmc>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35029&group=comp.theory#35029

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!peer01.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!fx01.ams4.POSTED!not-for-mail
From: flib...@reddwarf.jmc (Mr Flibble)
Newsgroups: comp.theory
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs [V2]
Message-ID: <20220627195334.0000091d@reddwarf.jmc>
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<kJKdnTmzKJCBACT_nZ2dnUU7_8zNnZ2d@giganews.com>
<20220627192020.00005278@reddwarf.jmc>
<O8OdnerVE-Y_ZyT_nZ2dnUU7_8zNnZ2d@giganews.com>
Organization: Jupiter Mining Corp
X-Newsreader: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-w64-mingw32)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Lines: 136
X-Complaints-To: abuse@eweka.nl
NNTP-Posting-Date: Mon, 27 Jun 2022 18:53:30 UTC
Date: Mon, 27 Jun 2022 19:53:34 +0100
X-Received-Bytes: 6745
 by: Mr Flibble - Mon, 27 Jun 2022 18:53 UTC

On Mon, 27 Jun 2022 13:44:49 -0500
olcott <NoOne@NoWhere.com> wrote:

> On 6/27/2022 1:20 PM, Mr Flibble wrote:
> > On Mon, 27 Jun 2022 07:05:46 -0500
> > olcott <NoOne@NoWhere.com> wrote:
> >
> >> *This is the outline of the complete refutation*
> >> *of the only rebuttal that anyone has left*
> >>
> >> (a) The complete and correct x86 emulation of the input to H(P,P)
> >> by H never reaches the "ret" instruction of P.
> >>
> >> (b) The direct execution of P(P) does reach its "ret" instruction.
> >>
> >> The above two are proven to be verified facts entirely on the basis
> >> of the semantics of the x86 language.
> >>
> >> A halt decider must compute the mapping from its inputs to an
> >> accept or reject state on the basis of the actual behavior that is
> >> actually specified by these inputs.
> >>
> >> P(P) is provably not the actual behavior of the actual input.
> >>
> >>
> >>
> >> void P(u32 x)
> >> {
> >> if (H(x, x))
> >> HERE: goto HERE;
> >> return;
> >> }
> >>
> >> int main()
> >> {
> >> Output("Input_Halts = ", H1((u32)P, (u32)P));
> >> }
> >>
> >> _P()
> >> [0000163a](01) 55 push ebp
> >> [0000163b](02) 8bec mov ebp,esp
> >> [0000163d](03) 8b4508 mov eax,[ebp+08]
> >> [00001640](01) 50 push eax
> >> [00001641](03) 8b4d08 mov ecx,[ebp+08]
> >> [00001644](01) 51 push ecx
> >> [00001645](05) e8f0fdffff call 0000143a // call H
> >> [0000164a](03) 83c408 add esp,+08
> >> [0000164d](02) 85c0 test eax,eax
> >> [0000164f](02) 7402 jz 00001653
> >> [00001651](02) ebfe jmp 00001651
> >> [00001653](01) 5d pop ebp
> >> [00001654](01) c3 ret
> >> Size in bytes:(0027) [00001654]
> >>
> >> _main()
> >> [0000165a](01) 55 push ebp
> >> [0000165b](02) 8bec mov ebp,esp
> >> [0000165d](05) 683a160000 push 0000163a // push P
> >> [00001662](05) 683a160000 push 0000163a // push P
> >> [00001667](05) e8cef9ffff call 0000103a // call H1
> >> [0000166c](03) 83c408 add esp,+08
> >> [0000166f](01) 50 push eax // push return value
> >> [00001670](05) 689b040000 push 0000049b // "Input_Halts = "
> >> [00001675](05) e870eeffff call 000004ea // call Output
> >> [0000167a](03) 83c408 add esp,+08
> >> [0000167d](02) 33c0 xor eax,eax
> >> [0000167f](01) 5d pop ebp
> >> [00001680](01) c3 ret
> >> Size in bytes:(0039) [00001680]
> >>
> >> machine stack stack machine assembly
> >> address address data code language
> >> ======== ======== ======== ========= =============
> >> [0000165a][001026a9][00000000] 55 push ebp
> >> [0000165b][001026a9][00000000] 8bec mov ebp,esp
> >> [0000165d][001026a5][0000163a] 683a160000 push 0000163a // push P
> >> [00001662][001026a1][0000163a] 683a160000 push 0000163a // push P
> >> [00001667][0010269d][0000166c] e8cef9ffff call 0000103a // call H1
> >>
> >> H1: Begin Simulation Execution Trace Stored at:21275d
> >> Address_of_H1:103a
> >> [0000163a][00212749][0021274d] 55 push ebp
> >> [0000163b][00212749][0021274d] 8bec mov ebp,esp
> >> [0000163d][00212749][0021274d] 8b4508 mov eax,[ebp+08]
> >> [00001640][00212745][0000163a] 50 push eax // push P
> >> [00001641][00212745][0000163a] 8b4d08 mov ecx,[ebp+08]
> >> [00001644][00212741][0000163a] 51 push ecx // push P
> >> [00001645][0021273d][0000164a] e8f0fdffff call 0000143a // call H
> >>
> >> H: Begin Simulation Execution Trace Stored at:2285c5
> >> Address_of_H:143a
> >> [0000163a][002285b1][002285b5] 55 push ebp
> >> [0000163b][002285b1][002285b5] 8bec mov ebp,esp
> >> [0000163d][002285b1][002285b5] 8b4508 mov eax,[ebp+08]
> >> [00001640][002285ad][0000163a] 50 push eax // push P
> >> [00001641][002285ad][0000163a] 8b4d08 mov ecx,[ebp+08]
> >> [00001644][002285a9][0000163a] 51 push ecx // push P
> >> [00001645][002285a5][0000164a] e8f0fdffff call 0000143a // call H
> >> H: Infinitely Recursive Simulation Detected Simulation Stopped
> >>
> >> [0000164a][00212749][0021274d] 83c408 add esp,+08
> >> [0000164d][00212749][0021274d] 85c0 test eax,eax
> >> [0000164f][00212749][0021274d] 7402 jz 00001653
> >> [00001653][0021274d][0000111e] 5d pop ebp
> >> [00001654][00212751][0000163a] c3 ret
> >> H1: End Simulation Input Terminated Normally
> >>
> >> [0000166c][001026a9][00000000] 83c408 add esp,+08
> >> [0000166f][001026a5][00000001] 50 push eax // return
> >> value [00001670][001026a1][0000049b] 689b040000 push 0000049b //
> >> "Input_Halts = " [00001675][001026a1][0000049b] e870eeffff call
> >> 000004ea // call Output Input_Halts = 1
> >> [0000167a][001026a9][00000000] 83c408 add esp,+08
> >> [0000167d][001026a9][00000000] 33c0 xor eax,eax
> >> [0000167f][001026ad][00100000] 5d pop ebp
> >> [00001680][001026b1][00000004] c3 ret
> >> Number of Instructions Executed(409590) == 6113 Pages
> >
> > Why the new H/H1 dichotomy? Are you finally admitting that the
> > decider that main() calls is different to the decider that P would
> > call if you weren't erroneously aborting the simulation?
> >
> > /Flibble
> >
>
> The above example proves the following:
>
> (a) The complete and correct x86 emulation of the input to H(P,P) by
> H never reaches the "ret" instruction of P.
>
> (b) The direct execution of P(P) does reach its "ret" instruction.

Then H returned the wrong answer. See [Strachey, 1965].

/Flibble

Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<s7ednVfn1vRNYyT_nZ2dnUU7_83NnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35030&group=comp.theory#35030

  copy link   Newsgroups: comp.theory sci.logic sci.math
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 27 Jun 2022 14:02:40 -0500
Date: Mon, 27 Jun 2022 14:02:39 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
Content-Language: en-US
Newsgroups: comp.theory,sci.logic,sci.math
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com>
<j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com>
<qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com>
<YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com>
<f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com>
<q4CdnWm9zL2KbST_nZ2dnUU7_8zNnZ2d@giganews.com>
<9f0c8dcb-ae3a-47bf-9093-4e4d9377dc47n@googlegroups.com>
<68ednUyP7tp6ZCT_nZ2dnUU7_8zNnZ2d@giganews.com>
<995fecc1-7fc4-4b40-8d68-fd74df13efefn@googlegroups.com>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <995fecc1-7fc4-4b40-8d68-fd74df13efefn@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <s7ednVfn1vRNYyT_nZ2dnUU7_83NnZ2d@giganews.com>
Lines: 268
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-lf0Yikir3grdC+RGWNHqghYC27/HBEsop9eYMDm/3hI9/ngfCyJyO2vqQhiAeTu1VlivNMf9IV6GaCP!DNhD2xo/tXHihVQE2PLKhBWygISvKfI5nmn6rTz8GVFJolZanKYjNgjBd3Xlhe6C/USTZoTJBHZ0
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 15103
 by: olcott - Mon, 27 Jun 2022 19:02 UTC

On 6/27/2022 1:51 PM, Dennis Bush wrote:
> On Monday, June 27, 2022 at 2:41:50 PM UTC-4, olcott wrote:
>> On 6/27/2022 1:08 PM, Dennis Bush wrote:
>>> On Monday, June 27, 2022 at 1:59:58 PM UTC-4, olcott wrote:
>>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
>>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
>>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
>>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
>>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
>>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
>>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
>>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
>>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
>>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>> *This is the outline of the complete refutation*
>>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
>>>>>>>>>>>>>> never reaches the "ret" instruction of P.
>>>>>>>>>>>>>
>>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>>>>>>>>>>>
>>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>>>>>>>>>>>>>
>>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
>>>>>>>>>>>>>> the semantics of the x86 language.
>>>>>>>>>>>>>
>>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
>>>>>>>>>>>>>
>>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
>>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
>>>>>>>>>>>>>
>>>>>>>>>>>>> H does not perform this mapping.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
>>>>>>>>>>>>>
>>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> void P(u32 x)
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>> if (H(x, x))
>>>>>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>>>>>> return;
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>> P(P);
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _P()
>>>>>>>>>>>>>> [000011f0](01) 55 push ebp
>>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
>>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>> [000011f6](01) 50 push eax
>>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>> [000011fa](01) 51 push ecx
>>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
>>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
>>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
>>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
>>>>>>>>>>>>>> [00001209](01) 5d pop ebp
>>>>>>>>>>>>>> [0000120a](01) c3 ret
>>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _main()
>>>>>>>>>>>>>> [00001210](01) 55 push ebp
>>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
>>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
>>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
>>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
>>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
>>>>>>>>>>>>>> [00001222](01) 5d pop ebp
>>>>>>>>>>>>>> [00001223](01) c3 ret
>>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> machine stack stack machine assembly
>>>>>>>>>>>>>> address address data code language
>>>>>>>>>>>>>> ======== ======== ======== ========= =============
>>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
>>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
>>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
>>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
>>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
>>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
>>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
>>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
>>>>>>>>>>>>>> Address_of_H:1020
>>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
>>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
>>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
>>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
>>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
>>>>>>>>>>>>>> recursive emulation.
>>>>>>>>>>>>>
>>>>>>>>>>>>> FALSE. P contains these instructions:
>>>>>>>>>>>>>
>>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
>>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
>>>>>>>>>>>>> goto END_OF_CODE;
>>>>>>>>>>>>> return 0; // Does not halt
>>>>>>>>>>>>> END_OF_CODE:
>>>>>>>>>>>>> return 1; // Input has normally terminated
>>>>>>>>>>>>>
>>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
>>>>>>>>>>>>>
>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
>>>>>>>>>>>>>
>>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
>>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
>>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
>>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
>>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
>>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
>>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
>>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
>>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
>>>>>>>>>>>> input never reaches the the "ret" instruction of P.
>>>>>>>>>>>
>>>>>>>>>>> Repeating your original point.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
>>>>>>>>>>>>
>>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Again, repeating your original point.
>>>>>>>>>>>
>>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>> Therefore H(P,P)==0 is correct.
>>>>>>>>>>>
>>>>>>>>>>> And again, repeating your original point.
>>>>>>>>>>>
>>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
>>>>>>>>>>>
>>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
>>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
>>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
>>>>>>>>>> never reach the final state "ret" instruction of this input.
>>>>>>>>>
>>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>> First of all I am not talking about UTM's.
>>>>>>>> I am talking about x86 emulation.
>>>>>>>> Try to encode what you mean, here is my guess:
>>>>>>>>
>>>>>>>> void P(u32 x)
>>>>>>>> {
>>>>>>>> if (emulate_x86(x, x))
>>>>>>>> HERE: goto HERE;
>>>>>>>> return;
>>>>>>>> }
>>>>>>>>
>>>>>>>> int main()
>>>>>>>> {
>>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
>>>>>>>> }
>>>>>>>
>>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
>>>>>>>
>>>>>>> void UTM(u32 x, u32 y)
>>>>>>> {
>>>>>>> x(y)
>>>>>>> }
>>>>>>>
>>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
>>>>>>>
>>>>>> A simulating halt decider correctly simulates its input until it
>>>>>> correctly determines that this simulated input would never reach its
>>>>>> final state.
>>>>>
>>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
>>>>>
>>>> The semantics of the x86 language conclusively proves that H(P,P)
>>>> correctly determines/predicts that its complete and correct x86
>>>> emulation of its input would never reach the "ret" instruction of P.
>>>
>>> As previously stated, this is nonsense. Failure to explain *in detail* why the below is wrong will be taken as an admission that it is correct.
>>>
>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>
>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>> I NEVER SAID that H does a complete and correct simulation of its input.
>
> Yes you did:
>
>> a) The complete and correct x86 emulation of the input to H(P,P) by H never reaches the "ret" instruction of P.
>


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs [V2]

<s7ednVbn1vReYiT_nZ2dnUU7_81g4p2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35031&group=comp.theory#35031

  copy link   Newsgroups: comp.theory sci.logic sci.math
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 27 Jun 2022 14:06:43 -0500
Date: Mon, 27 Jun 2022 14:06:42 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs [V2]
Content-Language: en-US
Newsgroups: comp.theory,sci.logic,sci.math
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<kJKdnTmzKJCBACT_nZ2dnUU7_8zNnZ2d@giganews.com>
<20220627192020.00005278@reddwarf.jmc>
<O8OdnerVE-Y_ZyT_nZ2dnUU7_8zNnZ2d@giganews.com>
<20220627195334.0000091d@reddwarf.jmc>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <20220627195334.0000091d@reddwarf.jmc>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Message-ID: <s7ednVbn1vReYiT_nZ2dnUU7_81g4p2d@giganews.com>
Lines: 225
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-874mJxbm6paO+fzNNzzSCX9nHWnqi8TFbGlG27W3Hsi/kX0L3ZVEQK7gX1YzKolt4gHFuJzkQed8+XK!GKBAp2VTHksJJmfHCJVAqLCAA0clipUaYWqdzhYxOQtAAh97+4i8mWZf4p5ae9W3tgVs94Zc4pFp
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 10658
 by: olcott - Mon, 27 Jun 2022 19:06 UTC

On 6/27/2022 1:53 PM, Mr Flibble wrote:
> On Mon, 27 Jun 2022 13:44:49 -0500
> olcott <NoOne@NoWhere.com> wrote:
>
>> On 6/27/2022 1:20 PM, Mr Flibble wrote:
>>> On Mon, 27 Jun 2022 07:05:46 -0500
>>> olcott <NoOne@NoWhere.com> wrote:
>>>
>>>> *This is the outline of the complete refutation*
>>>> *of the only rebuttal that anyone has left*
>>>>
>>>> (a) The complete and correct x86 emulation of the input to H(P,P)
>>>> by H never reaches the "ret" instruction of P.
>>>>
>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
>>>>
>>>> The above two are proven to be verified facts entirely on the basis
>>>> of the semantics of the x86 language.
>>>>
>>>> A halt decider must compute the mapping from its inputs to an
>>>> accept or reject state on the basis of the actual behavior that is
>>>> actually specified by these inputs.
>>>>
>>>> P(P) is provably not the actual behavior of the actual input.
>>>>
>>>>
>>>>
>>>> void P(u32 x)
>>>> {
>>>> if (H(x, x))
>>>> HERE: goto HERE;
>>>> return;
>>>> }
>>>>
>>>> int main()
>>>> {
>>>> Output("Input_Halts = ", H1((u32)P, (u32)P));
>>>> }
>>>>
>>>> _P()
>>>> [0000163a](01) 55 push ebp
>>>> [0000163b](02) 8bec mov ebp,esp
>>>> [0000163d](03) 8b4508 mov eax,[ebp+08]
>>>> [00001640](01) 50 push eax
>>>> [00001641](03) 8b4d08 mov ecx,[ebp+08]
>>>> [00001644](01) 51 push ecx
>>>> [00001645](05) e8f0fdffff call 0000143a // call H
>>>> [0000164a](03) 83c408 add esp,+08
>>>> [0000164d](02) 85c0 test eax,eax
>>>> [0000164f](02) 7402 jz 00001653
>>>> [00001651](02) ebfe jmp 00001651
>>>> [00001653](01) 5d pop ebp
>>>> [00001654](01) c3 ret
>>>> Size in bytes:(0027) [00001654]
>>>>
>>>> _main()
>>>> [0000165a](01) 55 push ebp
>>>> [0000165b](02) 8bec mov ebp,esp
>>>> [0000165d](05) 683a160000 push 0000163a // push P
>>>> [00001662](05) 683a160000 push 0000163a // push P
>>>> [00001667](05) e8cef9ffff call 0000103a // call H1
>>>> [0000166c](03) 83c408 add esp,+08
>>>> [0000166f](01) 50 push eax // push return value
>>>> [00001670](05) 689b040000 push 0000049b // "Input_Halts = "
>>>> [00001675](05) e870eeffff call 000004ea // call Output
>>>> [0000167a](03) 83c408 add esp,+08
>>>> [0000167d](02) 33c0 xor eax,eax
>>>> [0000167f](01) 5d pop ebp
>>>> [00001680](01) c3 ret
>>>> Size in bytes:(0039) [00001680]
>>>>
>>>> machine stack stack machine assembly
>>>> address address data code language
>>>> ======== ======== ======== ========= =============
>>>> [0000165a][001026a9][00000000] 55 push ebp
>>>> [0000165b][001026a9][00000000] 8bec mov ebp,esp
>>>> [0000165d][001026a5][0000163a] 683a160000 push 0000163a // push P
>>>> [00001662][001026a1][0000163a] 683a160000 push 0000163a // push P
>>>> [00001667][0010269d][0000166c] e8cef9ffff call 0000103a // call H1
>>>>
>>>> H1: Begin Simulation Execution Trace Stored at:21275d
>>>> Address_of_H1:103a
>>>> [0000163a][00212749][0021274d] 55 push ebp
>>>> [0000163b][00212749][0021274d] 8bec mov ebp,esp
>>>> [0000163d][00212749][0021274d] 8b4508 mov eax,[ebp+08]
>>>> [00001640][00212745][0000163a] 50 push eax // push P
>>>> [00001641][00212745][0000163a] 8b4d08 mov ecx,[ebp+08]
>>>> [00001644][00212741][0000163a] 51 push ecx // push P
>>>> [00001645][0021273d][0000164a] e8f0fdffff call 0000143a // call H
>>>>
>>>> H: Begin Simulation Execution Trace Stored at:2285c5
>>>> Address_of_H:143a
>>>> [0000163a][002285b1][002285b5] 55 push ebp
>>>> [0000163b][002285b1][002285b5] 8bec mov ebp,esp
>>>> [0000163d][002285b1][002285b5] 8b4508 mov eax,[ebp+08]
>>>> [00001640][002285ad][0000163a] 50 push eax // push P
>>>> [00001641][002285ad][0000163a] 8b4d08 mov ecx,[ebp+08]
>>>> [00001644][002285a9][0000163a] 51 push ecx // push P
>>>> [00001645][002285a5][0000164a] e8f0fdffff call 0000143a // call H
>>>> H: Infinitely Recursive Simulation Detected Simulation Stopped
>>>>
>>>> [0000164a][00212749][0021274d] 83c408 add esp,+08
>>>> [0000164d][00212749][0021274d] 85c0 test eax,eax
>>>> [0000164f][00212749][0021274d] 7402 jz 00001653
>>>> [00001653][0021274d][0000111e] 5d pop ebp
>>>> [00001654][00212751][0000163a] c3 ret
>>>> H1: End Simulation Input Terminated Normally
>>>>
>>>> [0000166c][001026a9][00000000] 83c408 add esp,+08
>>>> [0000166f][001026a5][00000001] 50 push eax // return
>>>> value [00001670][001026a1][0000049b] 689b040000 push 0000049b //
>>>> "Input_Halts = " [00001675][001026a1][0000049b] e870eeffff call
>>>> 000004ea // call Output Input_Halts = 1
>>>> [0000167a][001026a9][00000000] 83c408 add esp,+08
>>>> [0000167d][001026a9][00000000] 33c0 xor eax,eax
>>>> [0000167f][001026ad][00100000] 5d pop ebp
>>>> [00001680][001026b1][00000004] c3 ret
>>>> Number of Instructions Executed(409590) == 6113 Pages
>>>
>>> Why the new H/H1 dichotomy? Are you finally admitting that the
>>> decider that main() calls is different to the decider that P would
>>> call if you weren't erroneously aborting the simulation?
>>>
>>> /Flibble
>>>
>>
>> The above example proves the following:
>>
>> (a) The complete and correct x86 emulation of the input to H(P,P) by
>> H never reaches the "ret" instruction of P.
>>
>> (b) The direct execution of P(P) does reach its "ret" instruction.
>
> Then H returned the wrong answer. See [Strachey, 1965].
>
> /Flibble
>

So your rebuttals simply ignore that I proved you are wrong?

// rec routine P
// §L :if T[P] go to L
// Return §
// https://academic.oup.com/comjnl/article/7/4/313/354243
void Strachey_P()
{ L:if (T(Strachey_P))
goto L;
return;
}

int main()
{ Output("Input_Halts = ", T(Strachey_P));
}

_Strachey_P()
[000015b2](01) 55 push ebp
[000015b3](02) 8bec mov ebp,esp
[000015b5](05) 68b2150000 push 000015b2 // push Strachey_P
[000015ba](05) e813fdffff call 000012d2 // call T
[000015bf](03) 83c404 add esp,+04
[000015c2](02) 85c0 test eax,eax
[000015c4](02) 7402 jz 000015c8
[000015c6](02) ebed jmp 000015b5
[000015c8](01) 5d pop ebp
[000015c9](01) c3 ret
Size in bytes:(0024) [000015c9]

_main()
[000015d2](01) 55 push ebp
[000015d3](02) 8bec mov ebp,esp
[000015d5](05) 68b2150000 push 000015b2 // push Strachey_P
[000015da](05) e8f3fcffff call 000012d2 // call T
[000015df](03) 83c404 add esp,+04
[000015e2](01) 50 push eax
[000015e3](05) 6833040000 push 00000433
[000015e8](05) e895eeffff call 00000482
[000015ed](03) 83c408 add esp,+08
[000015f0](02) 33c0 xor eax,eax
[000015f2](01) 5d pop ebp
[000015f3](01) c3 ret
Size in bytes:(0034) [000015f3]

machine stack stack machine assembly
address address data code language
======== ======== ======== ========= =============
[000015d2][001025c6][00000000] 55 push ebp
[000015d3][001025c6][00000000] 8bec mov ebp,esp
[000015d5][001025c2][000015b2] 68b2150000 push 000015b2 // push Strachey_P
[000015da][001025be][000015df] e8f3fcffff call 000012d2 // call T


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<b9d6501d-9279-4862-b727-893b042022ben@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35032&group=comp.theory#35032

  copy link   Newsgroups: comp.theory
X-Received: by 2002:a5d:5a12:0:b0:21b:993a:7f8c with SMTP id bq18-20020a5d5a12000000b0021b993a7f8cmr13422985wrb.43.1656357191352;
Mon, 27 Jun 2022 12:13:11 -0700 (PDT)
X-Received: by 2002:a25:e750:0:b0:66c:8064:624 with SMTP id
e77-20020a25e750000000b0066c80640624mr15149173ybh.632.1656357190791; Mon, 27
Jun 2022 12:13:10 -0700 (PDT)
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!news.mixmin.net!proxad.net!feeder1-2.proxad.net!209.85.128.88.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.theory
Date: Mon, 27 Jun 2022 12:13:10 -0700 (PDT)
In-Reply-To: <s7ednVfn1vRNYyT_nZ2dnUU7_83NnZ2d@giganews.com>
Injection-Info: google-groups.googlegroups.com; posting-host=71.168.165.242; posting-account=ejFcQgoAAACAt5i0VbkATkR2ACWdgADD
NNTP-Posting-Host: 71.168.165.242
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com> <j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com> <qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com> <YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com> <f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com> <q4CdnWm9zL2KbST_nZ2dnUU7_8zNnZ2d@giganews.com>
<9f0c8dcb-ae3a-47bf-9093-4e4d9377dc47n@googlegroups.com> <68ednUyP7tp6ZCT_nZ2dnUU7_8zNnZ2d@giganews.com>
<995fecc1-7fc4-4b40-8d68-fd74df13efefn@googlegroups.com> <s7ednVfn1vRNYyT_nZ2dnUU7_83NnZ2d@giganews.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <b9d6501d-9279-4862-b727-893b042022ben@googlegroups.com>
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
From: dbush.mo...@gmail.com (Dennis Bush)
Injection-Date: Mon, 27 Jun 2022 19:13:11 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Dennis Bush - Mon, 27 Jun 2022 19:13 UTC

On Monday, June 27, 2022 at 3:02:47 PM UTC-4, olcott wrote:
> On 6/27/2022 1:51 PM, Dennis Bush wrote:
> > On Monday, June 27, 2022 at 2:41:50 PM UTC-4, olcott wrote:
> >> On 6/27/2022 1:08 PM, Dennis Bush wrote:
> >>> On Monday, June 27, 2022 at 1:59:58 PM UTC-4, olcott wrote:
> >>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
> >>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
> >>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
> >>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
> >>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
> >>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
> >>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
> >>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
> >>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
> >>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>> *This is the outline of the complete refutation*
> >>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
> >>>>>>>>>>>>>> never reaches the "ret" instruction of P.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
> >>>>>>>>>>>>>> the semantics of the x86 language.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
> >>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> H does not perform this mapping.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> void P(u32 x)
> >>>>>>>>>>>>>> {
> >>>>>>>>>>>>>> if (H(x, x))
> >>>>>>>>>>>>>> HERE: goto HERE;
> >>>>>>>>>>>>>> return;
> >>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> int main()
> >>>>>>>>>>>>>> {
> >>>>>>>>>>>>>> P(P);
> >>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> _P()
> >>>>>>>>>>>>>> [000011f0](01) 55 push ebp
> >>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>> [000011f6](01) 50 push eax
> >>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>> [000011fa](01) 51 push ecx
> >>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
> >>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
> >>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
> >>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
> >>>>>>>>>>>>>> [00001209](01) 5d pop ebp
> >>>>>>>>>>>>>> [0000120a](01) c3 ret
> >>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> _main()
> >>>>>>>>>>>>>> [00001210](01) 55 push ebp
> >>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
> >>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
> >>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
> >>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
> >>>>>>>>>>>>>> [00001222](01) 5d pop ebp
> >>>>>>>>>>>>>> [00001223](01) c3 ret
> >>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> machine stack stack machine assembly
> >>>>>>>>>>>>>> address address data code language
> >>>>>>>>>>>>>> ======== ======== ======== ========= =============
> >>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
> >>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
> >>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
> >>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
> >>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
> >>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
> >>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
> >>>>>>>>>>>>>> Address_of_H:1020
> >>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
> >>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
> >>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
> >>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
> >>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
> >>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
> >>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
> >>>>>>>>>>>>>> recursive emulation.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> FALSE. P contains these instructions:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
> >>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
> >>>>>>>>>>>>> goto END_OF_CODE;
> >>>>>>>>>>>>> return 0; // Does not halt
> >>>>>>>>>>>>> END_OF_CODE:
> >>>>>>>>>>>>> return 1; // Input has normally terminated
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
> >>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
> >>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
> >>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
> >>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
> >>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
> >>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
> >>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
> >>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
> >>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
> >>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
> >>>>>>>>>>>> input never reaches the the "ret" instruction of P.
> >>>>>>>>>>>
> >>>>>>>>>>> Repeating your original point.
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
> >>>>>>>>>>>>
> >>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Again, repeating your original point.
> >>>>>>>>>>>
> >>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
> >>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>> Therefore H(P,P)==0 is correct.
> >>>>>>>>>>>
> >>>>>>>>>>> And again, repeating your original point.
> >>>>>>>>>>>
> >>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
> >>>>>>>>>>>
> >>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
> >>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
> >>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
> >>>>>>>>>> never reach the final state "ret" instruction of this input.
> >>>>>>>>>
> >>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>> First of all I am not talking about UTM's.
> >>>>>>>> I am talking about x86 emulation.
> >>>>>>>> Try to encode what you mean, here is my guess:
> >>>>>>>>
> >>>>>>>> void P(u32 x)
> >>>>>>>> {
> >>>>>>>> if (emulate_x86(x, x))
> >>>>>>>> HERE: goto HERE;
> >>>>>>>> return;
> >>>>>>>> }
> >>>>>>>>
> >>>>>>>> int main()
> >>>>>>>> {
> >>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
> >>>>>>>> }
> >>>>>>>
> >>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
> >>>>>>>
> >>>>>>> void UTM(u32 x, u32 y)
> >>>>>>> {
> >>>>>>> x(y)
> >>>>>>> }
> >>>>>>>
> >>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
> >>>>>>>
> >>>>>> A simulating halt decider correctly simulates its input until it
> >>>>>> correctly determines that this simulated input would never reach its
> >>>>>> final state.
> >>>>>
> >>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
> >>>>>
> >>>> The semantics of the x86 language conclusively proves that H(P,P)
> >>>> correctly determines/predicts that its complete and correct x86
> >>>> emulation of its input would never reach the "ret" instruction of P.
> >>>
> >>> As previously stated, this is nonsense. Failure to explain *in detail* why the below is wrong will be taken as an admission that it is correct.
> >>>
> >>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> >>>
> >>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> >> I NEVER SAID that H does a complete and correct simulation of its input.
> >
> > Yes you did:
> >
> >> a) The complete and correct x86 emulation of the input to H(P,P) by H never reaches the "ret" instruction of P.
> >
> This does not say that H does a complete emulation.
> A simulating halt decider correctly simulates its input until it
> correctly determines that this simulated input would never reach its
> final state.


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs [V2]

<20220627201942.00003770@reddwarf.jmc>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35033&group=comp.theory#35033

  copy link   Newsgroups: comp.theory sci.logic sci.math
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!fx14.ams4.POSTED!not-for-mail
From: flib...@reddwarf.jmc (Mr Flibble)
Newsgroups: comp.theory,sci.logic,sci.math
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs [V2]
Message-ID: <20220627201942.00003770@reddwarf.jmc>
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<kJKdnTmzKJCBACT_nZ2dnUU7_8zNnZ2d@giganews.com>
<20220627192020.00005278@reddwarf.jmc>
<O8OdnerVE-Y_ZyT_nZ2dnUU7_8zNnZ2d@giganews.com>
<20220627195334.0000091d@reddwarf.jmc>
<s7ednVbn1vReYiT_nZ2dnUU7_81g4p2d@giganews.com>
Organization: Jupiter Mining Corp
X-Newsreader: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-w64-mingw32)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Lines: 235
X-Complaints-To: abuse@eweka.nl
NNTP-Posting-Date: Mon, 27 Jun 2022 19:19:39 UTC
Date: Mon, 27 Jun 2022 20:19:42 +0100
X-Received-Bytes: 11057
 by: Mr Flibble - Mon, 27 Jun 2022 19:19 UTC

On Mon, 27 Jun 2022 14:06:42 -0500
olcott <NoOne@NoWhere.com> wrote:

> On 6/27/2022 1:53 PM, Mr Flibble wrote:
> > On Mon, 27 Jun 2022 13:44:49 -0500
> > olcott <NoOne@NoWhere.com> wrote:
> >
> >> On 6/27/2022 1:20 PM, Mr Flibble wrote:
> >>> On Mon, 27 Jun 2022 07:05:46 -0500
> >>> olcott <NoOne@NoWhere.com> wrote:
> >>>
> >>>> *This is the outline of the complete refutation*
> >>>> *of the only rebuttal that anyone has left*
> >>>>
> >>>> (a) The complete and correct x86 emulation of the input to H(P,P)
> >>>> by H never reaches the "ret" instruction of P.
> >>>>
> >>>> (b) The direct execution of P(P) does reach its "ret"
> >>>> instruction.
> >>>>
> >>>> The above two are proven to be verified facts entirely on the
> >>>> basis of the semantics of the x86 language.
> >>>>
> >>>> A halt decider must compute the mapping from its inputs to an
> >>>> accept or reject state on the basis of the actual behavior that
> >>>> is actually specified by these inputs.
> >>>>
> >>>> P(P) is provably not the actual behavior of the actual input.
> >>>>
> >>>>
> >>>>
> >>>> void P(u32 x)
> >>>> {
> >>>> if (H(x, x))
> >>>> HERE: goto HERE;
> >>>> return;
> >>>> }
> >>>>
> >>>> int main()
> >>>> {
> >>>> Output("Input_Halts = ", H1((u32)P, (u32)P));
> >>>> }
> >>>>
> >>>> _P()
> >>>> [0000163a](01) 55 push ebp
> >>>> [0000163b](02) 8bec mov ebp,esp
> >>>> [0000163d](03) 8b4508 mov eax,[ebp+08]
> >>>> [00001640](01) 50 push eax
> >>>> [00001641](03) 8b4d08 mov ecx,[ebp+08]
> >>>> [00001644](01) 51 push ecx
> >>>> [00001645](05) e8f0fdffff call 0000143a // call H
> >>>> [0000164a](03) 83c408 add esp,+08
> >>>> [0000164d](02) 85c0 test eax,eax
> >>>> [0000164f](02) 7402 jz 00001653
> >>>> [00001651](02) ebfe jmp 00001651
> >>>> [00001653](01) 5d pop ebp
> >>>> [00001654](01) c3 ret
> >>>> Size in bytes:(0027) [00001654]
> >>>>
> >>>> _main()
> >>>> [0000165a](01) 55 push ebp
> >>>> [0000165b](02) 8bec mov ebp,esp
> >>>> [0000165d](05) 683a160000 push 0000163a // push P
> >>>> [00001662](05) 683a160000 push 0000163a // push P
> >>>> [00001667](05) e8cef9ffff call 0000103a // call H1
> >>>> [0000166c](03) 83c408 add esp,+08
> >>>> [0000166f](01) 50 push eax // push return
> >>>> value [00001670](05) 689b040000 push 0000049b //
> >>>> "Input_Halts = " [00001675](05) e870eeffff call 000004ea
> >>>> // call Output [0000167a](03) 83c408 add esp,+08
> >>>> [0000167d](02) 33c0 xor eax,eax
> >>>> [0000167f](01) 5d pop ebp
> >>>> [00001680](01) c3 ret
> >>>> Size in bytes:(0039) [00001680]
> >>>>
> >>>> machine stack stack machine assembly
> >>>> address address data code language
> >>>> ======== ======== ======== ========= ============> >>>> [0000165a][001026a9][00000000] 55 push ebp
> >>>> [0000165b][001026a9][00000000] 8bec mov ebp,esp
> >>>> [0000165d][001026a5][0000163a] 683a160000 push 0000163a // push P
> >>>> [00001662][001026a1][0000163a] 683a160000 push 0000163a // push P
> >>>> [00001667][0010269d][0000166c] e8cef9ffff call 0000103a // call
> >>>> H1
> >>>>
> >>>> H1: Begin Simulation Execution Trace Stored at:21275d
> >>>> Address_of_H1:103a
> >>>> [0000163a][00212749][0021274d] 55 push ebp
> >>>> [0000163b][00212749][0021274d] 8bec mov ebp,esp
> >>>> [0000163d][00212749][0021274d] 8b4508 mov eax,[ebp+08]
> >>>> [00001640][00212745][0000163a] 50 push eax // push P
> >>>> [00001641][00212745][0000163a] 8b4d08 mov ecx,[ebp+08]
> >>>> [00001644][00212741][0000163a] 51 push ecx // push P
> >>>> [00001645][0021273d][0000164a] e8f0fdffff call 0000143a // call H
> >>>>
> >>>> H: Begin Simulation Execution Trace Stored at:2285c5
> >>>> Address_of_H:143a
> >>>> [0000163a][002285b1][002285b5] 55 push ebp
> >>>> [0000163b][002285b1][002285b5] 8bec mov ebp,esp
> >>>> [0000163d][002285b1][002285b5] 8b4508 mov eax,[ebp+08]
> >>>> [00001640][002285ad][0000163a] 50 push eax // push P
> >>>> [00001641][002285ad][0000163a] 8b4d08 mov ecx,[ebp+08]
> >>>> [00001644][002285a9][0000163a] 51 push ecx // push P
> >>>> [00001645][002285a5][0000164a] e8f0fdffff call 0000143a // call H
> >>>> H: Infinitely Recursive Simulation Detected Simulation Stopped
> >>>>
> >>>> [0000164a][00212749][0021274d] 83c408 add esp,+08
> >>>> [0000164d][00212749][0021274d] 85c0 test eax,eax
> >>>> [0000164f][00212749][0021274d] 7402 jz 00001653
> >>>> [00001653][0021274d][0000111e] 5d pop ebp
> >>>> [00001654][00212751][0000163a] c3 ret
> >>>> H1: End Simulation Input Terminated Normally
> >>>>
> >>>> [0000166c][001026a9][00000000] 83c408 add esp,+08
> >>>> [0000166f][001026a5][00000001] 50 push eax // return
> >>>> value [00001670][001026a1][0000049b] 689b040000 push 0000049b //
> >>>> "Input_Halts = " [00001675][001026a1][0000049b] e870eeffff call
> >>>> 000004ea // call Output Input_Halts = 1
> >>>> [0000167a][001026a9][00000000] 83c408 add esp,+08
> >>>> [0000167d][001026a9][00000000] 33c0 xor eax,eax
> >>>> [0000167f][001026ad][00100000] 5d pop ebp
> >>>> [00001680][001026b1][00000004] c3 ret
> >>>> Number of Instructions Executed(409590) == 6113 Pages
> >>>
> >>> Why the new H/H1 dichotomy? Are you finally admitting that the
> >>> decider that main() calls is different to the decider that P would
> >>> call if you weren't erroneously aborting the simulation?
> >>>
> >>> /Flibble
> >>>
> >>
> >> The above example proves the following:
> >>
> >> (a) The complete and correct x86 emulation of the input to H(P,P)
> >> by H never reaches the "ret" instruction of P.
> >>
> >> (b) The direct execution of P(P) does reach its "ret" instruction.
> >>
> >
> > Then H returned the wrong answer. See [Strachey, 1965].
> >
> > /Flibble
> >
>
> So your rebuttals simply ignore that I proved you are wrong?
>
> // rec routine P
> // §L :if T[P] go to L
> // Return §
> // https://academic.oup.com/comjnl/article/7/4/313/354243
> void Strachey_P()
> {
> L:if (T(Strachey_P))
> goto L;
> return;
> }
>
> int main()
> {
> Output("Input_Halts = ", T(Strachey_P));
> }
>
> _Strachey_P()
> [000015b2](01) 55 push ebp
> [000015b3](02) 8bec mov ebp,esp
> [000015b5](05) 68b2150000 push 000015b2 // push Strachey_P
> [000015ba](05) e813fdffff call 000012d2 // call T
> [000015bf](03) 83c404 add esp,+04
> [000015c2](02) 85c0 test eax,eax
> [000015c4](02) 7402 jz 000015c8
> [000015c6](02) ebed jmp 000015b5
> [000015c8](01) 5d pop ebp
> [000015c9](01) c3 ret
> Size in bytes:(0024) [000015c9]
>
> _main()
> [000015d2](01) 55 push ebp
> [000015d3](02) 8bec mov ebp,esp
> [000015d5](05) 68b2150000 push 000015b2 // push Strachey_P
> [000015da](05) e8f3fcffff call 000012d2 // call T
> [000015df](03) 83c404 add esp,+04
> [000015e2](01) 50 push eax
> [000015e3](05) 6833040000 push 00000433
> [000015e8](05) e895eeffff call 00000482
> [000015ed](03) 83c408 add esp,+08
> [000015f0](02) 33c0 xor eax,eax
> [000015f2](01) 5d pop ebp
> [000015f3](01) c3 ret
> Size in bytes:(0034) [000015f3]
>
> machine stack stack machine assembly
> address address data code language
> ======== ======== ======== ========= ============> [000015d2][001025c6][00000000] 55 push ebp
> [000015d3][001025c6][00000000] 8bec mov ebp,esp
> [000015d5][001025c2][000015b2] 68b2150000 push 000015b2 // push
> Strachey_P [000015da][001025be][000015df] e8f3fcffff call 000012d2 //
> call T
>
> Begin Simulation Execution Trace Stored at:21267a
> Address_of_T:12d2
> [000015b2][0021266a][0021266e] 55 push ebp
> [000015b3][0021266a][0021266e] 8bec mov ebp,esp
> [000015b5][00212666][000015b2] 68b2150000 push 000015b2 // push
> Strachey_P [000015ba][00212662][000015bf] e813fdffff call 000012d2 //
> call T Infinitely Recursive Simulation Detected Simulation Stopped
>
> T knows its own machine address and on this basis it can easily
> examine its stored execution_trace of Strachey_P (see above) to
> determine: (a) Strachey_P is calling T with the same arguments that T
> was called with. (b) No instructions in Strachey_P could possibly
> escape this otherwise infinitely recursive emulation.
> (c) T aborts its emulation of Strachey_P before its call to T is
> emulated.
>
> [000015df][001025c6][00000000] 83c404 add esp,+04
> [000015e2][001025c2][00000000] 50 push eax
> [000015e3][001025be][00000433] 6833040000 push 00000433
> [000015e8][001025be][00000433] e895eeffff call 00000482
> Input_Halts = 0
> [000015ed][001025c6][00000000] 83c408 add esp,+08
> [000015f0][001025c6][00000000] 33c0 xor eax,eax
> [000015f2][001025ca][00100000] 5d pop ebp
> [000015f3][001025ce][00000004] c3 ret
> Number of Instructions Executed(528) == 8 Pages

Click here to read the complete article

Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<hrednRmsHZMNmyf_nZ2dnUU7_8zNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35034&group=comp.theory#35034

  copy link   Newsgroups: comp.theory sci.logic sci.math
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 27 Jun 2022 14:35:43 -0500
Date: Mon, 27 Jun 2022 14:35:42 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
Content-Language: en-US
Newsgroups: comp.theory,sci.logic,sci.math
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com>
<j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com>
<qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com>
<YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com>
<f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com>
<q4CdnWm9zL2KbST_nZ2dnUU7_8zNnZ2d@giganews.com>
<9f0c8dcb-ae3a-47bf-9093-4e4d9377dc47n@googlegroups.com>
<68ednUyP7tp6ZCT_nZ2dnUU7_8zNnZ2d@giganews.com>
<995fecc1-7fc4-4b40-8d68-fd74df13efefn@googlegroups.com>
<s7ednVfn1vRNYyT_nZ2dnUU7_83NnZ2d@giganews.com>
<b9d6501d-9279-4862-b727-893b042022ben@googlegroups.com>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <b9d6501d-9279-4862-b727-893b042022ben@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <hrednRmsHZMNmyf_nZ2dnUU7_8zNnZ2d@giganews.com>
Lines: 271
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-fQHiOBksyKA1jEzccfKZ+pZaA+T7CZW8VI7c8O9x9j9ADOzM+q0tSCzYlYQYZxiM7E0PmyzlZPEOOiK!CPb8tueHX+eNU7lpxm1JhQhFPxKoWEsaRhksTYk7MIwk4NQe/STrfAW6vK3yqZ9DsPJJKy0VBdXz
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 15823
 by: olcott - Mon, 27 Jun 2022 19:35 UTC

On 6/27/2022 2:13 PM, Dennis Bush wrote:
> On Monday, June 27, 2022 at 3:02:47 PM UTC-4, olcott wrote:
>> On 6/27/2022 1:51 PM, Dennis Bush wrote:
>>> On Monday, June 27, 2022 at 2:41:50 PM UTC-4, olcott wrote:
>>>> On 6/27/2022 1:08 PM, Dennis Bush wrote:
>>>>> On Monday, June 27, 2022 at 1:59:58 PM UTC-4, olcott wrote:
>>>>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
>>>>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
>>>>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
>>>>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
>>>>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
>>>>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
>>>>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>>>> *This is the outline of the complete refutation*
>>>>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
>>>>>>>>>>>>>>>> never reaches the "ret" instruction of P.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
>>>>>>>>>>>>>>>> the semantics of the x86 language.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
>>>>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> H does not perform this mapping.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> void P(u32 x)
>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>> if (H(x, x))
>>>>>>>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>>>>>>>> return;
>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>> P(P);
>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> _P()
>>>>>>>>>>>>>>>> [000011f0](01) 55 push ebp
>>>>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
>>>>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>> [000011f6](01) 50 push eax
>>>>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>> [000011fa](01) 51 push ecx
>>>>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
>>>>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
>>>>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
>>>>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
>>>>>>>>>>>>>>>> [00001209](01) 5d pop ebp
>>>>>>>>>>>>>>>> [0000120a](01) c3 ret
>>>>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> _main()
>>>>>>>>>>>>>>>> [00001210](01) 55 push ebp
>>>>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
>>>>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
>>>>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
>>>>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
>>>>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
>>>>>>>>>>>>>>>> [00001222](01) 5d pop ebp
>>>>>>>>>>>>>>>> [00001223](01) c3 ret
>>>>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> machine stack stack machine assembly
>>>>>>>>>>>>>>>> address address data code language
>>>>>>>>>>>>>>>> ======== ======== ======== ========= =============
>>>>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
>>>>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
>>>>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
>>>>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
>>>>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
>>>>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
>>>>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
>>>>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
>>>>>>>>>>>>>>>> Address_of_H:1020
>>>>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
>>>>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
>>>>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
>>>>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
>>>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
>>>>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
>>>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
>>>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
>>>>>>>>>>>>>>>> recursive emulation.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> FALSE. P contains these instructions:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
>>>>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
>>>>>>>>>>>>>>> goto END_OF_CODE;
>>>>>>>>>>>>>>> return 0; // Does not halt
>>>>>>>>>>>>>>> END_OF_CODE:
>>>>>>>>>>>>>>> return 1; // Input has normally terminated
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
>>>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
>>>>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
>>>>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
>>>>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
>>>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
>>>>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
>>>>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
>>>>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
>>>>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
>>>>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
>>>>>>>>>>>>>> input never reaches the the "ret" instruction of P.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Repeating your original point.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Again, repeating your original point.
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>>> Therefore H(P,P)==0 is correct.
>>>>>>>>>>>>>
>>>>>>>>>>>>> And again, repeating your original point.
>>>>>>>>>>>>>
>>>>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
>>>>>>>>>>>>>
>>>>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
>>>>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
>>>>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
>>>>>>>>>>>> never reach the final state "ret" instruction of this input.
>>>>>>>>>>>
>>>>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>> First of all I am not talking about UTM's.
>>>>>>>>>> I am talking about x86 emulation.
>>>>>>>>>> Try to encode what you mean, here is my guess:
>>>>>>>>>>
>>>>>>>>>> void P(u32 x)
>>>>>>>>>> {
>>>>>>>>>> if (emulate_x86(x, x))
>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>> return;
>>>>>>>>>> }
>>>>>>>>>>
>>>>>>>>>> int main()
>>>>>>>>>> {
>>>>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
>>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
>>>>>>>>>
>>>>>>>>> void UTM(u32 x, u32 y)
>>>>>>>>> {
>>>>>>>>> x(y)
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
>>>>>>>>>
>>>>>>>> A simulating halt decider correctly simulates its input until it
>>>>>>>> correctly determines that this simulated input would never reach its
>>>>>>>> final state.
>>>>>>>
>>>>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
>>>>>>>
>>>>>> The semantics of the x86 language conclusively proves that H(P,P)
>>>>>> correctly determines/predicts that its complete and correct x86
>>>>>> emulation of its input would never reach the "ret" instruction of P.
>>>>>
>>>>> As previously stated, this is nonsense. Failure to explain *in detail* why the below is wrong will be taken as an admission that it is correct.
>>>>>
>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>>>
>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>>>> I NEVER SAID that H does a complete and correct simulation of its input.
>>>
>>> Yes you did:
>>>
>>>> a) The complete and correct x86 emulation of the input to H(P,P) by H never reaches the "ret" instruction of P.
>>>
>> This does not say that H does a complete emulation.
>> A simulating halt decider correctly simulates its input until it
>> correctly determines that this simulated input would never reach its
>> final state.
>
> Which in the case of H(P,P) it doesn't since the correctly simulated input i.e. UTM(P,P) halts. H gets the wrong answer because it aborts too soon.
>
>> _Infinite_Loop()
>> [000015b8](01) 55 push ebp
>> [000015b9](02) 8bec mov ebp,esp
>> [000015bb](02) ebfe jmp 000015bb
>> [000015bd](01) 5d pop ebp
>> [000015be](01) c3 ret
>> Size in bytes:(0007) [000015be]
>>
>> The complete and correct x86 emulation of the input to H0(Infinite_Loop)
>> by H0 never reaches the "ret" instruction of Infinite_Loop.
>
> If H0 *actually* does a complete and correct emulation, then yes.


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs [V2]

<yLKdnasB19rvmif_nZ2dnUU7_8zNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35035&group=comp.theory#35035

  copy link   Newsgroups: comp.theory sci.logic sci.math
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 27 Jun 2022 14:39:30 -0500
Date: Mon, 27 Jun 2022 14:39:28 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs [V2]
Content-Language: en-US
Newsgroups: comp.theory,sci.logic,sci.math
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<kJKdnTmzKJCBACT_nZ2dnUU7_8zNnZ2d@giganews.com>
<20220627192020.00005278@reddwarf.jmc>
<O8OdnerVE-Y_ZyT_nZ2dnUU7_8zNnZ2d@giganews.com>
<20220627195334.0000091d@reddwarf.jmc>
<s7ednVbn1vReYiT_nZ2dnUU7_81g4p2d@giganews.com>
<20220627201942.00003770@reddwarf.jmc>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <20220627201942.00003770@reddwarf.jmc>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Message-ID: <yLKdnasB19rvmif_nZ2dnUU7_8zNnZ2d@giganews.com>
Lines: 247
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-7I3vri/m29HjnJTCQ7T+gEjCxLFLRhDJPEaXHxTurIcZa4J8gbvS9WBtuccn1WoKfuyuLUWVx9hudHe!AM6NxIEeb7hjZxH1DRMqtaQB0XVjh/BgJbOqLdxI8pzD3ksxLuSaOwQhtD4gZnMo4eDDKuIRlxdU
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 11831
 by: olcott - Mon, 27 Jun 2022 19:39 UTC

On 6/27/2022 2:19 PM, Mr Flibble wrote:
> On Mon, 27 Jun 2022 14:06:42 -0500
> olcott <NoOne@NoWhere.com> wrote:
>
>> On 6/27/2022 1:53 PM, Mr Flibble wrote:
>>> On Mon, 27 Jun 2022 13:44:49 -0500
>>> olcott <NoOne@NoWhere.com> wrote:
>>>
>>>> On 6/27/2022 1:20 PM, Mr Flibble wrote:
>>>>> On Mon, 27 Jun 2022 07:05:46 -0500
>>>>> olcott <NoOne@NoWhere.com> wrote:
>>>>>
>>>>>> *This is the outline of the complete refutation*
>>>>>> *of the only rebuttal that anyone has left*
>>>>>>
>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P)
>>>>>> by H never reaches the "ret" instruction of P.
>>>>>>
>>>>>> (b) The direct execution of P(P) does reach its "ret"
>>>>>> instruction.
>>>>>>
>>>>>> The above two are proven to be verified facts entirely on the
>>>>>> basis of the semantics of the x86 language.
>>>>>>
>>>>>> A halt decider must compute the mapping from its inputs to an
>>>>>> accept or reject state on the basis of the actual behavior that
>>>>>> is actually specified by these inputs.
>>>>>>
>>>>>> P(P) is provably not the actual behavior of the actual input.
>>>>>>
>>>>>>
>>>>>>
>>>>>> void P(u32 x)
>>>>>> {
>>>>>> if (H(x, x))
>>>>>> HERE: goto HERE;
>>>>>> return;
>>>>>> }
>>>>>>
>>>>>> int main()
>>>>>> {
>>>>>> Output("Input_Halts = ", H1((u32)P, (u32)P));
>>>>>> }
>>>>>>
>>>>>> _P()
>>>>>> [0000163a](01) 55 push ebp
>>>>>> [0000163b](02) 8bec mov ebp,esp
>>>>>> [0000163d](03) 8b4508 mov eax,[ebp+08]
>>>>>> [00001640](01) 50 push eax
>>>>>> [00001641](03) 8b4d08 mov ecx,[ebp+08]
>>>>>> [00001644](01) 51 push ecx
>>>>>> [00001645](05) e8f0fdffff call 0000143a // call H
>>>>>> [0000164a](03) 83c408 add esp,+08
>>>>>> [0000164d](02) 85c0 test eax,eax
>>>>>> [0000164f](02) 7402 jz 00001653
>>>>>> [00001651](02) ebfe jmp 00001651
>>>>>> [00001653](01) 5d pop ebp
>>>>>> [00001654](01) c3 ret
>>>>>> Size in bytes:(0027) [00001654]
>>>>>>
>>>>>> _main()
>>>>>> [0000165a](01) 55 push ebp
>>>>>> [0000165b](02) 8bec mov ebp,esp
>>>>>> [0000165d](05) 683a160000 push 0000163a // push P
>>>>>> [00001662](05) 683a160000 push 0000163a // push P
>>>>>> [00001667](05) e8cef9ffff call 0000103a // call H1
>>>>>> [0000166c](03) 83c408 add esp,+08
>>>>>> [0000166f](01) 50 push eax // push return
>>>>>> value [00001670](05) 689b040000 push 0000049b //
>>>>>> "Input_Halts = " [00001675](05) e870eeffff call 000004ea
>>>>>> // call Output [0000167a](03) 83c408 add esp,+08
>>>>>> [0000167d](02) 33c0 xor eax,eax
>>>>>> [0000167f](01) 5d pop ebp
>>>>>> [00001680](01) c3 ret
>>>>>> Size in bytes:(0039) [00001680]
>>>>>>
>>>>>> machine stack stack machine assembly
>>>>>> address address data code language
>>>>>> ======== ======== ======== ========= =============
>>>>>> [0000165a][001026a9][00000000] 55 push ebp
>>>>>> [0000165b][001026a9][00000000] 8bec mov ebp,esp
>>>>>> [0000165d][001026a5][0000163a] 683a160000 push 0000163a // push P
>>>>>> [00001662][001026a1][0000163a] 683a160000 push 0000163a // push P
>>>>>> [00001667][0010269d][0000166c] e8cef9ffff call 0000103a // call
>>>>>> H1
>>>>>>
>>>>>> H1: Begin Simulation Execution Trace Stored at:21275d
>>>>>> Address_of_H1:103a
>>>>>> [0000163a][00212749][0021274d] 55 push ebp
>>>>>> [0000163b][00212749][0021274d] 8bec mov ebp,esp
>>>>>> [0000163d][00212749][0021274d] 8b4508 mov eax,[ebp+08]
>>>>>> [00001640][00212745][0000163a] 50 push eax // push P
>>>>>> [00001641][00212745][0000163a] 8b4d08 mov ecx,[ebp+08]
>>>>>> [00001644][00212741][0000163a] 51 push ecx // push P
>>>>>> [00001645][0021273d][0000164a] e8f0fdffff call 0000143a // call H
>>>>>>
>>>>>> H: Begin Simulation Execution Trace Stored at:2285c5
>>>>>> Address_of_H:143a
>>>>>> [0000163a][002285b1][002285b5] 55 push ebp
>>>>>> [0000163b][002285b1][002285b5] 8bec mov ebp,esp
>>>>>> [0000163d][002285b1][002285b5] 8b4508 mov eax,[ebp+08]
>>>>>> [00001640][002285ad][0000163a] 50 push eax // push P
>>>>>> [00001641][002285ad][0000163a] 8b4d08 mov ecx,[ebp+08]
>>>>>> [00001644][002285a9][0000163a] 51 push ecx // push P
>>>>>> [00001645][002285a5][0000164a] e8f0fdffff call 0000143a // call H
>>>>>> H: Infinitely Recursive Simulation Detected Simulation Stopped
>>>>>>
>>>>>> [0000164a][00212749][0021274d] 83c408 add esp,+08
>>>>>> [0000164d][00212749][0021274d] 85c0 test eax,eax
>>>>>> [0000164f][00212749][0021274d] 7402 jz 00001653
>>>>>> [00001653][0021274d][0000111e] 5d pop ebp
>>>>>> [00001654][00212751][0000163a] c3 ret
>>>>>> H1: End Simulation Input Terminated Normally
>>>>>>
>>>>>> [0000166c][001026a9][00000000] 83c408 add esp,+08
>>>>>> [0000166f][001026a5][00000001] 50 push eax // return
>>>>>> value [00001670][001026a1][0000049b] 689b040000 push 0000049b //
>>>>>> "Input_Halts = " [00001675][001026a1][0000049b] e870eeffff call
>>>>>> 000004ea // call Output Input_Halts = 1
>>>>>> [0000167a][001026a9][00000000] 83c408 add esp,+08
>>>>>> [0000167d][001026a9][00000000] 33c0 xor eax,eax
>>>>>> [0000167f][001026ad][00100000] 5d pop ebp
>>>>>> [00001680][001026b1][00000004] c3 ret
>>>>>> Number of Instructions Executed(409590) == 6113 Pages
>>>>>
>>>>> Why the new H/H1 dichotomy? Are you finally admitting that the
>>>>> decider that main() calls is different to the decider that P would
>>>>> call if you weren't erroneously aborting the simulation?
>>>>>
>>>>> /Flibble
>>>>>
>>>>
>>>> The above example proves the following:
>>>>
>>>> (a) The complete and correct x86 emulation of the input to H(P,P)
>>>> by H never reaches the "ret" instruction of P.
>>>>
>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
>>>>
>>>
>>> Then H returned the wrong answer. See [Strachey, 1965].
>>>
>>> /Flibble
>>>
>>
>> So your rebuttals simply ignore that I proved you are wrong?
>>
>> // rec routine P
>> // §L :if T[P] go to L
>> // Return §
>> // https://academic.oup.com/comjnl/article/7/4/313/354243
>> void Strachey_P()
>> {
>> L:if (T(Strachey_P))
>> goto L;
>> return;
>> }
>>
>> int main()
>> {
>> Output("Input_Halts = ", T(Strachey_P));
>> }
>>
>> _Strachey_P()
>> [000015b2](01) 55 push ebp
>> [000015b3](02) 8bec mov ebp,esp
>> [000015b5](05) 68b2150000 push 000015b2 // push Strachey_P
>> [000015ba](05) e813fdffff call 000012d2 // call T
>> [000015bf](03) 83c404 add esp,+04
>> [000015c2](02) 85c0 test eax,eax
>> [000015c4](02) 7402 jz 000015c8
>> [000015c6](02) ebed jmp 000015b5
>> [000015c8](01) 5d pop ebp
>> [000015c9](01) c3 ret
>> Size in bytes:(0024) [000015c9]
>>
>> _main()
>> [000015d2](01) 55 push ebp
>> [000015d3](02) 8bec mov ebp,esp
>> [000015d5](05) 68b2150000 push 000015b2 // push Strachey_P
>> [000015da](05) e8f3fcffff call 000012d2 // call T
>> [000015df](03) 83c404 add esp,+04
>> [000015e2](01) 50 push eax
>> [000015e3](05) 6833040000 push 00000433
>> [000015e8](05) e895eeffff call 00000482
>> [000015ed](03) 83c408 add esp,+08
>> [000015f0](02) 33c0 xor eax,eax
>> [000015f2](01) 5d pop ebp
>> [000015f3](01) c3 ret
>> Size in bytes:(0034) [000015f3]
>>
>> machine stack stack machine assembly
>> address address data code language
>> ======== ======== ======== ========= =============
>> [000015d2][001025c6][00000000] 55 push ebp
>> [000015d3][001025c6][00000000] 8bec mov ebp,esp
>> [000015d5][001025c2][000015b2] 68b2150000 push 000015b2 // push
>> Strachey_P [000015da][001025be][000015df] e8f3fcffff call 000012d2 //
>> call T
>>
>> Begin Simulation Execution Trace Stored at:21267a
>> Address_of_T:12d2
>> [000015b2][0021266a][0021266e] 55 push ebp
>> [000015b3][0021266a][0021266e] 8bec mov ebp,esp
>> [000015b5][00212666][000015b2] 68b2150000 push 000015b2 // push
>> Strachey_P [000015ba][00212662][000015bf] e813fdffff call 000012d2 //
>> call T Infinitely Recursive Simulation Detected Simulation Stopped
>>
>> T knows its own machine address and on this basis it can easily
>> examine its stored execution_trace of Strachey_P (see above) to
>> determine: (a) Strachey_P is calling T with the same arguments that T
>> was called with. (b) No instructions in Strachey_P could possibly
>> escape this otherwise infinitely recursive emulation.
>> (c) T aborts its emulation of Strachey_P before its call to T is
>> emulated.
>>
>> [000015df][001025c6][00000000] 83c404 add esp,+04
>> [000015e2][001025c2][00000000] 50 push eax
>> [000015e3][001025be][00000433] 6833040000 push 00000433
>> [000015e8][001025be][00000433] e895eeffff call 00000482
>> Input_Halts = 0
>> [000015ed][001025c6][00000000] 83c408 add esp,+08
>> [000015f0][001025c6][00000000] 33c0 xor eax,eax
>> [000015f2][001025ca][00100000] 5d pop ebp
>> [000015f3][001025ce][00000004] c3 ret
>> Number of Instructions Executed(528) == 8 Pages
>
> There is no recursion in [Strachey, 1965]; a mistake you keep making
> again and again and again.
>
> /Flibble
>
>


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<ccce4f12-08f3-4a18-9211-bc3fa58eafcfn@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35036&group=comp.theory#35036

  copy link   Newsgroups: comp.theory
X-Received: by 2002:a05:600c:1e18:b0:3a0:4865:3784 with SMTP id ay24-20020a05600c1e1800b003a048653784mr10299344wmb.139.1656358781529;
Mon, 27 Jun 2022 12:39:41 -0700 (PDT)
X-Received: by 2002:a25:b3cb:0:b0:64f:cfbf:ecdf with SMTP id
x11-20020a25b3cb000000b0064fcfbfecdfmr15268044ybf.84.1656358780908; Mon, 27
Jun 2022 12:39:40 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.128.87.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.theory
Date: Mon, 27 Jun 2022 12:39:40 -0700 (PDT)
In-Reply-To: <hrednRmsHZMNmyf_nZ2dnUU7_8zNnZ2d@giganews.com>
Injection-Info: google-groups.googlegroups.com; posting-host=71.168.165.242; posting-account=ejFcQgoAAACAt5i0VbkATkR2ACWdgADD
NNTP-Posting-Host: 71.168.165.242
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com> <j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com> <qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com> <YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com> <f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com> <q4CdnWm9zL2KbST_nZ2dnUU7_8zNnZ2d@giganews.com>
<9f0c8dcb-ae3a-47bf-9093-4e4d9377dc47n@googlegroups.com> <68ednUyP7tp6ZCT_nZ2dnUU7_8zNnZ2d@giganews.com>
<995fecc1-7fc4-4b40-8d68-fd74df13efefn@googlegroups.com> <s7ednVfn1vRNYyT_nZ2dnUU7_83NnZ2d@giganews.com>
<b9d6501d-9279-4862-b727-893b042022ben@googlegroups.com> <hrednRmsHZMNmyf_nZ2dnUU7_8zNnZ2d@giganews.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <ccce4f12-08f3-4a18-9211-bc3fa58eafcfn@googlegroups.com>
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
From: dbush.mo...@gmail.com (Dennis Bush)
Injection-Date: Mon, 27 Jun 2022 19:39:41 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Dennis Bush - Mon, 27 Jun 2022 19:39 UTC

On Monday, June 27, 2022 at 3:35:53 PM UTC-4, olcott wrote:
> On 6/27/2022 2:13 PM, Dennis Bush wrote:
> > On Monday, June 27, 2022 at 3:02:47 PM UTC-4, olcott wrote:
> >> On 6/27/2022 1:51 PM, Dennis Bush wrote:
> >>> On Monday, June 27, 2022 at 2:41:50 PM UTC-4, olcott wrote:
> >>>> On 6/27/2022 1:08 PM, Dennis Bush wrote:
> >>>>> On Monday, June 27, 2022 at 1:59:58 PM UTC-4, olcott wrote:
> >>>>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
> >>>>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
> >>>>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
> >>>>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
> >>>>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
> >>>>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
> >>>>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
> >>>>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
> >>>>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>>>> *This is the outline of the complete refutation*
> >>>>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
> >>>>>>>>>>>>>>>> never reaches the "ret" instruction of P.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
> >>>>>>>>>>>>>>>> the semantics of the x86 language.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P).. The halting problem says that H MUST implement the following mapping (i.e.. the halting function):
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
> >>>>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> H does not perform this mapping.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> void P(u32 x)
> >>>>>>>>>>>>>>>> {
> >>>>>>>>>>>>>>>> if (H(x, x))
> >>>>>>>>>>>>>>>> HERE: goto HERE;
> >>>>>>>>>>>>>>>> return;
> >>>>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> int main()
> >>>>>>>>>>>>>>>> {
> >>>>>>>>>>>>>>>> P(P);
> >>>>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> _P()
> >>>>>>>>>>>>>>>> [000011f0](01) 55 push ebp
> >>>>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>>> [000011f6](01) 50 push eax
> >>>>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>>> [000011fa](01) 51 push ecx
> >>>>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
> >>>>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
> >>>>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
> >>>>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
> >>>>>>>>>>>>>>>> [00001209](01) 5d pop ebp
> >>>>>>>>>>>>>>>> [0000120a](01) c3 ret
> >>>>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> _main()
> >>>>>>>>>>>>>>>> [00001210](01) 55 push ebp
> >>>>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
> >>>>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
> >>>>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
> >>>>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
> >>>>>>>>>>>>>>>> [00001222](01) 5d pop ebp
> >>>>>>>>>>>>>>>> [00001223](01) c3 ret
> >>>>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> machine stack stack machine assembly
> >>>>>>>>>>>>>>>> address address data code language
> >>>>>>>>>>>>>>>> ======== ======== ======== ========= =============
> >>>>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
> >>>>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
> >>>>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
> >>>>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
> >>>>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
> >>>>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
> >>>>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
> >>>>>>>>>>>>>>>> Address_of_H:1020
> >>>>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
> >>>>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
> >>>>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
> >>>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
> >>>>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
> >>>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
> >>>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
> >>>>>>>>>>>>>>>> recursive emulation.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> FALSE. P contains these instructions:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
> >>>>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
> >>>>>>>>>>>>>>> goto END_OF_CODE;
> >>>>>>>>>>>>>>> return 0; // Does not halt
> >>>>>>>>>>>>>>> END_OF_CODE:
> >>>>>>>>>>>>>>> return 1; // Input has normally terminated
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
> >>>>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
> >>>>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
> >>>>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
> >>>>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
> >>>>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
> >>>>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
> >>>>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
> >>>>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
> >>>>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
> >>>>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
> >>>>>>>>>>>>>> input never reaches the the "ret" instruction of P.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Repeating your original point.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Again, repeating your original point.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
> >>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>>>> Therefore H(P,P)==0 is correct.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> And again, repeating your original point.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
> >>>>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
> >>>>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
> >>>>>>>>>>>> never reach the final state "ret" instruction of this input.
> >>>>>>>>>>>
> >>>>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>>>> First of all I am not talking about UTM's.
> >>>>>>>>>> I am talking about x86 emulation.
> >>>>>>>>>> Try to encode what you mean, here is my guess:
> >>>>>>>>>>
> >>>>>>>>>> void P(u32 x)
> >>>>>>>>>> {
> >>>>>>>>>> if (emulate_x86(x, x))
> >>>>>>>>>> HERE: goto HERE;
> >>>>>>>>>> return;
> >>>>>>>>>> }
> >>>>>>>>>>
> >>>>>>>>>> int main()
> >>>>>>>>>> {
> >>>>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
> >>>>>>>>>> }
> >>>>>>>>>
> >>>>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
> >>>>>>>>>
> >>>>>>>>> void UTM(u32 x, u32 y)
> >>>>>>>>> {
> >>>>>>>>> x(y)
> >>>>>>>>> }
> >>>>>>>>>
> >>>>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
> >>>>>>>>>
> >>>>>>>> A simulating halt decider correctly simulates its input until it
> >>>>>>>> correctly determines that this simulated input would never reach its
> >>>>>>>> final state.
> >>>>>>>
> >>>>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
> >>>>>>>
> >>>>>> The semantics of the x86 language conclusively proves that H(P,P)
> >>>>>> correctly determines/predicts that its complete and correct x86
> >>>>>> emulation of its input would never reach the "ret" instruction of P.
> >>>>>
> >>>>> As previously stated, this is nonsense. Failure to explain *in detail* why the below is wrong will be taken as an admission that it is correct..
> >>>>>
> >>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> >>>>>
> >>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> >>>> I NEVER SAID that H does a complete and correct simulation of its input.
> >>>
> >>> Yes you did:
> >>>
> >>>> a) The complete and correct x86 emulation of the input to H(P,P) by H never reaches the "ret" instruction of P.
> >>>
> >> This does not say that H does a complete emulation.
> >> A simulating halt decider correctly simulates its input until it
> >> correctly determines that this simulated input would never reach its
> >> final state.
> >
> > Which in the case of H(P,P) it doesn't since the correctly simulated input i.e. UTM(P,P) halts. H gets the wrong answer because it aborts too soon..
> >
> >> _Infinite_Loop()
> >> [000015b8](01) 55 push ebp
> >> [000015b9](02) 8bec mov ebp,esp
> >> [000015bb](02) ebfe jmp 000015bb
> >> [000015bd](01) 5d pop ebp
> >> [000015be](01) c3 ret
> >> Size in bytes:(0007) [000015be]
> >>
> >> The complete and correct x86 emulation of the input to H0(Infinite_Loop)
> >> by H0 never reaches the "ret" instruction of Infinite_Loop.
> >
> > If H0 *actually* does a complete and correct emulation, then yes.
> void Infinite_Loop()
> {
> HERE: goto HERE;
> }
>
> You are not bright enough to tell that an infinite loop doesn't stop
> running?


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs [V2]

<20220627204259.00004ab8@reddwarf.jmc>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35037&group=comp.theory#35037

  copy link   Newsgroups: comp.theory sci.logic sci.math
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!peer02.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!fx06.ams4.POSTED!not-for-mail
From: flib...@reddwarf.jmc (Mr Flibble)
Newsgroups: comp.theory,sci.logic,sci.math
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs [V2]
Message-ID: <20220627204259.00004ab8@reddwarf.jmc>
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<kJKdnTmzKJCBACT_nZ2dnUU7_8zNnZ2d@giganews.com>
<20220627192020.00005278@reddwarf.jmc>
<O8OdnerVE-Y_ZyT_nZ2dnUU7_8zNnZ2d@giganews.com>
<20220627195334.0000091d@reddwarf.jmc>
<s7ednVbn1vReYiT_nZ2dnUU7_81g4p2d@giganews.com>
<20220627201942.00003770@reddwarf.jmc>
<yLKdnasB19rvmif_nZ2dnUU7_8zNnZ2d@giganews.com>
Organization: Jupiter Mining Corp
X-Newsreader: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-w64-mingw32)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Lines: 255
X-Complaints-To: abuse@eweka.nl
NNTP-Posting-Date: Mon, 27 Jun 2022 19:42:56 UTC
Date: Mon, 27 Jun 2022 20:42:59 +0100
X-Received-Bytes: 12197
 by: Mr Flibble - Mon, 27 Jun 2022 19:42 UTC

On Mon, 27 Jun 2022 14:39:28 -0500
olcott <NoOne@NoWhere.com> wrote:

> On 6/27/2022 2:19 PM, Mr Flibble wrote:
> > On Mon, 27 Jun 2022 14:06:42 -0500
> > olcott <NoOne@NoWhere.com> wrote:
> >
> >> On 6/27/2022 1:53 PM, Mr Flibble wrote:
> >>> On Mon, 27 Jun 2022 13:44:49 -0500
> >>> olcott <NoOne@NoWhere.com> wrote:
> >>>
> >>>> On 6/27/2022 1:20 PM, Mr Flibble wrote:
> >>>>> On Mon, 27 Jun 2022 07:05:46 -0500
> >>>>> olcott <NoOne@NoWhere.com> wrote:
> >>>>>
> >>>>>> *This is the outline of the complete refutation*
> >>>>>> *of the only rebuttal that anyone has left*
> >>>>>>
> >>>>>> (a) The complete and correct x86 emulation of the input to
> >>>>>> H(P,P) by H never reaches the "ret" instruction of P.
> >>>>>>
> >>>>>> (b) The direct execution of P(P) does reach its "ret"
> >>>>>> instruction.
> >>>>>>
> >>>>>> The above two are proven to be verified facts entirely on the
> >>>>>> basis of the semantics of the x86 language.
> >>>>>>
> >>>>>> A halt decider must compute the mapping from its inputs to an
> >>>>>> accept or reject state on the basis of the actual behavior that
> >>>>>> is actually specified by these inputs.
> >>>>>>
> >>>>>> P(P) is provably not the actual behavior of the actual input.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> void P(u32 x)
> >>>>>> {
> >>>>>> if (H(x, x))
> >>>>>> HERE: goto HERE;
> >>>>>> return;
> >>>>>> }
> >>>>>>
> >>>>>> int main()
> >>>>>> {
> >>>>>> Output("Input_Halts = ", H1((u32)P, (u32)P));
> >>>>>> }
> >>>>>>
> >>>>>> _P()
> >>>>>> [0000163a](01) 55 push ebp
> >>>>>> [0000163b](02) 8bec mov ebp,esp
> >>>>>> [0000163d](03) 8b4508 mov eax,[ebp+08]
> >>>>>> [00001640](01) 50 push eax
> >>>>>> [00001641](03) 8b4d08 mov ecx,[ebp+08]
> >>>>>> [00001644](01) 51 push ecx
> >>>>>> [00001645](05) e8f0fdffff call 0000143a // call H
> >>>>>> [0000164a](03) 83c408 add esp,+08
> >>>>>> [0000164d](02) 85c0 test eax,eax
> >>>>>> [0000164f](02) 7402 jz 00001653
> >>>>>> [00001651](02) ebfe jmp 00001651
> >>>>>> [00001653](01) 5d pop ebp
> >>>>>> [00001654](01) c3 ret
> >>>>>> Size in bytes:(0027) [00001654]
> >>>>>>
> >>>>>> _main()
> >>>>>> [0000165a](01) 55 push ebp
> >>>>>> [0000165b](02) 8bec mov ebp,esp
> >>>>>> [0000165d](05) 683a160000 push 0000163a // push P
> >>>>>> [00001662](05) 683a160000 push 0000163a // push P
> >>>>>> [00001667](05) e8cef9ffff call 0000103a // call H1
> >>>>>> [0000166c](03) 83c408 add esp,+08
> >>>>>> [0000166f](01) 50 push eax // push return
> >>>>>> value [00001670](05) 689b040000 push 0000049b //
> >>>>>> "Input_Halts = " [00001675](05) e870eeffff call 000004ea
> >>>>>> // call Output [0000167a](03) 83c408 add esp,+08
> >>>>>> [0000167d](02) 33c0 xor eax,eax
> >>>>>> [0000167f](01) 5d pop ebp
> >>>>>> [00001680](01) c3 ret
> >>>>>> Size in bytes:(0039) [00001680]
> >>>>>>
> >>>>>> machine stack stack machine assembly
> >>>>>> address address data code language
> >>>>>> ======== ======== ======== ========= ============> >>>>>> [0000165a][001026a9][00000000] 55 push ebp
> >>>>>> [0000165b][001026a9][00000000] 8bec mov ebp,esp
> >>>>>> [0000165d][001026a5][0000163a] 683a160000 push 0000163a //
> >>>>>> push P [00001662][001026a1][0000163a] 683a160000 push 0000163a
> >>>>>> // push P [00001667][0010269d][0000166c] e8cef9ffff call
> >>>>>> 0000103a // call H1
> >>>>>>
> >>>>>> H1: Begin Simulation Execution Trace Stored at:21275d
> >>>>>> Address_of_H1:103a
> >>>>>> [0000163a][00212749][0021274d] 55 push ebp
> >>>>>> [0000163b][00212749][0021274d] 8bec mov ebp,esp
> >>>>>> [0000163d][00212749][0021274d] 8b4508 mov eax,[ebp+08]
> >>>>>> [00001640][00212745][0000163a] 50 push eax //
> >>>>>> push P [00001641][00212745][0000163a] 8b4d08 mov
> >>>>>> ecx,[ebp+08] [00001644][00212741][0000163a] 51 push
> >>>>>> ecx // push P [00001645][0021273d][0000164a] e8f0fdffff
> >>>>>> call 0000143a // call H
> >>>>>>
> >>>>>> H: Begin Simulation Execution Trace Stored at:2285c5
> >>>>>> Address_of_H:143a
> >>>>>> [0000163a][002285b1][002285b5] 55 push ebp
> >>>>>> [0000163b][002285b1][002285b5] 8bec mov ebp,esp
> >>>>>> [0000163d][002285b1][002285b5] 8b4508 mov eax,[ebp+08]
> >>>>>> [00001640][002285ad][0000163a] 50 push eax //
> >>>>>> push P [00001641][002285ad][0000163a] 8b4d08 mov
> >>>>>> ecx,[ebp+08] [00001644][002285a9][0000163a] 51 push
> >>>>>> ecx // push P [00001645][002285a5][0000164a] e8f0fdffff
> >>>>>> call 0000143a // call H H: Infinitely Recursive Simulation
> >>>>>> Detected Simulation Stopped
> >>>>>>
> >>>>>> [0000164a][00212749][0021274d] 83c408 add esp,+08
> >>>>>> [0000164d][00212749][0021274d] 85c0 test eax,eax
> >>>>>> [0000164f][00212749][0021274d] 7402 jz 00001653
> >>>>>> [00001653][0021274d][0000111e] 5d pop ebp
> >>>>>> [00001654][00212751][0000163a] c3 ret
> >>>>>> H1: End Simulation Input Terminated Normally
> >>>>>>
> >>>>>> [0000166c][001026a9][00000000] 83c408 add esp,+08
> >>>>>> [0000166f][001026a5][00000001] 50 push eax //
> >>>>>> return value [00001670][001026a1][0000049b] 689b040000 push
> >>>>>> 0000049b // "Input_Halts = " [00001675][001026a1][0000049b]
> >>>>>> e870eeffff call 000004ea // call Output Input_Halts = 1
> >>>>>> [0000167a][001026a9][00000000] 83c408 add esp,+08
> >>>>>> [0000167d][001026a9][00000000] 33c0 xor eax,eax
> >>>>>> [0000167f][001026ad][00100000] 5d pop ebp
> >>>>>> [00001680][001026b1][00000004] c3 ret
> >>>>>> Number of Instructions Executed(409590) == 6113 Pages
> >>>>>
> >>>>> Why the new H/H1 dichotomy? Are you finally admitting that the
> >>>>> decider that main() calls is different to the decider that P
> >>>>> would call if you weren't erroneously aborting the simulation?
> >>>>>
> >>>>> /Flibble
> >>>>>
> >>>>
> >>>> The above example proves the following:
> >>>>
> >>>> (a) The complete and correct x86 emulation of the input to H(P,P)
> >>>> by H never reaches the "ret" instruction of P.
> >>>>
> >>>> (b) The direct execution of P(P) does reach its "ret"
> >>>> instruction.
> >>>
> >>> Then H returned the wrong answer. See [Strachey, 1965].
> >>>
> >>> /Flibble
> >>>
> >>
> >> So your rebuttals simply ignore that I proved you are wrong?
> >>
> >> // rec routine P
> >> // §L :if T[P] go to L
> >> // Return §
> >> // https://academic.oup.com/comjnl/article/7/4/313/354243
> >> void Strachey_P()
> >> {
> >> L:if (T(Strachey_P))
> >> goto L;
> >> return;
> >> }
> >>
> >> int main()
> >> {
> >> Output("Input_Halts = ", T(Strachey_P));
> >> }
> >>
> >> _Strachey_P()
> >> [000015b2](01) 55 push ebp
> >> [000015b3](02) 8bec mov ebp,esp
> >> [000015b5](05) 68b2150000 push 000015b2 // push Strachey_P
> >> [000015ba](05) e813fdffff call 000012d2 // call T
> >> [000015bf](03) 83c404 add esp,+04
> >> [000015c2](02) 85c0 test eax,eax
> >> [000015c4](02) 7402 jz 000015c8
> >> [000015c6](02) ebed jmp 000015b5
> >> [000015c8](01) 5d pop ebp
> >> [000015c9](01) c3 ret
> >> Size in bytes:(0024) [000015c9]
> >>
> >> _main()
> >> [000015d2](01) 55 push ebp
> >> [000015d3](02) 8bec mov ebp,esp
> >> [000015d5](05) 68b2150000 push 000015b2 // push Strachey_P
> >> [000015da](05) e8f3fcffff call 000012d2 // call T
> >> [000015df](03) 83c404 add esp,+04
> >> [000015e2](01) 50 push eax
> >> [000015e3](05) 6833040000 push 00000433
> >> [000015e8](05) e895eeffff call 00000482
> >> [000015ed](03) 83c408 add esp,+08
> >> [000015f0](02) 33c0 xor eax,eax
> >> [000015f2](01) 5d pop ebp
> >> [000015f3](01) c3 ret
> >> Size in bytes:(0034) [000015f3]
> >>
> >> machine stack stack machine assembly
> >> address address data code language
> >> ======== ======== ======== ========= ============> >> [000015d2][001025c6][00000000] 55 push ebp
> >> [000015d3][001025c6][00000000] 8bec mov ebp,esp
> >> [000015d5][001025c2][000015b2] 68b2150000 push 000015b2 // push
> >> Strachey_P [000015da][001025be][000015df] e8f3fcffff call 000012d2
> >> // call T
> >>
> >> Begin Simulation Execution Trace Stored at:21267a
> >> Address_of_T:12d2
> >> [000015b2][0021266a][0021266e] 55 push ebp
> >> [000015b3][0021266a][0021266e] 8bec mov ebp,esp
> >> [000015b5][00212666][000015b2] 68b2150000 push 000015b2 // push
> >> Strachey_P [000015ba][00212662][000015bf] e813fdffff call 000012d2
> >> // call T Infinitely Recursive Simulation Detected Simulation
> >> Stopped
> >>
> >> T knows its own machine address and on this basis it can easily
> >> examine its stored execution_trace of Strachey_P (see above) to
> >> determine: (a) Strachey_P is calling T with the same arguments
> >> that T was called with. (b) No instructions in Strachey_P could
> >> possibly escape this otherwise infinitely recursive emulation.
> >> (c) T aborts its emulation of Strachey_P before its call to T is
> >> emulated.
> >>
> >> [000015df][001025c6][00000000] 83c404 add esp,+04
> >> [000015e2][001025c2][00000000] 50 push eax
> >> [000015e3][001025be][00000433] 6833040000 push 00000433
> >> [000015e8][001025be][00000433] e895eeffff call 00000482
> >> Input_Halts = 0
> >> [000015ed][001025c6][00000000] 83c408 add esp,+08
> >> [000015f0][001025c6][00000000] 33c0 xor eax,eax
> >> [000015f2][001025ca][00100000] 5d pop ebp
> >> [000015f3][001025ce][00000004] c3 ret
> >> Number of Instructions Executed(528) == 8 Pages
> >
> > There is no recursion in [Strachey, 1965]; a mistake you keep making
> > again and again and again.
> >
> > /Flibble
> >
> >
>
> A simulating halt decider correctly simulates its input until it
> correctly determines that this simulated input would never reach its
> final state.
>
> T correctly predicts/determines that Strachey_P would never reach its
> [000015c9] machine address: final state.

Click here to read the complete article

Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<c5e0f904-cd76-493c-8e40-4ceee0fdb605n@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35038&group=comp.theory#35038

  copy link   Newsgroups: comp.theory
X-Received: by 2002:a05:600c:358c:b0:39c:97ed:baa5 with SMTP id p12-20020a05600c358c00b0039c97edbaa5mr22636229wmq.77.1656359129988;
Mon, 27 Jun 2022 12:45:29 -0700 (PDT)
X-Received: by 2002:a25:a345:0:b0:66c:c670:6d13 with SMTP id
d63-20020a25a345000000b0066cc6706d13mr8210497ybi.307.1656359129417; Mon, 27
Jun 2022 12:45:29 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.128.88.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.theory
Date: Mon, 27 Jun 2022 12:45:29 -0700 (PDT)
In-Reply-To: <8bca30ba-3f3f-4b76-b401-504b4873e55en@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=71.168.165.242; posting-account=ejFcQgoAAACAt5i0VbkATkR2ACWdgADD
NNTP-Posting-Host: 71.168.165.242
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com> <j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com> <qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com> <YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com> <f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com> <Sv-dnX5Vh499eyT_nZ2dnUU7_8zNnZ2d@giganews.com>
<fc96a583-3a51-45fd-8275-4bc8aaca8fc0n@googlegroups.com> <Lfudna-pu95HbyT_nZ2dnUU7_83NnZ2d@giganews.com>
<8bca30ba-3f3f-4b76-b401-504b4873e55en@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <c5e0f904-cd76-493c-8e40-4ceee0fdb605n@googlegroups.com>
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
From: dbush.mo...@gmail.com (Dennis Bush)
Injection-Date: Mon, 27 Jun 2022 19:45:29 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Dennis Bush - Mon, 27 Jun 2022 19:45 UTC

On Monday, June 27, 2022 at 2:13:44 PM UTC-4, Dennis Bush wrote:
> On Monday, June 27, 2022 at 2:11:45 PM UTC-4, olcott wrote:
> > On 6/27/2022 1:03 PM, Dennis Bush wrote:
> > > On Monday, June 27, 2022 at 1:20:39 PM UTC-4, olcott wrote:
> > >> On 6/27/2022 12:03 PM, Dennis Bush wrote:
> > >>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
> > >>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
> > >>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
> > >>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
> > >>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
> > >>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
> > >>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
> > >>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
> > >>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
> > >>>>>>>>>>>> *This is the outline of the complete refutation*
> > >>>>>>>>>>>> *of the only rebuttal that anyone has left*
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
> > >>>>>>>>>>>> never reaches the "ret" instruction of P.
> > >>>>>>>>>>>
> > >>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> > >>>>>>>>>>>
> > >>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> > >>>>>>>>>>>
> > >>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> > >>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
> > >>>>>>>>>>>> the semantics of the x86 language.
> > >>>>>>>>>>>
> > >>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
> > >>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> > >>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> > >>>>>>>>>>>> specified by these inputs.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
> > >>>>>>>>>>>
> > >>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
> > >>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
> > >>>>>>>>>>>
> > >>>>>>>>>>> H does not perform this mapping.
> > >>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
> > >>>>>>>>>>>
> > >>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
> > >>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> void P(u32 x)
> > >>>>>>>>>>>> {
> > >>>>>>>>>>>> if (H(x, x))
> > >>>>>>>>>>>> HERE: goto HERE;
> > >>>>>>>>>>>> return;
> > >>>>>>>>>>>> }
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> int main()
> > >>>>>>>>>>>> {
> > >>>>>>>>>>>> P(P);
> > >>>>>>>>>>>> }
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> _P()
> > >>>>>>>>>>>> [000011f0](01) 55 push ebp
> > >>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
> > >>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
> > >>>>>>>>>>>> [000011f6](01) 50 push eax
> > >>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
> > >>>>>>>>>>>> [000011fa](01) 51 push ecx
> > >>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
> > >>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
> > >>>>>>>>>>>> [00001205](02) 7402 jz 00001209
> > >>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
> > >>>>>>>>>>>> [00001209](01) 5d pop ebp
> > >>>>>>>>>>>> [0000120a](01) c3 ret
> > >>>>>>>>>>>> Size in bytes:(0027) [0000120a]
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> _main()
> > >>>>>>>>>>>> [00001210](01) 55 push ebp
> > >>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
> > >>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
> > >>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
> > >>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
> > >>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
> > >>>>>>>>>>>> [00001222](01) 5d pop ebp
> > >>>>>>>>>>>> [00001223](01) c3 ret
> > >>>>>>>>>>>> Size in bytes:(0020) [00001223]
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> machine stack stack machine assembly
> > >>>>>>>>>>>> address address data code language
> > >>>>>>>>>>>> ======== ======== ======== ========= =============
> > >>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
> > >>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
> > >>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
> > >>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
> > >>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
> > >>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
> > >>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
> > >>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
> > >>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
> > >>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
> > >>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
> > >>>>>>>>>>>> Address_of_H:1020
> > >>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
> > >>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
> > >>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
> > >>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
> > >>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
> > >>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
> > >>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
> > >>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> H knows its own machine address and on this basis it can easily
> > >>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
> > >>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
> > >>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
> > >>>>>>>>>>>> recursive emulation.
> > >>>>>>>>>>>
> > >>>>>>>>>>> FALSE. P contains these instructions:
> > >>>>>>>>>>>
> > >>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
> > >>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
> > >>>>>>>>>>> goto END_OF_CODE;
> > >>>>>>>>>>> return 0; // Does not halt
> > >>>>>>>>>>> END_OF_CODE:
> > >>>>>>>>>>> return 1; // Input has normally terminated
> > >>>>>>>>>>>
> > >>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
> > >>>>>>>>>>>
> > >>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
> > >>>>>>>>>>>
> > >>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
> > >>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
> > >>>>>>>>>>>> executed P
> > >>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
> > >>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
> > >>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
> > >>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
> > >>>>>>>>>>>> executed P
> > >>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
> > >>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
> > >>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
> > >>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
> > >>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
> > >>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
> > >>>>>>>>>> input never reaches the the "ret" instruction of P.
> > >>>>>>>>>
> > >>>>>>>>> Repeating your original point.
> > >>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> This is the actual behavior of the input to H(P,P).
> > >>>>>>>>>>
> > >>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
> > >>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> Again, repeating your original point.
> > >>>>>>>>>
> > >>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
> > >>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> > >>>>>>>>>> reject state on the basis of the actual behavior that is actually
> > >>>>>>>>>> specified by these inputs.
> > >>>>>>>>>> Therefore H(P,P)==0 is correct.
> > >>>>>>>>>
> > >>>>>>>>> And again, repeating your original point.
> > >>>>>>>>>
> > >>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
> > >>>>>>>>>
> > >>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
> > >>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
> > >>>>>>>> halt decider correctly predicts that its correctly simulated input will
> > >>>>>>>> never reach the final state "ret" instruction of this input.
> > >>>>>>>
> > >>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> > >>>>>> First of all I am not talking about UTM's.
> > >>>>>> I am talking about x86 emulation.
> > >>>>>> Try to encode what you mean, here is my guess:
> > >>>>>>
> > >>>>>> void P(u32 x)
> > >>>>>> {
> > >>>>>> if (emulate_x86(x, x))
> > >>>>>> HERE: goto HERE;
> > >>>>>> return;
> > >>>>>> }
> > >>>>>>
> > >>>>>> int main()
> > >>>>>> {
> > >>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
> > >>>>>> }
> > >>>>>
> > >>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
> > >>>>>
> > >>>>> void UTM(u32 x, u32 y)
> > >>>>> {
> > >>>>> x(y)
> > >>>>> }
> > >>>>>
> > >>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
> > >>>>>
> > >>>> A simulating halt decider correctly simulates its input until it
> > >>>> correctly determines that this simulated input would never reach its
> > >>>> final state.
> > >>>
> > >>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
> > >>>
> > >> Every simulating decider that correctly simulates its input until it
> > >> correctly determines that this simulated input would never reach its
> > >> final state correctly determines the halt status of this input.
> > >
> > > And H isn't such a decider, because it does not correctly determine that the input to H(P,P) would never halt as demonstrated by UTM(P,P) halting.
> > >
> > > The specification for H:
> > >
> > > H(x,y)==0 if and only if x(y) does not halt, and
> > > H(x,y)==1 if and only if x(y) halts.
> > >
> > > H does not meet the specification.
> > >
> > The spec is provably incorrect in this case:
> A spec can't be incorrect. It just is. If it can't be satisfied, then that validates the halting problem proofs that say it can't be satisfied.


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<Xs-dnUWk_Ma_kCf_nZ2dnUU7_8zNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35039&group=comp.theory#35039

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 27 Jun 2022 15:03:46 -0500
Date: Mon, 27 Jun 2022 15:03:45 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
Content-Language: en-US
Newsgroups: comp.theory
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com>
<j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com>
<qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com>
<YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com>
<f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com>
<q4CdnWm9zL2KbST_nZ2dnUU7_8zNnZ2d@giganews.com>
<9f0c8dcb-ae3a-47bf-9093-4e4d9377dc47n@googlegroups.com>
<68ednUyP7tp6ZCT_nZ2dnUU7_8zNnZ2d@giganews.com>
<995fecc1-7fc4-4b40-8d68-fd74df13efefn@googlegroups.com>
<s7ednVfn1vRNYyT_nZ2dnUU7_83NnZ2d@giganews.com>
<b9d6501d-9279-4862-b727-893b042022ben@googlegroups.com>
<hrednRmsHZMNmyf_nZ2dnUU7_8zNnZ2d@giganews.com>
<ccce4f12-08f3-4a18-9211-bc3fa58eafcfn@googlegroups.com>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <ccce4f12-08f3-4a18-9211-bc3fa58eafcfn@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <Xs-dnUWk_Ma_kCf_nZ2dnUU7_8zNnZ2d@giganews.com>
Lines: 277
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-K28CaO7eJ1YX5aqMv8NOWbisYdXtdTslmWdiWU5VgdbWRfVlLNliukJEPUBUYKqVZPglamdl/0XCGhA!O1xf46pls9oRCsd5MzGS/0uezSJW46zV9Bwo4wn3PaPoZNC/XgJyqXOISfX6w1EDYijsOz+Jnt74
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 16770
 by: olcott - Mon, 27 Jun 2022 20:03 UTC

On 6/27/2022 2:39 PM, Dennis Bush wrote:
> On Monday, June 27, 2022 at 3:35:53 PM UTC-4, olcott wrote:
>> On 6/27/2022 2:13 PM, Dennis Bush wrote:
>>> On Monday, June 27, 2022 at 3:02:47 PM UTC-4, olcott wrote:
>>>> On 6/27/2022 1:51 PM, Dennis Bush wrote:
>>>>> On Monday, June 27, 2022 at 2:41:50 PM UTC-4, olcott wrote:
>>>>>> On 6/27/2022 1:08 PM, Dennis Bush wrote:
>>>>>>> On Monday, June 27, 2022 at 1:59:58 PM UTC-4, olcott wrote:
>>>>>>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
>>>>>>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
>>>>>>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
>>>>>>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
>>>>>>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
>>>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>>>>>> *This is the outline of the complete refutation*
>>>>>>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
>>>>>>>>>>>>>>>>>> never reaches the "ret" instruction of P.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
>>>>>>>>>>>>>>>>>> the semantics of the x86 language.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
>>>>>>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> H does not perform this mapping.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> void P(u32 x)
>>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>> if (H(x, x))
>>>>>>>>>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>>>>>>>>>> return;
>>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>> P(P);
>>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> _P()
>>>>>>>>>>>>>>>>>> [000011f0](01) 55 push ebp
>>>>>>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>>>> [000011f6](01) 50 push eax
>>>>>>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>>>> [000011fa](01) 51 push ecx
>>>>>>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
>>>>>>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
>>>>>>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
>>>>>>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
>>>>>>>>>>>>>>>>>> [00001209](01) 5d pop ebp
>>>>>>>>>>>>>>>>>> [0000120a](01) c3 ret
>>>>>>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> _main()
>>>>>>>>>>>>>>>>>> [00001210](01) 55 push ebp
>>>>>>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
>>>>>>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
>>>>>>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
>>>>>>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
>>>>>>>>>>>>>>>>>> [00001222](01) 5d pop ebp
>>>>>>>>>>>>>>>>>> [00001223](01) c3 ret
>>>>>>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> machine stack stack machine assembly
>>>>>>>>>>>>>>>>>> address address data code language
>>>>>>>>>>>>>>>>>> ======== ======== ======== ========= =============
>>>>>>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
>>>>>>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
>>>>>>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
>>>>>>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
>>>>>>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
>>>>>>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
>>>>>>>>>>>>>>>>>> Address_of_H:1020
>>>>>>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
>>>>>>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
>>>>>>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
>>>>>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
>>>>>>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
>>>>>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
>>>>>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
>>>>>>>>>>>>>>>>>> recursive emulation.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> FALSE. P contains these instructions:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
>>>>>>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
>>>>>>>>>>>>>>>>> goto END_OF_CODE;
>>>>>>>>>>>>>>>>> return 0; // Does not halt
>>>>>>>>>>>>>>>>> END_OF_CODE:
>>>>>>>>>>>>>>>>> return 1; // Input has normally terminated
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
>>>>>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
>>>>>>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
>>>>>>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
>>>>>>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
>>>>>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
>>>>>>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
>>>>>>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
>>>>>>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
>>>>>>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
>>>>>>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
>>>>>>>>>>>>>>>> input never reaches the the "ret" instruction of P.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Repeating your original point.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Again, repeating your original point.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
>>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>>>>> Therefore H(P,P)==0 is correct.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> And again, repeating your original point.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
>>>>>>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
>>>>>>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
>>>>>>>>>>>>>> never reach the final state "ret" instruction of this input.
>>>>>>>>>>>>>
>>>>>>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>>>> First of all I am not talking about UTM's.
>>>>>>>>>>>> I am talking about x86 emulation.
>>>>>>>>>>>> Try to encode what you mean, here is my guess:
>>>>>>>>>>>>
>>>>>>>>>>>> void P(u32 x)
>>>>>>>>>>>> {
>>>>>>>>>>>> if (emulate_x86(x, x))
>>>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>>>> return;
>>>>>>>>>>>> }
>>>>>>>>>>>>
>>>>>>>>>>>> int main()
>>>>>>>>>>>> {
>>>>>>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
>>>>>>>>>>>> }
>>>>>>>>>>>
>>>>>>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
>>>>>>>>>>>
>>>>>>>>>>> void UTM(u32 x, u32 y)
>>>>>>>>>>> {
>>>>>>>>>>> x(y)
>>>>>>>>>>> }
>>>>>>>>>>>
>>>>>>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
>>>>>>>>>>>
>>>>>>>>>> A simulating halt decider correctly simulates its input until it
>>>>>>>>>> correctly determines that this simulated input would never reach its
>>>>>>>>>> final state.
>>>>>>>>>
>>>>>>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
>>>>>>>>>
>>>>>>>> The semantics of the x86 language conclusively proves that H(P,P)
>>>>>>>> correctly determines/predicts that its complete and correct x86
>>>>>>>> emulation of its input would never reach the "ret" instruction of P.
>>>>>>>
>>>>>>> As previously stated, this is nonsense. Failure to explain *in detail* why the below is wrong will be taken as an admission that it is correct.
>>>>>>>
>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>>>>>
>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>>>>>> I NEVER SAID that H does a complete and correct simulation of its input.
>>>>>
>>>>> Yes you did:
>>>>>
>>>>>> a) The complete and correct x86 emulation of the input to H(P,P) by H never reaches the "ret" instruction of P.
>>>>>
>>>> This does not say that H does a complete emulation.
>>>> A simulating halt decider correctly simulates its input until it
>>>> correctly determines that this simulated input would never reach its
>>>> final state.
>>>
>>> Which in the case of H(P,P) it doesn't since the correctly simulated input i.e. UTM(P,P) halts. H gets the wrong answer because it aborts too soon.
>>>
>>>> _Infinite_Loop()
>>>> [000015b8](01) 55 push ebp
>>>> [000015b9](02) 8bec mov ebp,esp
>>>> [000015bb](02) ebfe jmp 000015bb
>>>> [000015bd](01) 5d pop ebp
>>>> [000015be](01) c3 ret
>>>> Size in bytes:(0007) [000015be]
>>>>
>>>> The complete and correct x86 emulation of the input to H0(Infinite_Loop)
>>>> by H0 never reaches the "ret" instruction of Infinite_Loop.
>>>
>>> If H0 *actually* does a complete and correct emulation, then yes.
>> void Infinite_Loop()
>> {
>> HERE: goto HERE;
>> }
>>
>> You are not bright enough to tell that an infinite loop doesn't stop
>> running?
>
> My point was that if H0 does in fact do a correct and complete simulation then the behavior of H0(Infinite_Loop)


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<ead4dce1-03a6-445e-b749-b81b4949f1ban@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35040&group=comp.theory#35040

  copy link   Newsgroups: comp.theory
X-Received: by 2002:a5d:5a12:0:b0:21b:993a:7f8c with SMTP id bq18-20020a5d5a12000000b0021b993a7f8cmr13614450wrb.43.1656360454629;
Mon, 27 Jun 2022 13:07:34 -0700 (PDT)
X-Received: by 2002:a25:f508:0:b0:66c:8fbd:9060 with SMTP id
a8-20020a25f508000000b0066c8fbd9060mr12856094ybe.16.1656360453821; Mon, 27
Jun 2022 13:07:33 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.128.87.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.theory
Date: Mon, 27 Jun 2022 13:07:33 -0700 (PDT)
In-Reply-To: <Xs-dnUWk_Ma_kCf_nZ2dnUU7_8zNnZ2d@giganews.com>
Injection-Info: google-groups.googlegroups.com; posting-host=71.168.165.242; posting-account=ejFcQgoAAACAt5i0VbkATkR2ACWdgADD
NNTP-Posting-Host: 71.168.165.242
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com> <j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com> <qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com> <YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com> <f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com> <q4CdnWm9zL2KbST_nZ2dnUU7_8zNnZ2d@giganews.com>
<9f0c8dcb-ae3a-47bf-9093-4e4d9377dc47n@googlegroups.com> <68ednUyP7tp6ZCT_nZ2dnUU7_8zNnZ2d@giganews.com>
<995fecc1-7fc4-4b40-8d68-fd74df13efefn@googlegroups.com> <s7ednVfn1vRNYyT_nZ2dnUU7_83NnZ2d@giganews.com>
<b9d6501d-9279-4862-b727-893b042022ben@googlegroups.com> <hrednRmsHZMNmyf_nZ2dnUU7_8zNnZ2d@giganews.com>
<ccce4f12-08f3-4a18-9211-bc3fa58eafcfn@googlegroups.com> <Xs-dnUWk_Ma_kCf_nZ2dnUU7_8zNnZ2d@giganews.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <ead4dce1-03a6-445e-b749-b81b4949f1ban@googlegroups.com>
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
From: dbush.mo...@gmail.com (Dennis Bush)
Injection-Date: Mon, 27 Jun 2022 20:07:34 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Dennis Bush - Mon, 27 Jun 2022 20:07 UTC

On Monday, June 27, 2022 at 4:03:53 PM UTC-4, olcott wrote:
> On 6/27/2022 2:39 PM, Dennis Bush wrote:
> > On Monday, June 27, 2022 at 3:35:53 PM UTC-4, olcott wrote:
> >> On 6/27/2022 2:13 PM, Dennis Bush wrote:
> >>> On Monday, June 27, 2022 at 3:02:47 PM UTC-4, olcott wrote:
> >>>> On 6/27/2022 1:51 PM, Dennis Bush wrote:
> >>>>> On Monday, June 27, 2022 at 2:41:50 PM UTC-4, olcott wrote:
> >>>>>> On 6/27/2022 1:08 PM, Dennis Bush wrote:
> >>>>>>> On Monday, June 27, 2022 at 1:59:58 PM UTC-4, olcott wrote:
> >>>>>>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
> >>>>>>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
> >>>>>>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
> >>>>>>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
> >>>>>>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
> >>>>>>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
> >>>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
> >>>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>>>>>> *This is the outline of the complete refutation*
> >>>>>>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
> >>>>>>>>>>>>>>>>>> never reaches the "ret" instruction of P.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
> >>>>>>>>>>>>>>>>>> the semantics of the x86 language.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i..e. the halting function):
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
> >>>>>>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> H does not perform this mapping.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> void P(u32 x)
> >>>>>>>>>>>>>>>>>> {
> >>>>>>>>>>>>>>>>>> if (H(x, x))
> >>>>>>>>>>>>>>>>>> HERE: goto HERE;
> >>>>>>>>>>>>>>>>>> return;
> >>>>>>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> int main()
> >>>>>>>>>>>>>>>>>> {
> >>>>>>>>>>>>>>>>>> P(P);
> >>>>>>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> _P()
> >>>>>>>>>>>>>>>>>> [000011f0](01) 55 push ebp
> >>>>>>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>>>>> [000011f6](01) 50 push eax
> >>>>>>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>>>>> [000011fa](01) 51 push ecx
> >>>>>>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
> >>>>>>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
> >>>>>>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
> >>>>>>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
> >>>>>>>>>>>>>>>>>> [00001209](01) 5d pop ebp
> >>>>>>>>>>>>>>>>>> [0000120a](01) c3 ret
> >>>>>>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> _main()
> >>>>>>>>>>>>>>>>>> [00001210](01) 55 push ebp
> >>>>>>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
> >>>>>>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
> >>>>>>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
> >>>>>>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
> >>>>>>>>>>>>>>>>>> [00001222](01) 5d pop ebp
> >>>>>>>>>>>>>>>>>> [00001223](01) c3 ret
> >>>>>>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> machine stack stack machine assembly
> >>>>>>>>>>>>>>>>>> address address data code language
> >>>>>>>>>>>>>>>>>> ======== ======== ======== ========= =============
> >>>>>>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
> >>>>>>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
> >>>>>>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
> >>>>>>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
> >>>>>>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
> >>>>>>>>>>>>>>>>>> Address_of_H:1020
> >>>>>>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
> >>>>>>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
> >>>>>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
> >>>>>>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
> >>>>>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
> >>>>>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
> >>>>>>>>>>>>>>>>>> recursive emulation.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> FALSE. P contains these instructions:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
> >>>>>>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
> >>>>>>>>>>>>>>>>> goto END_OF_CODE;
> >>>>>>>>>>>>>>>>> return 0; // Does not halt
> >>>>>>>>>>>>>>>>> END_OF_CODE:
> >>>>>>>>>>>>>>>>> return 1; // Input has normally terminated
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
> >>>>>>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
> >>>>>>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
> >>>>>>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
> >>>>>>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
> >>>>>>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
> >>>>>>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
> >>>>>>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
> >>>>>>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
> >>>>>>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct..
> >>>>>>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
> >>>>>>>>>>>>>>>> input never reaches the the "ret" instruction of P.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Repeating your original point.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Again, repeating your original point.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
> >>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>>>>>> Therefore H(P,P)==0 is correct.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> And again, repeating your original point.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
> >>>>>>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
> >>>>>>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
> >>>>>>>>>>>>>> never reach the final state "ret" instruction of this input.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>>>>>> First of all I am not talking about UTM's.
> >>>>>>>>>>>> I am talking about x86 emulation.
> >>>>>>>>>>>> Try to encode what you mean, here is my guess:
> >>>>>>>>>>>>
> >>>>>>>>>>>> void P(u32 x)
> >>>>>>>>>>>> {
> >>>>>>>>>>>> if (emulate_x86(x, x))
> >>>>>>>>>>>> HERE: goto HERE;
> >>>>>>>>>>>> return;
> >>>>>>>>>>>> }
> >>>>>>>>>>>>
> >>>>>>>>>>>> int main()
> >>>>>>>>>>>> {
> >>>>>>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
> >>>>>>>>>>>> }
> >>>>>>>>>>>
> >>>>>>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
> >>>>>>>>>>>
> >>>>>>>>>>> void UTM(u32 x, u32 y)
> >>>>>>>>>>> {
> >>>>>>>>>>> x(y)
> >>>>>>>>>>> }
> >>>>>>>>>>>
> >>>>>>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
> >>>>>>>>>>>
> >>>>>>>>>> A simulating halt decider correctly simulates its input until it
> >>>>>>>>>> correctly determines that this simulated input would never reach its
> >>>>>>>>>> final state.
> >>>>>>>>>
> >>>>>>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
> >>>>>>>>>
> >>>>>>>> The semantics of the x86 language conclusively proves that H(P,P)
> >>>>>>>> correctly determines/predicts that its complete and correct x86
> >>>>>>>> emulation of its input would never reach the "ret" instruction of P.
> >>>>>>>
> >>>>>>> As previously stated, this is nonsense. Failure to explain *in detail* why the below is wrong will be taken as an admission that it is correct.
> >>>>>>>
> >>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> >>>>>>>
> >>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> >>>>>> I NEVER SAID that H does a complete and correct simulation of its input.
> >>>>>
> >>>>> Yes you did:
> >>>>>
> >>>>>> a) The complete and correct x86 emulation of the input to H(P,P) by H never reaches the "ret" instruction of P.
> >>>>>
> >>>> This does not say that H does a complete emulation.
> >>>> A simulating halt decider correctly simulates its input until it
> >>>> correctly determines that this simulated input would never reach its
> >>>> final state.
> >>>
> >>> Which in the case of H(P,P) it doesn't since the correctly simulated input i.e. UTM(P,P) halts. H gets the wrong answer because it aborts too soon.
> >>>
> >>>> _Infinite_Loop()
> >>>> [000015b8](01) 55 push ebp
> >>>> [000015b9](02) 8bec mov ebp,esp
> >>>> [000015bb](02) ebfe jmp 000015bb
> >>>> [000015bd](01) 5d pop ebp
> >>>> [000015be](01) c3 ret
> >>>> Size in bytes:(0007) [000015be]
> >>>>
> >>>> The complete and correct x86 emulation of the input to H0(Infinite_Loop)
> >>>> by H0 never reaches the "ret" instruction of Infinite_Loop.
> >>>
> >>> If H0 *actually* does a complete and correct emulation, then yes.
> >> void Infinite_Loop()
> >> {
> >> HERE: goto HERE;
> >> }
> >>
> >> You are not bright enough to tell that an infinite loop doesn't stop
> >> running?
> >
> > My point was that if H0 does in fact do a correct and complete simulation then the behavior of H0(Infinite_Loop)
> You didn't notice that it is ridiculously stupid to think that an
> infinite loop can be completely simulated?


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<s8ednRTcbPnnhSf_nZ2dnUU7_83NnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35042&group=comp.theory#35042

  copy link   Newsgroups: comp.theory sci.logic sci.math
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 27 Jun 2022 15:52:10 -0500
Date: Mon, 27 Jun 2022 15:52:09 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
Content-Language: en-US
Newsgroups: comp.theory,sci.logic,sci.math
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com>
<j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com>
<qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com>
<YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com>
<f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com>
<Sv-dnX5Vh499eyT_nZ2dnUU7_8zNnZ2d@giganews.com>
<fc96a583-3a51-45fd-8275-4bc8aaca8fc0n@googlegroups.com>
<Lfudna-pu95HbyT_nZ2dnUU7_83NnZ2d@giganews.com>
<8bca30ba-3f3f-4b76-b401-504b4873e55en@googlegroups.com>
<c5e0f904-cd76-493c-8e40-4ceee0fdb605n@googlegroups.com>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <c5e0f904-cd76-493c-8e40-4ceee0fdb605n@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <s8ednRTcbPnnhSf_nZ2dnUU7_83NnZ2d@giganews.com>
Lines: 255
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-sZ7hv6UMC795MR7PQ6iydW1v/PmX0C3zxUUVoM2WF28fvSJzKevKYnGiqacsClJE4avT/DIKOxbNGTw!2BJI/BrxszTjiQKmiXaS8yWR2iKecARYf+M9C+LvXESsxxMZzyC2nOwTM/w4pGp5XLDjmfAA93Xw
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 14918
 by: olcott - Mon, 27 Jun 2022 20:52 UTC

On 6/27/2022 2:45 PM, Dennis Bush wrote:
> On Monday, June 27, 2022 at 2:13:44 PM UTC-4, Dennis Bush wrote:
>> On Monday, June 27, 2022 at 2:11:45 PM UTC-4, olcott wrote:
>>> On 6/27/2022 1:03 PM, Dennis Bush wrote:
>>>> On Monday, June 27, 2022 at 1:20:39 PM UTC-4, olcott wrote:
>>>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
>>>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
>>>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
>>>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
>>>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
>>>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
>>>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
>>>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
>>>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
>>>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>>> *This is the outline of the complete refutation*
>>>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
>>>>>>>>>>>>>>> never reaches the "ret" instruction of P.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
>>>>>>>>>>>>>>> the semantics of the x86 language.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
>>>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> H does not perform this mapping.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> void P(u32 x)
>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>> if (H(x, x))
>>>>>>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>>>>>>> return;
>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>> P(P);
>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> _P()
>>>>>>>>>>>>>>> [000011f0](01) 55 push ebp
>>>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
>>>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>> [000011f6](01) 50 push eax
>>>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>> [000011fa](01) 51 push ecx
>>>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
>>>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
>>>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
>>>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
>>>>>>>>>>>>>>> [00001209](01) 5d pop ebp
>>>>>>>>>>>>>>> [0000120a](01) c3 ret
>>>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> _main()
>>>>>>>>>>>>>>> [00001210](01) 55 push ebp
>>>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
>>>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
>>>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
>>>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
>>>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
>>>>>>>>>>>>>>> [00001222](01) 5d pop ebp
>>>>>>>>>>>>>>> [00001223](01) c3 ret
>>>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> machine stack stack machine assembly
>>>>>>>>>>>>>>> address address data code language
>>>>>>>>>>>>>>> ======== ======== ======== ========= =============
>>>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
>>>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
>>>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
>>>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
>>>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
>>>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
>>>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
>>>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
>>>>>>>>>>>>>>> Address_of_H:1020
>>>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
>>>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
>>>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
>>>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
>>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
>>>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
>>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
>>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
>>>>>>>>>>>>>>> recursive emulation.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> FALSE. P contains these instructions:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
>>>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
>>>>>>>>>>>>>> goto END_OF_CODE;
>>>>>>>>>>>>>> return 0; // Does not halt
>>>>>>>>>>>>>> END_OF_CODE:
>>>>>>>>>>>>>> return 1; // Input has normally terminated
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
>>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
>>>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
>>>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
>>>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
>>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
>>>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
>>>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
>>>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
>>>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
>>>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
>>>>>>>>>>>>> input never reaches the the "ret" instruction of P.
>>>>>>>>>>>>
>>>>>>>>>>>> Repeating your original point.
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
>>>>>>>>>>>>>
>>>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Again, repeating your original point.
>>>>>>>>>>>>
>>>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>> Therefore H(P,P)==0 is correct.
>>>>>>>>>>>>
>>>>>>>>>>>> And again, repeating your original point.
>>>>>>>>>>>>
>>>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
>>>>>>>>>>>>
>>>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
>>>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
>>>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
>>>>>>>>>>> never reach the final state "ret" instruction of this input.
>>>>>>>>>>
>>>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>> First of all I am not talking about UTM's.
>>>>>>>>> I am talking about x86 emulation.
>>>>>>>>> Try to encode what you mean, here is my guess:
>>>>>>>>>
>>>>>>>>> void P(u32 x)
>>>>>>>>> {
>>>>>>>>> if (emulate_x86(x, x))
>>>>>>>>> HERE: goto HERE;
>>>>>>>>> return;
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> int main()
>>>>>>>>> {
>>>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
>>>>>>>>> }
>>>>>>>>
>>>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
>>>>>>>>
>>>>>>>> void UTM(u32 x, u32 y)
>>>>>>>> {
>>>>>>>> x(y)
>>>>>>>> }
>>>>>>>>
>>>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
>>>>>>>>
>>>>>>> A simulating halt decider correctly simulates its input until it
>>>>>>> correctly determines that this simulated input would never reach its
>>>>>>> final state.
>>>>>>
>>>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
>>>>>>
>>>>> Every simulating decider that correctly simulates its input until it
>>>>> correctly determines that this simulated input would never reach its
>>>>> final state correctly determines the halt status of this input.
>>>>
>>>> And H isn't such a decider, because it does not correctly determine that the input to H(P,P) would never halt as demonstrated by UTM(P,P) halting.
>>>>
>>>> The specification for H:
>>>>
>>>> H(x,y)==0 if and only if x(y) does not halt, and
>>>> H(x,y)==1 if and only if x(y) halts.
>>>>
>>>> H does not meet the specification.
>>>>
>>> The spec is provably incorrect in this case:
>> A spec can't be incorrect. It just is. If it can't be satisfied, then that validates the halting problem proofs that say it can't be satisfied.
>
>
> No response to this I see. So you agree that your H does not meet the above spec that the halting problem requires?


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<i42dnfG6dLPshyf_nZ2dnUU7_83NnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35044&group=comp.theory#35044

  copy link   Newsgroups: comp.theory sci.logic sci.math
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 27 Jun 2022 16:00:33 -0500
Date: Mon, 27 Jun 2022 16:00:31 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
Content-Language: en-US
Newsgroups: comp.theory,sci.logic,sci.math
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com>
<qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com>
<YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com>
<f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com>
<q4CdnWm9zL2KbST_nZ2dnUU7_8zNnZ2d@giganews.com>
<9f0c8dcb-ae3a-47bf-9093-4e4d9377dc47n@googlegroups.com>
<68ednUyP7tp6ZCT_nZ2dnUU7_8zNnZ2d@giganews.com>
<995fecc1-7fc4-4b40-8d68-fd74df13efefn@googlegroups.com>
<s7ednVfn1vRNYyT_nZ2dnUU7_83NnZ2d@giganews.com>
<b9d6501d-9279-4862-b727-893b042022ben@googlegroups.com>
<hrednRmsHZMNmyf_nZ2dnUU7_8zNnZ2d@giganews.com>
<ccce4f12-08f3-4a18-9211-bc3fa58eafcfn@googlegroups.com>
<Xs-dnUWk_Ma_kCf_nZ2dnUU7_8zNnZ2d@giganews.com>
<ead4dce1-03a6-445e-b749-b81b4949f1ban@googlegroups.com>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <ead4dce1-03a6-445e-b749-b81b4949f1ban@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <i42dnfG6dLPshyf_nZ2dnUU7_83NnZ2d@giganews.com>
Lines: 286
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-RirtpTaQSqxr6y+5UWjoJ8y4Dl+HwdjaPqonXHiq6n9YAJki7uiwNnOs07D2MNpaXCT4TyvduqN+xUM!yZ6xaGDz3i3ZtA1LmAt0mP9w87syrClfTOLjGOBBZni5Y1/9egu41GSqS9NUqqtqppDBVAefGKEo
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 18078
 by: olcott - Mon, 27 Jun 2022 21:00 UTC

On 6/27/2022 3:07 PM, Dennis Bush wrote:
> On Monday, June 27, 2022 at 4:03:53 PM UTC-4, olcott wrote:
>> On 6/27/2022 2:39 PM, Dennis Bush wrote:
>>> On Monday, June 27, 2022 at 3:35:53 PM UTC-4, olcott wrote:
>>>> On 6/27/2022 2:13 PM, Dennis Bush wrote:
>>>>> On Monday, June 27, 2022 at 3:02:47 PM UTC-4, olcott wrote:
>>>>>> On 6/27/2022 1:51 PM, Dennis Bush wrote:
>>>>>>> On Monday, June 27, 2022 at 2:41:50 PM UTC-4, olcott wrote:
>>>>>>>> On 6/27/2022 1:08 PM, Dennis Bush wrote:
>>>>>>>>> On Monday, June 27, 2022 at 1:59:58 PM UTC-4, olcott wrote:
>>>>>>>>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
>>>>>>>>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
>>>>>>>>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
>>>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
>>>>>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>>>>>>>> *This is the outline of the complete refutation*
>>>>>>>>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
>>>>>>>>>>>>>>>>>>>> never reaches the "ret" instruction of P.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
>>>>>>>>>>>>>>>>>>>> the semantics of the x86 language.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
>>>>>>>>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> H does not perform this mapping.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> void P(u32 x)
>>>>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>>>> if (H(x, x))
>>>>>>>>>>>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>>>>>>>>>>>> return;
>>>>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>>>> P(P);
>>>>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> _P()
>>>>>>>>>>>>>>>>>>>> [000011f0](01) 55 push ebp
>>>>>>>>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>>>>>> [000011f6](01) 50 push eax
>>>>>>>>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>>>>>> [000011fa](01) 51 push ecx
>>>>>>>>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
>>>>>>>>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
>>>>>>>>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
>>>>>>>>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
>>>>>>>>>>>>>>>>>>>> [00001209](01) 5d pop ebp
>>>>>>>>>>>>>>>>>>>> [0000120a](01) c3 ret
>>>>>>>>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> _main()
>>>>>>>>>>>>>>>>>>>> [00001210](01) 55 push ebp
>>>>>>>>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
>>>>>>>>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
>>>>>>>>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
>>>>>>>>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
>>>>>>>>>>>>>>>>>>>> [00001222](01) 5d pop ebp
>>>>>>>>>>>>>>>>>>>> [00001223](01) c3 ret
>>>>>>>>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> machine stack stack machine assembly
>>>>>>>>>>>>>>>>>>>> address address data code language
>>>>>>>>>>>>>>>>>>>> ======== ======== ======== ========= =============
>>>>>>>>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
>>>>>>>>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
>>>>>>>>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
>>>>>>>>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
>>>>>>>>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
>>>>>>>>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
>>>>>>>>>>>>>>>>>>>> Address_of_H:1020
>>>>>>>>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
>>>>>>>>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
>>>>>>>>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
>>>>>>>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
>>>>>>>>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
>>>>>>>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
>>>>>>>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
>>>>>>>>>>>>>>>>>>>> recursive emulation.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> FALSE. P contains these instructions:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
>>>>>>>>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
>>>>>>>>>>>>>>>>>>> goto END_OF_CODE;
>>>>>>>>>>>>>>>>>>> return 0; // Does not halt
>>>>>>>>>>>>>>>>>>> END_OF_CODE:
>>>>>>>>>>>>>>>>>>> return 1; // Input has normally terminated
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
>>>>>>>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
>>>>>>>>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
>>>>>>>>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
>>>>>>>>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
>>>>>>>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
>>>>>>>>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
>>>>>>>>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
>>>>>>>>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
>>>>>>>>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
>>>>>>>>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
>>>>>>>>>>>>>>>>>> input never reaches the the "ret" instruction of P.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Repeating your original point.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Again, repeating your original point.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
>>>>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>>>>>>> Therefore H(P,P)==0 is correct.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> And again, repeating your original point.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
>>>>>>>>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
>>>>>>>>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
>>>>>>>>>>>>>>>> never reach the final state "ret" instruction of this input.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>>>>>> First of all I am not talking about UTM's.
>>>>>>>>>>>>>> I am talking about x86 emulation.
>>>>>>>>>>>>>> Try to encode what you mean, here is my guess:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> void P(u32 x)
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>> if (emulate_x86(x, x))
>>>>>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>>>>>> return;
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>
>>>>>>>>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
>>>>>>>>>>>>>
>>>>>>>>>>>>> void UTM(u32 x, u32 y)
>>>>>>>>>>>>> {
>>>>>>>>>>>>> x(y)
>>>>>>>>>>>>> }
>>>>>>>>>>>>>
>>>>>>>>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
>>>>>>>>>>>>>
>>>>>>>>>>>> A simulating halt decider correctly simulates its input until it
>>>>>>>>>>>> correctly determines that this simulated input would never reach its
>>>>>>>>>>>> final state.
>>>>>>>>>>>
>>>>>>>>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
>>>>>>>>>>>
>>>>>>>>>> The semantics of the x86 language conclusively proves that H(P,P)
>>>>>>>>>> correctly determines/predicts that its complete and correct x86
>>>>>>>>>> emulation of its input would never reach the "ret" instruction of P.
>>>>>>>>>
>>>>>>>>> As previously stated, this is nonsense. Failure to explain *in detail* why the below is wrong will be taken as an admission that it is correct.
>>>>>>>>>
>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>>>>>>>
>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>>>>>>>> I NEVER SAID that H does a complete and correct simulation of its input.
>>>>>>>
>>>>>>> Yes you did:
>>>>>>>
>>>>>>>> a) The complete and correct x86 emulation of the input to H(P,P) by H never reaches the "ret" instruction of P.
>>>>>>>
>>>>>> This does not say that H does a complete emulation.
>>>>>> A simulating halt decider correctly simulates its input until it
>>>>>> correctly determines that this simulated input would never reach its
>>>>>> final state.
>>>>>
>>>>> Which in the case of H(P,P) it doesn't since the correctly simulated input i.e. UTM(P,P) halts. H gets the wrong answer because it aborts too soon.
>>>>>
>>>>>> _Infinite_Loop()
>>>>>> [000015b8](01) 55 push ebp
>>>>>> [000015b9](02) 8bec mov ebp,esp
>>>>>> [000015bb](02) ebfe jmp 000015bb
>>>>>> [000015bd](01) 5d pop ebp
>>>>>> [000015be](01) c3 ret
>>>>>> Size in bytes:(0007) [000015be]
>>>>>>
>>>>>> The complete and correct x86 emulation of the input to H0(Infinite_Loop)
>>>>>> by H0 never reaches the "ret" instruction of Infinite_Loop.
>>>>>
>>>>> If H0 *actually* does a complete and correct emulation, then yes.
>>>> void Infinite_Loop()
>>>> {
>>>> HERE: goto HERE;
>>>> }
>>>>
>>>> You are not bright enough to tell that an infinite loop doesn't stop
>>>> running?
>>>
>>> My point was that if H0 does in fact do a correct and complete simulation then the behavior of H0(Infinite_Loop)
>> You didn't notice that it is ridiculously stupid to think that an
>> infinite loop can be completely simulated?
>
> It can, by a simulator that *never* aborts.
>
> If H0 does in fact do a correct and complete simulation by never aborting then the behavior of H0(Infinite_Loop) is a source of truth for H(Infinite_Loop). H(P,P) is not a source of truth for H(P,P) because H does not do a correct and complete simulation. UTM(P,P) does and it halts, so H(P,P)==0 is wrong


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<71b90384-d502-4a24-a1a7-b6f7548e0ebbn@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35045&group=comp.theory#35045

  copy link   Newsgroups: comp.theory
X-Received: by 2002:a5d:47cf:0:b0:21b:b58b:99c5 with SMTP id o15-20020a5d47cf000000b0021bb58b99c5mr14166604wrc.348.1656363730925;
Mon, 27 Jun 2022 14:02:10 -0700 (PDT)
X-Received: by 2002:a81:3ac6:0:b0:31b:d731:f03c with SMTP id
h189-20020a813ac6000000b0031bd731f03cmr5124738ywa.461.1656363730075; Mon, 27
Jun 2022 14:02:10 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.128.88.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.theory
Date: Mon, 27 Jun 2022 14:02:09 -0700 (PDT)
In-Reply-To: <s8ednRTcbPnnhSf_nZ2dnUU7_83NnZ2d@giganews.com>
Injection-Info: google-groups.googlegroups.com; posting-host=71.168.165.242; posting-account=ejFcQgoAAACAt5i0VbkATkR2ACWdgADD
NNTP-Posting-Host: 71.168.165.242
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com> <j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com> <qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com> <YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com> <f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com> <Sv-dnX5Vh499eyT_nZ2dnUU7_8zNnZ2d@giganews.com>
<fc96a583-3a51-45fd-8275-4bc8aaca8fc0n@googlegroups.com> <Lfudna-pu95HbyT_nZ2dnUU7_83NnZ2d@giganews.com>
<8bca30ba-3f3f-4b76-b401-504b4873e55en@googlegroups.com> <c5e0f904-cd76-493c-8e40-4ceee0fdb605n@googlegroups.com>
<s8ednRTcbPnnhSf_nZ2dnUU7_83NnZ2d@giganews.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <71b90384-d502-4a24-a1a7-b6f7548e0ebbn@googlegroups.com>
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
From: dbush.mo...@gmail.com (Dennis Bush)
Injection-Date: Mon, 27 Jun 2022 21:02:10 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Dennis Bush - Mon, 27 Jun 2022 21:02 UTC

On Monday, June 27, 2022 at 4:52:17 PM UTC-4, olcott wrote:
> On 6/27/2022 2:45 PM, Dennis Bush wrote:
> > On Monday, June 27, 2022 at 2:13:44 PM UTC-4, Dennis Bush wrote:
> >> On Monday, June 27, 2022 at 2:11:45 PM UTC-4, olcott wrote:
> >>> On 6/27/2022 1:03 PM, Dennis Bush wrote:
> >>>> On Monday, June 27, 2022 at 1:20:39 PM UTC-4, olcott wrote:
> >>>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
> >>>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
> >>>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
> >>>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
> >>>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
> >>>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
> >>>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
> >>>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
> >>>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>>> *This is the outline of the complete refutation*
> >>>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
> >>>>>>>>>>>>>>> never reaches the "ret" instruction of P.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong..
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
> >>>>>>>>>>>>>>> the semantics of the x86 language.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
> >>>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> H does not perform this mapping.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> void P(u32 x)
> >>>>>>>>>>>>>>> {
> >>>>>>>>>>>>>>> if (H(x, x))
> >>>>>>>>>>>>>>> HERE: goto HERE;
> >>>>>>>>>>>>>>> return;
> >>>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> int main()
> >>>>>>>>>>>>>>> {
> >>>>>>>>>>>>>>> P(P);
> >>>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> _P()
> >>>>>>>>>>>>>>> [000011f0](01) 55 push ebp
> >>>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>> [000011f6](01) 50 push eax
> >>>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>> [000011fa](01) 51 push ecx
> >>>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
> >>>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
> >>>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
> >>>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
> >>>>>>>>>>>>>>> [00001209](01) 5d pop ebp
> >>>>>>>>>>>>>>> [0000120a](01) c3 ret
> >>>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> _main()
> >>>>>>>>>>>>>>> [00001210](01) 55 push ebp
> >>>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
> >>>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
> >>>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
> >>>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
> >>>>>>>>>>>>>>> [00001222](01) 5d pop ebp
> >>>>>>>>>>>>>>> [00001223](01) c3 ret
> >>>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> machine stack stack machine assembly
> >>>>>>>>>>>>>>> address address data code language
> >>>>>>>>>>>>>>> ======== ======== ======== ========= =============
> >>>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
> >>>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
> >>>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
> >>>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
> >>>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
> >>>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
> >>>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
> >>>>>>>>>>>>>>> Address_of_H:1020
> >>>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
> >>>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
> >>>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
> >>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
> >>>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
> >>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
> >>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
> >>>>>>>>>>>>>>> recursive emulation.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> FALSE. P contains these instructions:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
> >>>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
> >>>>>>>>>>>>>> goto END_OF_CODE;
> >>>>>>>>>>>>>> return 0; // Does not halt
> >>>>>>>>>>>>>> END_OF_CODE:
> >>>>>>>>>>>>>> return 1; // Input has normally terminated
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
> >>>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
> >>>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
> >>>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
> >>>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
> >>>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
> >>>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
> >>>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
> >>>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
> >>>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
> >>>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
> >>>>>>>>>>>>> input never reaches the the "ret" instruction of P.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Repeating your original point.
> >>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Again, repeating your original point.
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
> >>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>>> Therefore H(P,P)==0 is correct.
> >>>>>>>>>>>>
> >>>>>>>>>>>> And again, repeating your original point.
> >>>>>>>>>>>>
> >>>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
> >>>>>>>>>>>>
> >>>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
> >>>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
> >>>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
> >>>>>>>>>>> never reach the final state "ret" instruction of this input.
> >>>>>>>>>>
> >>>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>>> First of all I am not talking about UTM's.
> >>>>>>>>> I am talking about x86 emulation.
> >>>>>>>>> Try to encode what you mean, here is my guess:
> >>>>>>>>>
> >>>>>>>>> void P(u32 x)
> >>>>>>>>> {
> >>>>>>>>> if (emulate_x86(x, x))
> >>>>>>>>> HERE: goto HERE;
> >>>>>>>>> return;
> >>>>>>>>> }
> >>>>>>>>>
> >>>>>>>>> int main()
> >>>>>>>>> {
> >>>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
> >>>>>>>>> }
> >>>>>>>>
> >>>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
> >>>>>>>>
> >>>>>>>> void UTM(u32 x, u32 y)
> >>>>>>>> {
> >>>>>>>> x(y)
> >>>>>>>> }
> >>>>>>>>
> >>>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
> >>>>>>>>
> >>>>>>> A simulating halt decider correctly simulates its input until it
> >>>>>>> correctly determines that this simulated input would never reach its
> >>>>>>> final state.
> >>>>>>
> >>>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
> >>>>>>
> >>>>> Every simulating decider that correctly simulates its input until it
> >>>>> correctly determines that this simulated input would never reach its
> >>>>> final state correctly determines the halt status of this input.
> >>>>
> >>>> And H isn't such a decider, because it does not correctly determine that the input to H(P,P) would never halt as demonstrated by UTM(P,P) halting.
> >>>>
> >>>> The specification for H:
> >>>>
> >>>> H(x,y)==0 if and only if x(y) does not halt, and
> >>>> H(x,y)==1 if and only if x(y) halts.
> >>>>
> >>>> H does not meet the specification.
> >>>>
> >>> The spec is provably incorrect in this case:
> >> A spec can't be incorrect. It just is. If it can't be satisfied, then that validates the halting problem proofs that say it can't be satisfied.
> >
> >
> > No response to this I see. So you agree that your H does not meet the above spec that the halting problem requires?
> You are just playing word games so I will use a different word:
> "criterion measure".
> A halt decider must compute the mapping from its inputs to an accept or
> reject state on the basis of the actual behavior that is actually
> specified by these inputs.


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<164f1bf0-db9f-451c-b59d-90fb1aa9caa2n@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35046&group=comp.theory#35046

  copy link   Newsgroups: comp.theory
X-Received: by 2002:a05:6000:1448:b0:21b:b7db:c40b with SMTP id v8-20020a056000144800b0021bb7dbc40bmr14752522wrx.279.1656363869332;
Mon, 27 Jun 2022 14:04:29 -0700 (PDT)
X-Received: by 2002:a25:a345:0:b0:66c:c670:6d13 with SMTP id
d63-20020a25a345000000b0066cc6706d13mr8590803ybi.307.1656363868705; Mon, 27
Jun 2022 14:04:28 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.128.87.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.theory
Date: Mon, 27 Jun 2022 14:04:28 -0700 (PDT)
In-Reply-To: <i42dnfG6dLPshyf_nZ2dnUU7_83NnZ2d@giganews.com>
Injection-Info: google-groups.googlegroups.com; posting-host=71.168.165.242; posting-account=ejFcQgoAAACAt5i0VbkATkR2ACWdgADD
NNTP-Posting-Host: 71.168.165.242
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com> <qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com> <YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com> <f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com> <q4CdnWm9zL2KbST_nZ2dnUU7_8zNnZ2d@giganews.com>
<9f0c8dcb-ae3a-47bf-9093-4e4d9377dc47n@googlegroups.com> <68ednUyP7tp6ZCT_nZ2dnUU7_8zNnZ2d@giganews.com>
<995fecc1-7fc4-4b40-8d68-fd74df13efefn@googlegroups.com> <s7ednVfn1vRNYyT_nZ2dnUU7_83NnZ2d@giganews.com>
<b9d6501d-9279-4862-b727-893b042022ben@googlegroups.com> <hrednRmsHZMNmyf_nZ2dnUU7_8zNnZ2d@giganews.com>
<ccce4f12-08f3-4a18-9211-bc3fa58eafcfn@googlegroups.com> <Xs-dnUWk_Ma_kCf_nZ2dnUU7_8zNnZ2d@giganews.com>
<ead4dce1-03a6-445e-b749-b81b4949f1ban@googlegroups.com> <i42dnfG6dLPshyf_nZ2dnUU7_83NnZ2d@giganews.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <164f1bf0-db9f-451c-b59d-90fb1aa9caa2n@googlegroups.com>
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
From: dbush.mo...@gmail.com (Dennis Bush)
Injection-Date: Mon, 27 Jun 2022 21:04:29 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Dennis Bush - Mon, 27 Jun 2022 21:04 UTC

On Monday, June 27, 2022 at 5:00:41 PM UTC-4, olcott wrote:
> On 6/27/2022 3:07 PM, Dennis Bush wrote:
> > On Monday, June 27, 2022 at 4:03:53 PM UTC-4, olcott wrote:
> >> On 6/27/2022 2:39 PM, Dennis Bush wrote:
> >>> On Monday, June 27, 2022 at 3:35:53 PM UTC-4, olcott wrote:
> >>>> On 6/27/2022 2:13 PM, Dennis Bush wrote:
> >>>>> On Monday, June 27, 2022 at 3:02:47 PM UTC-4, olcott wrote:
> >>>>>> On 6/27/2022 1:51 PM, Dennis Bush wrote:
> >>>>>>> On Monday, June 27, 2022 at 2:41:50 PM UTC-4, olcott wrote:
> >>>>>>>> On 6/27/2022 1:08 PM, Dennis Bush wrote:
> >>>>>>>>> On Monday, June 27, 2022 at 1:59:58 PM UTC-4, olcott wrote:
> >>>>>>>>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
> >>>>>>>>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
> >>>>>>>>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
> >>>>>>>>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
> >>>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
> >>>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
> >>>>>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>>>>>>>> *This is the outline of the complete refutation*
> >>>>>>>>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
> >>>>>>>>>>>>>>>>>>>> never reaches the "ret" instruction of P.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
> >>>>>>>>>>>>>>>>>>>> the semantics of the x86 language.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
> >>>>>>>>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> H does not perform this mapping.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> void P(u32 x)
> >>>>>>>>>>>>>>>>>>>> {
> >>>>>>>>>>>>>>>>>>>> if (H(x, x))
> >>>>>>>>>>>>>>>>>>>> HERE: goto HERE;
> >>>>>>>>>>>>>>>>>>>> return;
> >>>>>>>>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> int main()
> >>>>>>>>>>>>>>>>>>>> {
> >>>>>>>>>>>>>>>>>>>> P(P);
> >>>>>>>>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> _P()
> >>>>>>>>>>>>>>>>>>>> [000011f0](01) 55 push ebp
> >>>>>>>>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>>>>>>> [000011f6](01) 50 push eax
> >>>>>>>>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>>>>>>> [000011fa](01) 51 push ecx
> >>>>>>>>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
> >>>>>>>>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
> >>>>>>>>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
> >>>>>>>>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
> >>>>>>>>>>>>>>>>>>>> [00001209](01) 5d pop ebp
> >>>>>>>>>>>>>>>>>>>> [0000120a](01) c3 ret
> >>>>>>>>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> _main()
> >>>>>>>>>>>>>>>>>>>> [00001210](01) 55 push ebp
> >>>>>>>>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
> >>>>>>>>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
> >>>>>>>>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
> >>>>>>>>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
> >>>>>>>>>>>>>>>>>>>> [00001222](01) 5d pop ebp
> >>>>>>>>>>>>>>>>>>>> [00001223](01) c3 ret
> >>>>>>>>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> machine stack stack machine assembly
> >>>>>>>>>>>>>>>>>>>> address address data code language
> >>>>>>>>>>>>>>>>>>>> ======== ======== ======== ========= =============
> >>>>>>>>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
> >>>>>>>>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
> >>>>>>>>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
> >>>>>>>>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
> >>>>>>>>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
> >>>>>>>>>>>>>>>>>>>> Address_of_H:1020
> >>>>>>>>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
> >>>>>>>>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
> >>>>>>>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
> >>>>>>>>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
> >>>>>>>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
> >>>>>>>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
> >>>>>>>>>>>>>>>>>>>> recursive emulation.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> FALSE. P contains these instructions:
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
> >>>>>>>>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
> >>>>>>>>>>>>>>>>>>> goto END_OF_CODE;
> >>>>>>>>>>>>>>>>>>> return 0; // Does not halt
> >>>>>>>>>>>>>>>>>>> END_OF_CODE:
> >>>>>>>>>>>>>>>>>>> return 1; // Input has normally terminated
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
> >>>>>>>>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
> >>>>>>>>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
> >>>>>>>>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
> >>>>>>>>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
> >>>>>>>>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
> >>>>>>>>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
> >>>>>>>>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
> >>>>>>>>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
> >>>>>>>>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
> >>>>>>>>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
> >>>>>>>>>>>>>>>>>> input never reaches the the "ret" instruction of P.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Repeating your original point.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P)..
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Again, repeating your original point.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
> >>>>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>>>>>>>> Therefore H(P,P)==0 is correct.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> And again, repeating your original point.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
> >>>>>>>>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
> >>>>>>>>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
> >>>>>>>>>>>>>>>> never reach the final state "ret" instruction of this input.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>>>>>>>> First of all I am not talking about UTM's.
> >>>>>>>>>>>>>> I am talking about x86 emulation.
> >>>>>>>>>>>>>> Try to encode what you mean, here is my guess:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> void P(u32 x)
> >>>>>>>>>>>>>> {
> >>>>>>>>>>>>>> if (emulate_x86(x, x))
> >>>>>>>>>>>>>> HERE: goto HERE;
> >>>>>>>>>>>>>> return;
> >>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> int main()
> >>>>>>>>>>>>>> {
> >>>>>>>>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
> >>>>>>>>>>>>>> }
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> void UTM(u32 x, u32 y)
> >>>>>>>>>>>>> {
> >>>>>>>>>>>>> x(y)
> >>>>>>>>>>>>> }
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
> >>>>>>>>>>>>>
> >>>>>>>>>>>> A simulating halt decider correctly simulates its input until it
> >>>>>>>>>>>> correctly determines that this simulated input would never reach its
> >>>>>>>>>>>> final state.
> >>>>>>>>>>>
> >>>>>>>>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
> >>>>>>>>>>>
> >>>>>>>>>> The semantics of the x86 language conclusively proves that H(P,P)
> >>>>>>>>>> correctly determines/predicts that its complete and correct x86
> >>>>>>>>>> emulation of its input would never reach the "ret" instruction of P.
> >>>>>>>>>
> >>>>>>>>> As previously stated, this is nonsense. Failure to explain *in detail* why the below is wrong will be taken as an admission that it is correct.
> >>>>>>>>>
> >>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> >>>>>>>>>
> >>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> >>>>>>>> I NEVER SAID that H does a complete and correct simulation of its input.
> >>>>>>>
> >>>>>>> Yes you did:
> >>>>>>>
> >>>>>>>> a) The complete and correct x86 emulation of the input to H(P,P) by H never reaches the "ret" instruction of P.
> >>>>>>>
> >>>>>> This does not say that H does a complete emulation.
> >>>>>> A simulating halt decider correctly simulates its input until it
> >>>>>> correctly determines that this simulated input would never reach its
> >>>>>> final state.
> >>>>>
> >>>>> Which in the case of H(P,P) it doesn't since the correctly simulated input i.e. UTM(P,P) halts. H gets the wrong answer because it aborts too soon.
> >>>>>
> >>>>>> _Infinite_Loop()
> >>>>>> [000015b8](01) 55 push ebp
> >>>>>> [000015b9](02) 8bec mov ebp,esp
> >>>>>> [000015bb](02) ebfe jmp 000015bb
> >>>>>> [000015bd](01) 5d pop ebp
> >>>>>> [000015be](01) c3 ret
> >>>>>> Size in bytes:(0007) [000015be]
> >>>>>>
> >>>>>> The complete and correct x86 emulation of the input to H0(Infinite_Loop)
> >>>>>> by H0 never reaches the "ret" instruction of Infinite_Loop.
> >>>>>
> >>>>> If H0 *actually* does a complete and correct emulation, then yes.
> >>>> void Infinite_Loop()
> >>>> {
> >>>> HERE: goto HERE;
> >>>> }
> >>>>
> >>>> You are not bright enough to tell that an infinite loop doesn't stop
> >>>> running?
> >>>
> >>> My point was that if H0 does in fact do a correct and complete simulation then the behavior of H0(Infinite_Loop)
> >> You didn't notice that it is ridiculously stupid to think that an
> >> infinite loop can be completely simulated?
> >
> > It can, by a simulator that *never* aborts.
> >
> > If H0 does in fact do a correct and complete simulation by never aborting then the behavior of H0(Infinite_Loop) is a source of truth for H(Infinite_Loop). H(P,P) is not a source of truth for H(P,P) because H does not do a correct and complete simulation. UTM(P,P) does and it halts, so H(P,P)==0 is wrong
> When you say that *only* an actual correct and complete simulation of an
> input correctly predicts the behavior the complete and correct
> simulation of this input


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<pcudnZlH9bNmgSf_nZ2dnUU7_83NnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35047&group=comp.theory#35047

  copy link   Newsgroups: comp.theory sci.logic sci.math
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 27 Jun 2022 16:11:23 -0500
Date: Mon, 27 Jun 2022 16:11:22 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
Content-Language: en-US
Newsgroups: comp.theory,sci.logic,sci.math
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com>
<j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com>
<qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com>
<YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com>
<f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com>
<Sv-dnX5Vh499eyT_nZ2dnUU7_8zNnZ2d@giganews.com>
<fc96a583-3a51-45fd-8275-4bc8aaca8fc0n@googlegroups.com>
<Lfudna-pu95HbyT_nZ2dnUU7_83NnZ2d@giganews.com>
<8bca30ba-3f3f-4b76-b401-504b4873e55en@googlegroups.com>
<c5e0f904-cd76-493c-8e40-4ceee0fdb605n@googlegroups.com>
<s8ednRTcbPnnhSf_nZ2dnUU7_83NnZ2d@giganews.com>
<71b90384-d502-4a24-a1a7-b6f7548e0ebbn@googlegroups.com>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <71b90384-d502-4a24-a1a7-b6f7548e0ebbn@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <pcudnZlH9bNmgSf_nZ2dnUU7_83NnZ2d@giganews.com>
Lines: 273
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-nO79ioKR6zw8L9i/aoaekqBpDlnkPthJ/RUHSn+1pu5+R62i2RSQtB9fPv/PO70pbeAgsQNXUTS/gsw!FVei8oYZasjb67fvHirIolIOPkuoGY+pRUphvnQHY7gyE3kNf4S6VU0QvPTUOZGN/wI6BKaaSSxS
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 16379
 by: olcott - Mon, 27 Jun 2022 21:11 UTC

On 6/27/2022 4:02 PM, Dennis Bush wrote:
> On Monday, June 27, 2022 at 4:52:17 PM UTC-4, olcott wrote:
>> On 6/27/2022 2:45 PM, Dennis Bush wrote:
>>> On Monday, June 27, 2022 at 2:13:44 PM UTC-4, Dennis Bush wrote:
>>>> On Monday, June 27, 2022 at 2:11:45 PM UTC-4, olcott wrote:
>>>>> On 6/27/2022 1:03 PM, Dennis Bush wrote:
>>>>>> On Monday, June 27, 2022 at 1:20:39 PM UTC-4, olcott wrote:
>>>>>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
>>>>>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
>>>>>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
>>>>>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
>>>>>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
>>>>>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
>>>>>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
>>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
>>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>>>>> *This is the outline of the complete refutation*
>>>>>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
>>>>>>>>>>>>>>>>> never reaches the "ret" instruction of P.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
>>>>>>>>>>>>>>>>> the semantics of the x86 language.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
>>>>>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> H does not perform this mapping.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> void P(u32 x)
>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>> if (H(x, x))
>>>>>>>>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>>>>>>>>> return;
>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>> P(P);
>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> _P()
>>>>>>>>>>>>>>>>> [000011f0](01) 55 push ebp
>>>>>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
>>>>>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>>> [000011f6](01) 50 push eax
>>>>>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>>> [000011fa](01) 51 push ecx
>>>>>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
>>>>>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
>>>>>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
>>>>>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
>>>>>>>>>>>>>>>>> [00001209](01) 5d pop ebp
>>>>>>>>>>>>>>>>> [0000120a](01) c3 ret
>>>>>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> _main()
>>>>>>>>>>>>>>>>> [00001210](01) 55 push ebp
>>>>>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
>>>>>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
>>>>>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
>>>>>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
>>>>>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
>>>>>>>>>>>>>>>>> [00001222](01) 5d pop ebp
>>>>>>>>>>>>>>>>> [00001223](01) c3 ret
>>>>>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> machine stack stack machine assembly
>>>>>>>>>>>>>>>>> address address data code language
>>>>>>>>>>>>>>>>> ======== ======== ======== ========= =============
>>>>>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
>>>>>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
>>>>>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
>>>>>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
>>>>>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
>>>>>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
>>>>>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
>>>>>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
>>>>>>>>>>>>>>>>> Address_of_H:1020
>>>>>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
>>>>>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
>>>>>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
>>>>>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
>>>>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
>>>>>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
>>>>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
>>>>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
>>>>>>>>>>>>>>>>> recursive emulation.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> FALSE. P contains these instructions:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
>>>>>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
>>>>>>>>>>>>>>>> goto END_OF_CODE;
>>>>>>>>>>>>>>>> return 0; // Does not halt
>>>>>>>>>>>>>>>> END_OF_CODE:
>>>>>>>>>>>>>>>> return 1; // Input has normally terminated
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
>>>>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
>>>>>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
>>>>>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
>>>>>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
>>>>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
>>>>>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
>>>>>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
>>>>>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
>>>>>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
>>>>>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
>>>>>>>>>>>>>>> input never reaches the the "ret" instruction of P.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Repeating your original point.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Again, repeating your original point.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>>>> Therefore H(P,P)==0 is correct.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> And again, repeating your original point.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
>>>>>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
>>>>>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
>>>>>>>>>>>>> never reach the final state "ret" instruction of this input.
>>>>>>>>>>>>
>>>>>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>>> First of all I am not talking about UTM's.
>>>>>>>>>>> I am talking about x86 emulation.
>>>>>>>>>>> Try to encode what you mean, here is my guess:
>>>>>>>>>>>
>>>>>>>>>>> void P(u32 x)
>>>>>>>>>>> {
>>>>>>>>>>> if (emulate_x86(x, x))
>>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>>> return;
>>>>>>>>>>> }
>>>>>>>>>>>
>>>>>>>>>>> int main()
>>>>>>>>>>> {
>>>>>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
>>>>>>>>>>> }
>>>>>>>>>>
>>>>>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
>>>>>>>>>>
>>>>>>>>>> void UTM(u32 x, u32 y)
>>>>>>>>>> {
>>>>>>>>>> x(y)
>>>>>>>>>> }
>>>>>>>>>>
>>>>>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
>>>>>>>>>>
>>>>>>>>> A simulating halt decider correctly simulates its input until it
>>>>>>>>> correctly determines that this simulated input would never reach its
>>>>>>>>> final state.
>>>>>>>>
>>>>>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
>>>>>>>>
>>>>>>> Every simulating decider that correctly simulates its input until it
>>>>>>> correctly determines that this simulated input would never reach its
>>>>>>> final state correctly determines the halt status of this input.
>>>>>>
>>>>>> And H isn't such a decider, because it does not correctly determine that the input to H(P,P) would never halt as demonstrated by UTM(P,P) halting.
>>>>>>
>>>>>> The specification for H:
>>>>>>
>>>>>> H(x,y)==0 if and only if x(y) does not halt, and
>>>>>> H(x,y)==1 if and only if x(y) halts.
>>>>>>
>>>>>> H does not meet the specification.
>>>>>>
>>>>> The spec is provably incorrect in this case:
>>>> A spec can't be incorrect. It just is. If it can't be satisfied, then that validates the halting problem proofs that say it can't be satisfied.
>>>
>>>
>>> No response to this I see. So you agree that your H does not meet the above spec that the halting problem requires?
>> You are just playing word games so I will use a different word:
>> "criterion measure".
>> A halt decider must compute the mapping from its inputs to an accept or
>> reject state on the basis of the actual behavior that is actually
>> specified by these inputs.
>
> As per this specification:
>
> H(x,y)==0 if and only if x(y) does not halt, and
> H(x,y)==1 if and only if x(y) halts
>
> Which means the actual behavior of the actual input to H(P,P) is defined to be the behavior of P(P).
>
> Remember, the halting problem is ultimately about algorithms, not some simulator's simulation of it.
>
> This also means that if the result of H(P,P) doesn't match the behavior of P(P) then H is wrong by definition.
>
>
>> P(P) is provably not the actual behavior of the actual input,
>
> If you mean that H(P,P) can't simulate its input to a final state, then any simulator that aborts its input for any reason is necessarily correct, which is clearly nonsense.


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<pcudnZhH9bMJgCf_nZ2dnUU7_81g4p2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35048&group=comp.theory#35048

  copy link   Newsgroups: comp.theory sci.logic sci.math
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 27 Jun 2022 16:13:56 -0500
Date: Mon, 27 Jun 2022 16:13:55 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
Content-Language: en-US
Newsgroups: comp.theory,sci.logic,sci.math
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com>
<YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com>
<f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com>
<q4CdnWm9zL2KbST_nZ2dnUU7_8zNnZ2d@giganews.com>
<9f0c8dcb-ae3a-47bf-9093-4e4d9377dc47n@googlegroups.com>
<68ednUyP7tp6ZCT_nZ2dnUU7_8zNnZ2d@giganews.com>
<995fecc1-7fc4-4b40-8d68-fd74df13efefn@googlegroups.com>
<s7ednVfn1vRNYyT_nZ2dnUU7_83NnZ2d@giganews.com>
<b9d6501d-9279-4862-b727-893b042022ben@googlegroups.com>
<hrednRmsHZMNmyf_nZ2dnUU7_8zNnZ2d@giganews.com>
<ccce4f12-08f3-4a18-9211-bc3fa58eafcfn@googlegroups.com>
<Xs-dnUWk_Ma_kCf_nZ2dnUU7_8zNnZ2d@giganews.com>
<ead4dce1-03a6-445e-b749-b81b4949f1ban@googlegroups.com>
<i42dnfG6dLPshyf_nZ2dnUU7_83NnZ2d@giganews.com>
<164f1bf0-db9f-451c-b59d-90fb1aa9caa2n@googlegroups.com>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <164f1bf0-db9f-451c-b59d-90fb1aa9caa2n@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <pcudnZhH9bMJgCf_nZ2dnUU7_81g4p2d@giganews.com>
Lines: 297
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-bglNLjPYKJQAfPSdw0eUtpxuTvOo7N1L6CY+V4InZXUhXRHKQhkcNI572bPnd0Cd232SPWWQ5BWWkeL!RhwCILyEay/33C36Q0NUMKmRwLV3iCWqgrnpdwTCnkzK+dSzudu5jKpbc6fEKIrfH/lsfRSdUseA
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 19183
 by: olcott - Mon, 27 Jun 2022 21:13 UTC

On 6/27/2022 4:04 PM, Dennis Bush wrote:
> On Monday, June 27, 2022 at 5:00:41 PM UTC-4, olcott wrote:
>> On 6/27/2022 3:07 PM, Dennis Bush wrote:
>>> On Monday, June 27, 2022 at 4:03:53 PM UTC-4, olcott wrote:
>>>> On 6/27/2022 2:39 PM, Dennis Bush wrote:
>>>>> On Monday, June 27, 2022 at 3:35:53 PM UTC-4, olcott wrote:
>>>>>> On 6/27/2022 2:13 PM, Dennis Bush wrote:
>>>>>>> On Monday, June 27, 2022 at 3:02:47 PM UTC-4, olcott wrote:
>>>>>>>> On 6/27/2022 1:51 PM, Dennis Bush wrote:
>>>>>>>>> On Monday, June 27, 2022 at 2:41:50 PM UTC-4, olcott wrote:
>>>>>>>>>> On 6/27/2022 1:08 PM, Dennis Bush wrote:
>>>>>>>>>>> On Monday, June 27, 2022 at 1:59:58 PM UTC-4, olcott wrote:
>>>>>>>>>>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
>>>>>>>>>>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
>>>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
>>>>>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
>>>>>>>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
>>>>>>>>>>>>>>>>>>>>>> *This is the outline of the complete refutation*
>>>>>>>>>>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
>>>>>>>>>>>>>>>>>>>>>> never reaches the "ret" instruction of P.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
>>>>>>>>>>>>>>>>>>>>>> the semantics of the x86 language.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
>>>>>>>>>>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> H does not perform this mapping.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> void P(u32 x)
>>>>>>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>>>>>> if (H(x, x))
>>>>>>>>>>>>>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>>>>>>>>>>>>>> return;
>>>>>>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>>>>>> P(P);
>>>>>>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> _P()
>>>>>>>>>>>>>>>>>>>>>> [000011f0](01) 55 push ebp
>>>>>>>>>>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>>>>>>>> [000011f6](01) 50 push eax
>>>>>>>>>>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>>>>>>>> [000011fa](01) 51 push ecx
>>>>>>>>>>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
>>>>>>>>>>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
>>>>>>>>>>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
>>>>>>>>>>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
>>>>>>>>>>>>>>>>>>>>>> [00001209](01) 5d pop ebp
>>>>>>>>>>>>>>>>>>>>>> [0000120a](01) c3 ret
>>>>>>>>>>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> _main()
>>>>>>>>>>>>>>>>>>>>>> [00001210](01) 55 push ebp
>>>>>>>>>>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
>>>>>>>>>>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
>>>>>>>>>>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
>>>>>>>>>>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
>>>>>>>>>>>>>>>>>>>>>> [00001222](01) 5d pop ebp
>>>>>>>>>>>>>>>>>>>>>> [00001223](01) c3 ret
>>>>>>>>>>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> machine stack stack machine assembly
>>>>>>>>>>>>>>>>>>>>>> address address data code language
>>>>>>>>>>>>>>>>>>>>>> ======== ======== ======== ========= =============
>>>>>>>>>>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
>>>>>>>>>>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
>>>>>>>>>>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
>>>>>>>>>>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
>>>>>>>>>>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
>>>>>>>>>>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
>>>>>>>>>>>>>>>>>>>>>> Address_of_H:1020
>>>>>>>>>>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
>>>>>>>>>>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
>>>>>>>>>>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
>>>>>>>>>>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
>>>>>>>>>>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
>>>>>>>>>>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
>>>>>>>>>>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
>>>>>>>>>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
>>>>>>>>>>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
>>>>>>>>>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
>>>>>>>>>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
>>>>>>>>>>>>>>>>>>>>>> recursive emulation.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> FALSE. P contains these instructions:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
>>>>>>>>>>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
>>>>>>>>>>>>>>>>>>>>> goto END_OF_CODE;
>>>>>>>>>>>>>>>>>>>>> return 0; // Does not halt
>>>>>>>>>>>>>>>>>>>>> END_OF_CODE:
>>>>>>>>>>>>>>>>>>>>> return 1; // Input has normally terminated
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
>>>>>>>>>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
>>>>>>>>>>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
>>>>>>>>>>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
>>>>>>>>>>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
>>>>>>>>>>>>>>>>>>>>>> executed P
>>>>>>>>>>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
>>>>>>>>>>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
>>>>>>>>>>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
>>>>>>>>>>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
>>>>>>>>>>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
>>>>>>>>>>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
>>>>>>>>>>>>>>>>>>>> input never reaches the the "ret" instruction of P.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Repeating your original point.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Again, repeating your original point.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
>>>>>>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
>>>>>>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
>>>>>>>>>>>>>>>>>>>> specified by these inputs.
>>>>>>>>>>>>>>>>>>>> Therefore H(P,P)==0 is correct.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> And again, repeating your original point.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
>>>>>>>>>>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
>>>>>>>>>>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
>>>>>>>>>>>>>>>>>> never reach the final state "ret" instruction of this input.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
>>>>>>>>>>>>>>>> First of all I am not talking about UTM's.
>>>>>>>>>>>>>>>> I am talking about x86 emulation.
>>>>>>>>>>>>>>>> Try to encode what you mean, here is my guess:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> void P(u32 x)
>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>> if (emulate_x86(x, x))
>>>>>>>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>>>>>>>> return;
>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> void UTM(u32 x, u32 y)
>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>> x(y)
>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> A simulating halt decider correctly simulates its input until it
>>>>>>>>>>>>>> correctly determines that this simulated input would never reach its
>>>>>>>>>>>>>> final state.
>>>>>>>>>>>>>
>>>>>>>>>>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
>>>>>>>>>>>>>
>>>>>>>>>>>> The semantics of the x86 language conclusively proves that H(P,P)
>>>>>>>>>>>> correctly determines/predicts that its complete and correct x86
>>>>>>>>>>>> emulation of its input would never reach the "ret" instruction of P.
>>>>>>>>>>>
>>>>>>>>>>> As previously stated, this is nonsense. Failure to explain *in detail* why the below is wrong will be taken as an admission that it is correct.
>>>>>>>>>>>
>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
>>>>>>>>>>>
>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
>>>>>>>>>> I NEVER SAID that H does a complete and correct simulation of its input.
>>>>>>>>>
>>>>>>>>> Yes you did:
>>>>>>>>>
>>>>>>>>>> a) The complete and correct x86 emulation of the input to H(P,P) by H never reaches the "ret" instruction of P.
>>>>>>>>>
>>>>>>>> This does not say that H does a complete emulation.
>>>>>>>> A simulating halt decider correctly simulates its input until it
>>>>>>>> correctly determines that this simulated input would never reach its
>>>>>>>> final state.
>>>>>>>
>>>>>>> Which in the case of H(P,P) it doesn't since the correctly simulated input i.e. UTM(P,P) halts. H gets the wrong answer because it aborts too soon.
>>>>>>>
>>>>>>>> _Infinite_Loop()
>>>>>>>> [000015b8](01) 55 push ebp
>>>>>>>> [000015b9](02) 8bec mov ebp,esp
>>>>>>>> [000015bb](02) ebfe jmp 000015bb
>>>>>>>> [000015bd](01) 5d pop ebp
>>>>>>>> [000015be](01) c3 ret
>>>>>>>> Size in bytes:(0007) [000015be]
>>>>>>>>
>>>>>>>> The complete and correct x86 emulation of the input to H0(Infinite_Loop)
>>>>>>>> by H0 never reaches the "ret" instruction of Infinite_Loop.
>>>>>>>
>>>>>>> If H0 *actually* does a complete and correct emulation, then yes.
>>>>>> void Infinite_Loop()
>>>>>> {
>>>>>> HERE: goto HERE;
>>>>>> }
>>>>>>
>>>>>> You are not bright enough to tell that an infinite loop doesn't stop
>>>>>> running?
>>>>>
>>>>> My point was that if H0 does in fact do a correct and complete simulation then the behavior of H0(Infinite_Loop)
>>>> You didn't notice that it is ridiculously stupid to think that an
>>>> infinite loop can be completely simulated?
>>>
>>> It can, by a simulator that *never* aborts.
>>>
>>> If H0 does in fact do a correct and complete simulation by never aborting then the behavior of H0(Infinite_Loop) is a source of truth for H(Infinite_Loop). H(P,P) is not a source of truth for H(P,P) because H does not do a correct and complete simulation. UTM(P,P) does and it halts, so H(P,P)==0 is wrong
>> When you say that *only* an actual correct and complete simulation of an
>> input correctly predicts the behavior the complete and correct
>> simulation of this input
>
> No, I'm saying that only the correct and complete simulation of an input defines what the correct answer is. UTM(Infinite_Loop) does not halt, so H(Infinite_Loop)==0 is correct. UTM(P,P) does halt, so H(P,P)==0 is wrong.
>


Click here to read the complete article
Re: Conquering the last rebuttal to H(P,P)==0 refutation of the halting problem proofs

<f0391029-35e5-4e6f-90f1-dfdf23672b9an@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=35049&group=comp.theory#35049

  copy link   Newsgroups: comp.theory
X-Received: by 2002:a5d:5888:0:b0:21b:cc1f:c8e3 with SMTP id n8-20020a5d5888000000b0021bcc1fc8e3mr8048932wrf.263.1656364444806;
Mon, 27 Jun 2022 14:14:04 -0700 (PDT)
X-Received: by 2002:a0d:d914:0:b0:31b:a963:f4a1 with SMTP id
b20-20020a0dd914000000b0031ba963f4a1mr9777322ywe.307.1656364443958; Mon, 27
Jun 2022 14:14:03 -0700 (PDT)
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!feeder1.cambriumusenet.nl!feed.tweak.nl!209.85.128.88.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.theory
Date: Mon, 27 Jun 2022 14:14:03 -0700 (PDT)
In-Reply-To: <pcudnZlH9bNmgSf_nZ2dnUU7_83NnZ2d@giganews.com>
Injection-Info: google-groups.googlegroups.com; posting-host=71.168.165.242; posting-account=ejFcQgoAAACAt5i0VbkATkR2ACWdgADD
NNTP-Posting-Host: 71.168.165.242
References: <PqadncNqadjPDST_nZ2dnUU7_8zNnZ2d@giganews.com>
<13d3c11d-2219-4232-9aec-63167655b803n@googlegroups.com> <j4udnXhGprK9AiT_nZ2dnUU7_83NnZ2d@giganews.com>
<2f493c95-96ca-4f1a-9467-092cd1eb9d7cn@googlegroups.com> <qI6dnRfaBtBaPiT_nZ2dnUU7_83NnZ2d@giganews.com>
<ce3d399e-d163-48e1-a679-8e2b27bdad94n@googlegroups.com> <YNKdnT0wGczrOiT_nZ2dnUU7_8zNnZ2d@giganews.com>
<62035ef4-5a47-47bc-8997-38a3498d26d1n@googlegroups.com> <f5adnZz_oeLyLST_nZ2dnUU7_8zNnZ2d@giganews.com>
<c4f7fa35-d1a7-4e55-b230-4253bf0a7256n@googlegroups.com> <Sv-dnX5Vh499eyT_nZ2dnUU7_8zNnZ2d@giganews.com>
<fc96a583-3a51-45fd-8275-4bc8aaca8fc0n@googlegroups.com> <Lfudna-pu95HbyT_nZ2dnUU7_83NnZ2d@giganews.com>
<8bca30ba-3f3f-4b76-b401-504b4873e55en@googlegroups.com> <c5e0f904-cd76-493c-8e40-4ceee0fdb605n@googlegroups.com>
<s8ednRTcbPnnhSf_nZ2dnUU7_83NnZ2d@giganews.com> <71b90384-d502-4a24-a1a7-b6f7548e0ebbn@googlegroups.com>
<pcudnZlH9bNmgSf_nZ2dnUU7_83NnZ2d@giganews.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <f0391029-35e5-4e6f-90f1-dfdf23672b9an@googlegroups.com>
Subject: Re: Conquering the last rebuttal to H(P,P)==0 refutation of the
halting problem proofs
From: dbush.mo...@gmail.com (Dennis Bush)
Injection-Date: Mon, 27 Jun 2022 21:14:04 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Dennis Bush - Mon, 27 Jun 2022 21:14 UTC

On Monday, June 27, 2022 at 5:11:30 PM UTC-4, olcott wrote:
> On 6/27/2022 4:02 PM, Dennis Bush wrote:
> > On Monday, June 27, 2022 at 4:52:17 PM UTC-4, olcott wrote:
> >> On 6/27/2022 2:45 PM, Dennis Bush wrote:
> >>> On Monday, June 27, 2022 at 2:13:44 PM UTC-4, Dennis Bush wrote:
> >>>> On Monday, June 27, 2022 at 2:11:45 PM UTC-4, olcott wrote:
> >>>>> On 6/27/2022 1:03 PM, Dennis Bush wrote:
> >>>>>> On Monday, June 27, 2022 at 1:20:39 PM UTC-4, olcott wrote:
> >>>>>>> On 6/27/2022 12:03 PM, Dennis Bush wrote:
> >>>>>>>> On Monday, June 27, 2022 at 9:28:22 AM UTC-4, olcott wrote:
> >>>>>>>>> On 6/27/2022 7:58 AM, Dennis Bush wrote:
> >>>>>>>>>> On Monday, June 27, 2022 at 8:50:05 AM UTC-4, olcott wrote:
> >>>>>>>>>>> On 6/27/2022 7:40 AM, Dennis Bush wrote:
> >>>>>>>>>>>> On Monday, June 27, 2022 at 8:34:22 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>> On 6/27/2022 7:26 AM, Dennis Bush wrote:
> >>>>>>>>>>>>>> On Monday, June 27, 2022 at 8:14:31 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>>> On 6/27/2022 6:57 AM, Dennis Bush wrote:
> >>>>>>>>>>>>>>>> On Monday, June 27, 2022 at 7:11:21 AM UTC-4, olcott wrote:
> >>>>>>>>>>>>>>>>> *This is the outline of the complete refutation*
> >>>>>>>>>>>>>>>>> *of the only rebuttal that anyone has left*
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> (a) The complete and correct x86 emulation of the input to H(P,P) by H
> >>>>>>>>>>>>>>>>> never reaches the "ret" instruction of P.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> It is known that H aborts its simulation and returns 0. That means that H *by definition* does not perform a complete and correct emulation. And since H (if it was constructed correctly) is a pure function of its inputs, it will ALWAYS return the same return for a given input.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> To state that H aborts *and* does a complete and correct simulation is simply nonsense.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> What *does* perform a complete and correct emulation of the input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> (b) The direct execution of P(P) does reach its "ret" instruction.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> The above two are proven to be verified facts entirely on the basis of
> >>>>>>>>>>>>>>>>> the semantics of the x86 language.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> A nonsense statement can't be a "fact", verified or otherwise.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Which for H(P,P) is BY DEFINITION is the behavior of P(P). The halting problem says that H MUST implement the following mapping (i.e. the halting function):
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> H(x,y)==1 if and only if x(y) halts, and
> >>>>>>>>>>>>>>>> H(x,y)==0 if and only if x(y) does not halt.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> H does not perform this mapping.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> P(P) is provably not the actual behavior of the actual input.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> It is BY DEFINITION. So if H comes up with something different that means it did something wrong, specifically it aborted a halting computation too soon.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> void P(u32 x)
> >>>>>>>>>>>>>>>>> {
> >>>>>>>>>>>>>>>>> if (H(x, x))
> >>>>>>>>>>>>>>>>> HERE: goto HERE;
> >>>>>>>>>>>>>>>>> return;
> >>>>>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> int main()
> >>>>>>>>>>>>>>>>> {
> >>>>>>>>>>>>>>>>> P(P);
> >>>>>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> _P()
> >>>>>>>>>>>>>>>>> [000011f0](01) 55 push ebp
> >>>>>>>>>>>>>>>>> [000011f1](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>> [000011f3](03) 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>>>> [000011f6](01) 50 push eax
> >>>>>>>>>>>>>>>>> [000011f7](03) 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>>>> [000011fa](01) 51 push ecx
> >>>>>>>>>>>>>>>>> [000011fb](05) e820feffff call 00001020
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> [00001200](03) 83c408 add esp,+08
> >>>>>>>>>>>>>>>>> [00001203](02) 85c0 test eax,eax
> >>>>>>>>>>>>>>>>> [00001205](02) 7402 jz 00001209
> >>>>>>>>>>>>>>>>> [00001207](02) ebfe jmp 00001207
> >>>>>>>>>>>>>>>>> [00001209](01) 5d pop ebp
> >>>>>>>>>>>>>>>>> [0000120a](01) c3 ret
> >>>>>>>>>>>>>>>>> Size in bytes:(0027) [0000120a]
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> _main()
> >>>>>>>>>>>>>>>>> [00001210](01) 55 push ebp
> >>>>>>>>>>>>>>>>> [00001211](02) 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>> [00001213](05) 68f0110000 push 000011f0
> >>>>>>>>>>>>>>>>> [00001218](05) e8d3ffffff call 000011f0
> >>>>>>>>>>>>>>>>> [0000121d](03) 83c404 add esp,+04
> >>>>>>>>>>>>>>>>> [00001220](02) 33c0 xor eax,eax
> >>>>>>>>>>>>>>>>> [00001222](01) 5d pop ebp
> >>>>>>>>>>>>>>>>> [00001223](01) c3 ret
> >>>>>>>>>>>>>>>>> Size in bytes:(0020) [00001223]
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> machine stack stack machine assembly
> >>>>>>>>>>>>>>>>> address address data code language
> >>>>>>>>>>>>>>>>> ======== ======== ======== ========= =============
> >>>>>>>>>>>>>>>>> [00001210][00101fba][00000000] 55 push ebp
> >>>>>>>>>>>>>>>>> [00001211][00101fba][00000000] 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>> [00001213][00101fb6][000011f0] 68f0110000 push 000011f0 // push P
> >>>>>>>>>>>>>>>>> [00001218][00101fb2][0000121d] e8d3ffffff call 000011f0 // call P
> >>>>>>>>>>>>>>>>> [000011f0][00101fae][00101fba] 55 push ebp // enter executed P
> >>>>>>>>>>>>>>>>> [000011f1][00101fae][00101fba] 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>> [000011f3][00101fae][00101fba] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>>>> [000011f6][00101faa][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>>>>> [000011f7][00101faa][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>>>> [000011fa][00101fa6][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>>>>> [000011fb][00101fa2][00001200] e820feffff call 00001020 // call H
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Begin Simulation Execution Trace Stored at:21206e
> >>>>>>>>>>>>>>>>> Address_of_H:1020
> >>>>>>>>>>>>>>>>> [000011f0][0021205a][0021205e] 55 push ebp // enter emulated P
> >>>>>>>>>>>>>>>>> [000011f1][0021205a][0021205e] 8bec mov ebp,esp
> >>>>>>>>>>>>>>>>> [000011f3][0021205a][0021205e] 8b4508 mov eax,[ebp+08]
> >>>>>>>>>>>>>>>>> [000011f6][00212056][000011f0] 50 push eax // push P
> >>>>>>>>>>>>>>>>> [000011f7][00212056][000011f0] 8b4d08 mov ecx,[ebp+08]
> >>>>>>>>>>>>>>>>> [000011fa][00212052][000011f0] 51 push ecx // push P
> >>>>>>>>>>>>>>>>> [000011fb][0021204e][00001200] e820feffff call 00001020 // call emulated H
> >>>>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> H knows its own machine address and on this basis it can easily
> >>>>>>>>>>>>>>>>> examine its stored execution_trace of P (see above) to determine:
> >>>>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called with.
> >>>>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise infinitely
> >>>>>>>>>>>>>>>>> recursive emulation.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> FALSE. P contains these instructions:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> if (Decide_Halting(&execution_trace, &decoded, code_end, &master_state,
> >>>>>>>>>>>>>>>> &slave_state, &slave_stack, Address_of_H, P, I))
> >>>>>>>>>>>>>>>> goto END_OF_CODE;
> >>>>>>>>>>>>>>>> return 0; // Does not halt
> >>>>>>>>>>>>>>>> END_OF_CODE:
> >>>>>>>>>>>>>>>> return 1; // Input has normally terminated
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> That *can* and *do* prevent infinite recursive emulation in a *correct* and *complete* emulation
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is emulated.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> And in doing so it fails to see that the call to H, since H is a computation, will aborts *its* simulation of P and return 0 to the outer P being emulated, which would cause it to halt, making H(P,P)==0 wrong.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> [00001200][00101fae][00101fba] 83c408 add esp,+08 // return to
> >>>>>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>>>>> [00001203][00101fae][00101fba] 85c0 test eax,eax
> >>>>>>>>>>>>>>>>> [00001205][00101fae][00101fba] 7402 jz 00001209
> >>>>>>>>>>>>>>>>> [00001209][00101fb2][0000121d] 5d pop ebp
> >>>>>>>>>>>>>>>>> [0000120a][00101fb6][000011f0] c3 ret // return from
> >>>>>>>>>>>>>>>>> executed P
> >>>>>>>>>>>>>>>>> [0000121d][00101fba][00000000] 83c404 add esp,+04
> >>>>>>>>>>>>>>>>> [00001220][00101fba][00000000] 33c0 xor eax,eax
> >>>>>>>>>>>>>>>>> [00001222][00101fbe][00100000] 5d pop ebp
> >>>>>>>>>>>>>>>>> [00001223][00101fc2][00000000] c3 ret // ret from main
> >>>>>>>>>>>>>>>>> Number of Instructions Executed(878) / 67 = 13 pages
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I've stated in detail why you're wrong. Now you need to explain in detail why I'm wrong.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Failure to do so, which includes simply restating your original point, will be taken as admission that what I've stated is correct.
> >>>>>>>>>>>>>>> H correctly predicts that its complete and correct x86 emulation of its
> >>>>>>>>>>>>>>> input never reaches the the "ret" instruction of P.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Repeating your original point.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> This is the actual behavior of the input to H(P,P).
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> P(P) is not the actual behavior of the input to H(P,P).
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Again, repeating your original point.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Never reaching the "ret" instruction means that P does not halt.
> >>>>>>>>>>>>>>> A halt decider must compute the mapping from its inputs to an accept or
> >>>>>>>>>>>>>>> reject state on the basis of the actual behavior that is actually
> >>>>>>>>>>>>>>> specified by these inputs.
> >>>>>>>>>>>>>>> Therefore H(P,P)==0 is correct.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> And again, repeating your original point.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> So no explanation as to why I'm wrong, just a repetition of your original points.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> That means you accept that what I've said is true, and that H(P,P)==0 is wrong.
> >>>>>>>>>>>>> You rebuttal is based on rejecting the verified fact that a simulating
> >>>>>>>>>>>>> halt decider correctly predicts that its correctly simulated input will
> >>>>>>>>>>>>> never reach the final state "ret" instruction of this input..
> >>>>>>>>>>>>
> >>>>>>>>>>>> FALSE. The correctly simulated input to H(P,P) is UTM(P,P) which halts, therefore H(P,P)==0 is wrong.
> >>>>>>>>>>> First of all I am not talking about UTM's.
> >>>>>>>>>>> I am talking about x86 emulation.
> >>>>>>>>>>> Try to encode what you mean, here is my guess:
> >>>>>>>>>>>
> >>>>>>>>>>> void P(u32 x)
> >>>>>>>>>>> {
> >>>>>>>>>>> if (emulate_x86(x, x))
> >>>>>>>>>>> HERE: goto HERE;
> >>>>>>>>>>> return;
> >>>>>>>>>>> }
> >>>>>>>>>>>
> >>>>>>>>>>> int main()
> >>>>>>>>>>> {
> >>>>>>>>>>> Output("Input_Halts = ", H((u32)P, (u32)P));
> >>>>>>>>>>> }
> >>>>>>>>>>
> >>>>>>>>>> P is a computation and therefore it can't be changed, nor can anything that it calls. I mean UTM(P,P). The simplest way to implement this is:
> >>>>>>>>>>
> >>>>>>>>>> void UTM(u32 x, u32 y)
> >>>>>>>>>> {
> >>>>>>>>>> x(y)
> >>>>>>>>>> }
> >>>>>>>>>>
> >>>>>>>>>> H cannot by definition perform a correct and complete emulation if it aborts, so the input must be passed to something that does, i.e. a UTM, for the source of truth.
> >>>>>>>>>>
> >>>>>>>>> A simulating halt decider correctly simulates its input until it
> >>>>>>>>> correctly determines that this simulated input would never reach its
> >>>>>>>>> final state.
> >>>>>>>>
> >>>>>>>> But H isn't such a decider, because the simulated input does reach a final state when correctly simulated, i.e. by UTM(P,P), therefore H(P,P)==0 is wrong.
> >>>>>>>>
> >>>>>>> Every simulating decider that correctly simulates its input until it
> >>>>>>> correctly determines that this simulated input would never reach its
> >>>>>>> final state correctly determines the halt status of this input.
> >>>>>>
> >>>>>> And H isn't such a decider, because it does not correctly determine that the input to H(P,P) would never halt as demonstrated by UTM(P,P) halting.
> >>>>>>
> >>>>>> The specification for H:
> >>>>>>
> >>>>>> H(x,y)==0 if and only if x(y) does not halt, and
> >>>>>> H(x,y)==1 if and only if x(y) halts.
> >>>>>>
> >>>>>> H does not meet the specification.
> >>>>>>
> >>>>> The spec is provably incorrect in this case:
> >>>> A spec can't be incorrect. It just is. If it can't be satisfied, then that validates the halting problem proofs that say it can't be satisfied.
> >>>
> >>>
> >>> No response to this I see. So you agree that your H does not meet the above spec that the halting problem requires?
> >> You are just playing word games so I will use a different word:
> >> "criterion measure".
> >> A halt decider must compute the mapping from its inputs to an accept or
> >> reject state on the basis of the actual behavior that is actually
> >> specified by these inputs.
> >
> > As per this specification:
> >
> > H(x,y)==0 if and only if x(y) does not halt, and
> > H(x,y)==1 if and only if x(y) halts
> >
> > Which means the actual behavior of the actual input to H(P,P) is defined to be the behavior of P(P).
> >
> > Remember, the halting problem is ultimately about algorithms, not some simulator's simulation of it.
> >
> > This also means that if the result of H(P,P) doesn't match the behavior of P(P) then H is wrong by definition.
> >
> >
> >> P(P) is provably not the actual behavior of the actual input,
> >
> > If you mean that H(P,P) can't simulate its input to a final state, then any simulator that aborts its input for any reason is necessarily correct, which is clearly nonsense.
> The formal mathematical semantics of the x86 language conclusively
> proves that P(P) is not the actual behavior of the actual input to H(P,P)..


Click here to read the complete article
Pages:123456789
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor