Re: HHH maps its input to the behavior specified by it --- key error in all the proofs --- Mike

Am Mon, 12 Aug 2024 13:25:23 -0500 schrieb olcott:

On 8/12/2024 1:16 PM, Richard Damon wrote:

On 8/12/24 1:32 PM, olcott wrote:

On 8/12/2024 12:12 PM, Richard Damon wrote:

YOU don't understand the rules of the x86 code, or don't care if you
are wrong, as NOTHING in the x86 language allows the leaving of the
direct exectuion thread and into showing the code the simulator being
simulated is simulating. The ONLY correct answer is showing it doing
the simulating.
>

I showed the first four lines of this code highlighted in red and you
ignored it. https://liarparadox.org/HHH(DDD)_Full_Trace.pdf

>
No, you ignored my comments.
First, that isn't a trace generated by HHH emulating DDD, but by x86UTM
emulating HHH, so your claim is just a type error.
Then when I look at this emulation, we see that HHH *ONLY* emulates
those first 4 instructions of HHH and no more,

That is counter factual.

It doesn't simulate the following call.
 

that it doesn't simulate what happens in HHH after the jmp 000015e7
instruction, and thus you claim is still a LIE.

That is counter factual.

Where does it jump to?
 

It says that you have HHH simulate the first *8* instructions of the
program DDD, and then stop doing a correct x86 emulation, and switches
to an INCORRECT functional emulation, since it doesn't note that this
emulation is CONDITIONAL.
>

I HAVE pointed out the exact point you "correct emulation" deviates
from the x86 requirments, > and you only answer seems to be that the
x86 model of simulation gets too long. In other words, you logic
system allows people to just LIE if they want to.