Re: 197 page execution trace of DDD correctly simulated by HHH

Liste des GroupesRevenir à s logic 
Sujet : Re: 197 page execution trace of DDD correctly simulated by HHH
De : noreply (at) *nospam* example.com (joes)
Groupes : comp.theory
Date : 28. Jun 2024, 21:18:41
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <v5n2ah$1d3t3$10@i2pn2.org>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
User-Agent : Pan/0.145 (Duplicitous mercenary valetism; d7e168a git.gnome.org/pan2)
Am Fri, 28 Jun 2024 12:53:46 -0500 schrieb olcott:
On 6/28/2024 12:41 PM, joes wrote:
Thanks for leaving the unanswered questions in place, though I’d rather
have you answer them.
I rest my case.

Am Fri, 28 Jun 2024 12:05:18 -0500 schrieb olcott:
On 6/28/2024 11:26 AM, joes wrote:
Am Fri, 28 Jun 2024 10:25:36 -0500 schrieb olcott:
On 6/28/2024 8:14 AM, joes wrote:
Am Thu, 27 Jun 2024 12:30:38 -0500 schrieb olcott:

To the caller DDD, which then returns to its own caller H0, which
returns „halting” to main… hold on.
Why doesn’t the first recursive H return?

H0 must not report on itself, only on DDD. Which you’ve proven
halts.
We don’t care how H0 deviates (i.e. is incorrect) in its
simulation. That would be main {H0(H0(DDD))}.
Can you see the difference?

The behavior of the directly executed DDD() is irrelevant because
that is not the behavior of the input.
What is the input?

In this case the sequence is the line-by-line execution trace of the
behavior of DDD correctly emulated by HHH.
No, the sequence is the behaviour of DDD, period.
The input is not HHH(DDD). See above.

The behavior of this input must include and cannot ignore the
recursive emulation specified by the fact that DDD is calling its
own emulator.
Yes, and the behaviour of H0 is that it produces the exact same
behaviour as DDD.

The call from DDD to HHH(DDD) when N steps of DDD are correctly
emulated by any pure function x86 emulator HHH cannot possibly return.
That you assume that it does against the facts is ridiculous.
I don’t. A simulator doesn’t even need to return. That’s not in
question. A decider however must.
That you keep trying to ignore the fact that DDD calls HHH(DDD)
in recursive simulation is your huge mistake.
WTF? I just agreed with you.

Please reply to my other points.

--
Am Fri, 21 Jun 2024 12:22:04 -0500 schrieb olcott: the logical
impossibility of specifying a halt decider H that correctly reports the
halt status of input D that is defined to do the opposite of whatever
value that H reports.

Date Sujet#  Auteur
21 Sep 24 o 

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal