Liste des Groupes | Revenir à theory |
On 5/29/24 2:31 PM, olcott wrote:Right the execution trace of D simulated by pure function H usingOn 5/29/2024 1:14 PM, Ben Bacarisse wrote:How is that?Alan Mackenzie <acm@muc.de> writes:>
>How about a bit of respect? Mike specifically asked you not to cite his>
name as a back up for your points. Why do you keep doing it?
He does it to try to rope more people in. It's the same ploy as
insulting people by name. It's hard to ignore being maligned in public
by a fool.
>
*Thanks for validating my simplified encoding of the Linz*
>
When Ĥ is applied to ⟨Ĥ⟩
Ĥ.q0 ⟨Ĥ⟩ ⊢* embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.qy ∞
Ĥ.q0 ⟨Ĥ⟩ ⊢* embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.qn
>
I really did believe that Ben Bacarisse was lying when I said it.
>
At the time I was talking about the easily verified fact of the actual
execution trace of fully operational code and everyone was denying the
easily verified facts.
>
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 }
>
It turns out that two dozen people are easily proven wrong when
they claimed that the correct simulation of the input to H(D,D)
is the behavior of int main() { D(D); }
>
When D is correctly simulated by H using an x86 emulator the onlyWhich isn't a "Correct Simulation" by the definition that allow the relating of a "Simulation" to the behavior of an input.
way that the emulated D can reach its own emulated final state
at line 06 and halt is
(a) The x86 machine code of D is emulated incorrectly
(b) The x86 machine code of D is emulated in the wrong order
>
Les messages affichés proviennent d'usenet.