Sujet : Re: Any honest person that knows the x86 language can see... predict correctly
De : polcott333 (at) *nospam* gmail.com (olcott)
Groupes : comp.theoryDate : 31. Jul 2024, 17:32:22
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v8doun$1lugu$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14
User-Agent : Mozilla Thunderbird
On 7/31/2024 11:17 AM, joes wrote:
Am Wed, 31 Jul 2024 10:02:26 -0500 schrieb olcott:
On 7/31/2024 9:16 AM, joes wrote:
Am Wed, 31 Jul 2024 05:52:54 -0500 schrieb olcott:
On 7/31/2024 3:54 AM, joes wrote:
Am Tue, 30 Jul 2024 16:13:55 -0500 schrieb olcott:
On 7/30/2024 4:07 PM, joes wrote:
Am Tue, 30 Jul 2024 15:05:54 -0500 schrieb olcott:
On 7/30/2024 1:48 PM, Fred. Zwarts wrote:
Op 30.jul.2024 om 17:14 schreef olcott:
On 7/30/2024 9:51 AM, Fred. Zwarts wrote:
Op 30.jul.2024 om 16:21 schreef olcott:
On 7/30/2024 1:52 AM, Mikko wrote:
On 2024-07-29 14:07:53 +0000, olcott said:
>
I proved otherwise. When the abort code is commented out then it
keeps repeating again and again, thus conclusively proving that is
must be aborted or HHH never halts.
But the abort is not commented out in the running code!
>
I modified the original code by commenting out the abort and it does
endlessly repeat just like HHH correctly predicted.
>
Yes, and that modification makes HHH not call itself
Not at all. It makes HHH stop aborting DDD.
So that HHH and DDD endlessly repeat.
>
Commenting out a section changes the program.
This conclusively proving that this section was required.
When you put in the abort, it also appears in the simulated HHH.
Yet this is unreachable in the same way that in a single file
foot race with everyone going the same speed and everyone
15 feet ahead of the next person that the first person must win.
The outermost HHH sees that it must abort one whole execution
trace sooner than the next inner HHH.
You changed only the inner HHH's, not the outermost one, thus breaking
the recursive simulation.
Not at all. I simply disabled the abort and this resulted in unlimited
repetition non-halting behavior.
You did NOT change all calls to HHH.
I disabled aborting for the whole system and every call.
but a different program. You'd need to also comment out the outermost
abort; then it wouldn't halt, but if you change HHH to abort, you
change all copies of it at the same time (to keep the recursive call
structure).
A program's identity changes with its code. It doesn't matter what I
label it in the source. I can define different functions with the same
name.
To prove that a section of code is required we remove that section and
the resulting endless repetition proves that the abort section was
required to prevent the endless repetition.
Enough said.
Meaning that you agree or still fail to understand?
-- Copyright 2024 Olcott "Talent hits a target no one else can hit; Geniushits a target no one else can see." Arthur Schopenhauer