Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connectionsPath: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: olcott Newsgroups: comp.theory Subject: Re: Can you see that D correctly simulated by H remains stuck in recursive simulation? Date: Fri, 24 May 2024 12:16:31 -0500 Organization: A noiseless patient Spider Lines: 58 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Fri, 24 May 2024 19:16:32 +0200 (CEST) Injection-Info: dont-email.me; posting-host="853a48eea7a3e841565c364baea8e5bf"; logging-data="2549243"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18ObO5LANxyq74WbdcE9/KV" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:+Wd/YKJVy3lCv0kNrct712qjrmU= In-Reply-To: Content-Language: en-US Bytes: 3327 On 5/24/2024 4:03 AM, Mikko wrote: > On 2024-05-23 17:04:49 +0000, olcott said: > >> typedef int (*ptr)();  // ptr is pointer to int function in C >> 00       int H(ptr p, ptr i); >> 01       int D(ptr p) >> 02       { >> 03         int Halt_Status = H(p, p); >> 04         if (Halt_Status) >> 05           HERE: goto HERE; >> 06         return Halt_Status; >> 07       } >> 08 >> 09       int main() >> 10       { >> 11         H(D,D); >> 12         return 0; >> 13       } >> >> The above template refers to an infinite set of H/D pairs where D is >> correctly simulated by pure function H. This was done because many >> reviewers used the shell game ploy to endlessly switch which H/D pair >> was being referred to. >> >> *Correct Simulation Defined* >>     This is provided because every reviewer had a different notion of >>     correct simulation that diverges from this notion. >> >>     A simulator is an x86 emulator that correctly emulates at least one >>     of the x86 instructions of D in the order specified by the x86 >>     instructions of D. >> >>     This may include correctly emulating the x86 instructions of H in >>     the order specified by the x86 instructions of H thus calling H(D,D) >>     in recursive simulation. >> >> *Execution Trace* >>     Line 11: main() invokes H(D,D); H(D,D) simulates lines 01, 02, and 03 >>     of D. This invokes H(D,D) again to repeat the process in endless >>     recursive simulation. > > One can see that D is never stuch in recursive simulation unless H is. Counter-factual, please try again. > Whether H is cannot be seen has the details of H are not shown. Even > if they were H must, in order to simulate any x86 execution, be so > big and complicated that essential aspect may be hard to see; depending, > of course, on how the code is organized. > We simply assume that H is the C equivalent of a UTM that stops simulating at some point and returns the meaningless 56. -- Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius hits a target no one else can see." Arthur Schopenhauer