Liste des Groupes | Revenir à theory |
On 6/20/2025 7:13 PM, Richard Damon wrote:Which isn't the definition of "Correct Emulation", and thus is just a lie of equivocation.On 6/20/25 1:09 PM, olcott wrote:HHH emulates N x86 machine language instructions ofOn 6/20/2025 10:27 AM, joes wrote:>Am Fri, 20 Jun 2025 09:53:41 -0500 schrieb olcott:>On 6/20/2025 4:42 AM, Fred. Zwarts wrote:>Op 19.jun.2025 om 17:23 schreef olcott:On 6/19/2025 3:55 AM, Fred. Zwarts wrote:Op 18.jun.2025 om 17:41 schreef olcott:On 6/18/2025 4:36 AM, Fred. Zwarts wrote:Op 17.jun.2025 om 16:36 schreef olcott:It was an agreement.Indeed, HHH fails to reach the end of the simulation, even thoughThat is counter-factual and over-your-head.
the end is only one cycle further from the point where it gave up
the simulation.
>
>Lol, that was the same paragraph.Yes this is factual.>No evidence presented for this claim. Dreaming again?>
Even a beginner understands that when HHH has code to abort and halt,
the simulated HHH runs one cycle behind the simulating HHH, so that
when the simulating HHH aborts, the simulated HHH is only one cycle
away from the same point.
Proving that you do not understand what unreachable code is.
Even a beginner understands that when HHH has code to abort and halt,
the simulated HHH runs one cycle behind the simulating HHH, so that
when the simulating HHH aborts, the simulated HHH is only one cycle
away from the same point.
>Every simulated HHH remains one cycle behind its simulator no matter howYes, no simulator can proceed past a call to itself.
deep the recursive simulations go. This means that the outermost
directly executed HHH reaches its abort criteria first.
>
That is counter-factual and it you knew c well
enough you could verify that is counter-factual.
https://github.com/plolcott/x86utm/blob/master/Halt7.c
Which shows that HHH never correctly simulates its input, as it always will abort its simulation, and a partial simulation is never a correct simulation by the term-of-art definition.
>
DDD according to the semantics of the x86 language,
thus necessarily emulates these N instructions correctly.
This also requires HHH to emulate itself emulating DDD
at least once.
The main computer science definition of halting isRight. but youy don't understand the "of what".
reaching a final halt state, anyone disagreeing is
incorrect. An alternative definition that is easier
for programmers to understand is never stop running.
Any disagreement with these is incorrect.
When there are no N instructions of DDD correctlyNo, since every HHH creates a different DDD.
simulated by HHH that can possibly reach their final
halt state then it is a verified fact that the input to
HHH(DDD) specifies a non-halting sequence of
configurations. The directly executed DDD() is the
caller of HHH(DDD) thus not its input.
Les messages affichés proviennent d'usenet.