Re: Who here is too stupid to know that DDD simulated by HHH cannot reach its own return? (typos fixed)

Liste des GroupesRevenir à theory 
Sujet : Re: Who here is too stupid to know that DDD simulated by HHH cannot reach its own return? (typos fixed)
De : polcott333 (at) *nospam* gmail.com (olcott)
Groupes : comp.theory
Date : 07. Aug 2024, 21:50:15
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v90mm7$3bj21$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
User-Agent : Mozilla Thunderbird
On 8/7/2024 2:02 PM, olcott wrote:
On 8/7/2024 1:25 PM, joes wrote:
Am Wed, 07 Aug 2024 08:40:31 -0500 schrieb olcott:
On 8/7/2024 2:22 AM, Mikko wrote:
On 2024-08-05 15:00:12 +0000, olcott said:
On 8/5/2024 2:44 AM, Mikko wrote:
On 2024-08-04 13:11:56 +0000, olcott said:
On 8/4/2024 1:26 AM, Fred. Zwarts wrote:
Op 03.aug.2024 om 17:20 schreef olcott:>>
>
In another message you have said that when HHH simulates itself
simulating DDD is does not simulate itself simulating itself
simulating DDD. You have not told whether it makes a cup of coffee.
Neither action can be seen in the traces you have shown.
>
HHH and HH and the original H have proved that they simulate
themselves simulating DDD, DD and P for three years now.
>
Your trace don't show siulation of exectuion differently from
simulation of simulation of execution.
>
It does but it is too difficult to dig it out of emulations of emulators
emulating inputs.
You could make it clearer by prefixing the simulation level.
>
 Maybe I can do this. it requires a static local, yet this
is only for reporting purposes and does not have an effect
on the computation.
 
None of this was ever really required. We have complete
proof that the second HHH does emulate its DDD correctly
by simply comparing the execution trace that it produces
to the x86 source code of DDD.

 We have had this complete proof for HH/DD and H/P for three
years and everyone simply ignores it. This can only mean:
(a) dishonesty
(b) insufficient technical competence.
 
As soon as the first HHH sees the second DDD about to invoke a third HHH
it aborts the emulation. At this point DDD, the second HHH and the
second DDD all immediately stop running and HHH returns 0 to main.
 
And HHH concludes that the second invocation of itself would somehow
not also abort but run forever, and then returns that itself wouldn't
halt, and halts. ???
>
 void DDD()
{
   HHH(DDD);
   return;
}
 Any expert in C can tell that DDD simulated by HHH cannot
possibly ever reach its own "return" instruction final halt
state.
 Is it possible for someone to have a PhD in computer science
and not have any clue about something as simple as this?
  
--
Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer

Date Sujet#  Auteur
5 Jul 25 o 

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal