Sujet : Re: 195 page execution trace of DDD correctly simulated by HH0 ---Boilerplate Reply
De : richard (at) *nospam* damon-family.org (Richard Damon)
Groupes : comp.theory sci.logicDate : 21. Jun 2024, 21:11:37
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <v54j99$lkkc$10@i2pn2.org>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
User-Agent : Mozilla Thunderbird
On 6/21/24 2:51 PM, olcott wrote:
On 6/21/2024 1:39 PM, Richard Damon wrote:
On 6/21/24 2:22 PM, olcott wrote:
On 6/21/2024 1:00 PM, Richard Damon wrote:
On 6/21/24 1:55 PM, olcott wrote:
On 6/21/2024 12:40 PM, Richard Damon wrote:
On 6/21/24 1:22 PM, olcott wrote:
>
When there is no mapping from the finite string x86 machine
language input to H(D,D) to the behavior of D(D) then
H(D,D) IS NOT being asked about the behavior of D(D).
>
But there *IS* a mapping, it just isn't a COMPUTABLE MAPPING.
>
>
If there is a mapping yet not a computable mapping then
the actual halt decider cannot even see the question that
the textbooks expect it to see.
>
But a decider doesn't "See" the question. it just computes the result it was programmed to give.
>
>
It must be the behavior that the input finite string actually specifies.
It cannot be the behavior that the programmer imagines that it specifies.
>
>
But strings don't "have" behavior, or even "specify" behavior by themselves, the behavior comes from applying the string to the DEFINITION of the problem.
>
In this case the definition of the x86 language specifies
the behavior of DDD. If you deny this then you are a liar.
But only when the problem statement says the byte string is to be interpreded as x86 code.
No matter how much textbooks expect that the input to HH0(DDD)
does not specify recursive simulation their counter-factual
expectations are refuted.
Nope. Just more of your lies. Maybe it specifies FINITELY recursive simulation because HH0 will abort its simulation.
Anything else is just counter factual to the actual behavior of the FULL input.
Of course, if you keep on insisting that you input is JUST what you show, I will point out that your problem is just INVALID as the byte sequence alone does NOT actually specify the behavior of the program, as it goes into territory with no defined values.
That is like asking for "the sum of 2 and" (and then not giving the rest of the input),
_DDD()
[00002093] 55 push ebp
[00002094] 8bec mov ebp,esp
[00002096] 6893200000 push 00002093 ; push DDD
[0000209b] e853f4ffff call 000014f3 ; call HH0
[000020a0] 83c404 add esp,+04
[000020a3] 5d pop ebp
[000020a4] c3 ret
Size in bytes:(0018) [000020a4]
It is as if you have been indoctrinated like the
Moonies: (cult members must be deprogrammed)
https://en.wikipedia.org/wiki/Unification_Church
I understand the Moonies, YOU are the one that has been brainwashed, and it seems you did it to yourself.