Re: DDD correctly emulated by H0 -- Ben agrees that Sipser approved criteria is met

On 6/26/24 11:30 PM, olcott wrote:

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.

Obviously not if it affect the behavior of the inner layers to make them not allocate a new buffer.

 

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.

Then how do they know not to create the buffer?

 

>

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.

Then take it out. That might help you get the output of just the simulation that the decider is doing, and not have it mixed in with the trace of that simulators execution, as you claim to have.

 

>

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.

But what we need to see is the simulation done by the top level decider, and it alone.

 

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.
 

Nope. Your "Master UTM" isn't doing its job right if it is doing that. Its job is to just run the machine it was given. That machine needs to do the job IT was given, and so on. The lower level emulators can't use the "master UTM", as they can't know it exists, so they need to use there own instance of the same code (it may be physically the same code, but with a TOTALLY new data space (and no shared statics).