Liste des Groupes | Revenir à theory |
On 8/18/2024 3:50 AM, Mikko wrote:And thus the input to HHH isn't the bytes you try to pass off as it but ALL of the code of Halt7.obj, so every HHH sees a DIFFERENT input so you can't use the results of one to try to provide data for a different one without making the mistake of talking about cats by looking at 10 story office buildings.On 2024-08-17 12:31:01 +0000, olcott said:We are discussing the foundation of that in this thread.
>On 8/17/2024 7:29 AM, olcott wrote:>void DDD()>
{
HHH(DDD);
}
>
_DDD()
[00002172] 55 push ebp ; housekeeping
[00002173] 8bec mov ebp,esp ; housekeeping
[00002175] 6872210000 push 00002172 ; push DDD
[0000217a] e853f4ffff call 000015d2 ; call HHH(DDD)
[0000217f] 83c404 add esp,+04
[00002182] 5d pop ebp
[00002183] c3 ret
Size in bytes:(0018) [00002183]
>
*It is a basic fact that DDD emulated by HHH according to*
*the semantics of the x86 language cannot possibly stop*
*running unless aborted* (out of memory error excluded)
>
Simulating Termination Analyzer H is Not Fooled by Pathological Input D
>
https://www.researchgate.net/ publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D
That attempt should be discussed separately, and to some extent already is.
>
X = DDD emulated by HHH according to the semantics of the x86 language
Y = HHH never aborts its emulation of DDD
Z = DDD never stops running
This is the essence of above: (X ∧ Y) ↔ Z
x86utm takes the compiled Halt7.obj file of this c program
https://github.com/plolcott/x86utm/blob/master/Halt7.c
Thus making all of the code of HHH directly available to
DDD and itself. HHH emulates itself emulating DDD.
Les messages affichés proviennent d'usenet.