Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: olcott Newsgroups: comp.theory,sci.logic Subject: Re: DDD correctly emulated by H0 -- Ben agrees that Sipser approved criteria is met Date: Wed, 26 Jun 2024 22:30:54 -0500 Organization: A noiseless patient Spider Lines: 63 Message-ID: References: <87jzidm83f.fsf@bsb.me.uk> <5nSdnSkMN76jIOH7nZ2dnZfqnPidnZ2d@brightview.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Thu, 27 Jun 2024 05:30:55 +0200 (CEST) Injection-Info: dont-email.me; posting-host="d7b6b7ddfe8775f34f568700240d9d1b"; logging-data="2701383"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18k7DpZ/vYlDdU1UHKDfa3X" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:zt9e43iWGXSS6NS1lprkq/IInOQ= In-Reply-To: Content-Language: en-US Bytes: 4081 On 6/26/2024 10:15 PM, Richard Damon wrote: > On 6/26/24 10:56 PM, olcott wrote: >> On 6/26/2024 9:39 PM, Richard Damon wrote: >>> >>> Nope, they use virtual memory provided by the UTM. >>> >> >> That *is* what it *is* doing. >> The UTM gets this from x86utm. >> The slaves use the already allocated memory. > > But they don't get to use the same memory that the simulator simulating > them is using, as that leaks information that they don't get to know. > The information flow is only upward. > They have a memory buffer (as far as they see) that starts empty, and > they put data in it, and they take data out, and only what they put in > is ever there, > This is what is intended, and how it actually works. >> >>> They write to what they consider to be their tape, and the UTM >>> figures out how to store that on its tape to be able to give it back >>> when requested. >>> >> That is already what it does. > > But if the simulated machine can see that there is a layer outside them, > then it isn't correct. > It need not see this and my algorithm still works. >> >>> Of course, you never understood the need for putting the simulated >>> machine in its own virtual memory space. >> >> I have been doing that for 3.5 years. >> It has its own stack registers and RAM. >> >> The machine code is the same code, yet executed >> as a separate process. >> > > Then what does the "global" comment mean, every simulator should think > it is the globally top level simulator, and be simulating the simulator That was so that humans could see the level in an output message. I don't use that anymore. It is disabled. > of the next level down (not doing that simulators simulation), so no > simulator has "levels" in it for its own simulation. From the master UTM's perspective there is one more level before it sees the infinite recursion behavior pattern. -- Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius hits a target no one else can see." Arthur Schopenhauer