Sujet : Re: HHH maps its input to the behavior specified by it --- partial simulation never reaches its halt state, but the actual behavior of the actual program does
De : richard (at) *nospam* damon-family.org (Richard Damon)
Groupes : comp.theoryDate : 10. Aug 2024, 00:46:18
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <d981db697b2b07a5f0dd4e235709928c6bd3b1b7@i2pn2.org>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
User-Agent : Mozilla Thunderbird
On 8/9/24 10:51 AM, olcott wrote:
On 8/9/2024 4:03 AM, Mikko wrote:
On 2024-08-08 13:18:34 +0000, olcott said:
>
void DDD()
{
HHH(DDD);
return;
}
>
Each HHH of every HHH that can possibly exist definitely
*emulates zero to infinity instructions correctly* In
none of these cases does the emulated DDD ever reach
its "return" instruction halt state.
>
The ranges of "each HHH" and "every HHH" are not defined above
so that does not really mean anything.
>
Here is something that literally does not mean anything:
"0i34ine ir m0945r (*&ubYU I*(ubn)I*054 gfdpodf["
"Colorless green ideas sleep furiously"
https://en.wikipedia.org/wiki/Colorless_green_ideas_sleep_furiously
Has lots of meaning, that does not totally fit together coherently.
I defined an infinite set of HHH x86 emulators.
I stipulated that each member of this set emulates
zero to infinity instructions of DDD.
*I can't say it this way without losing 90% of my audience*
Each element of this set is mapped to one element of the
set of non-negative integers indicating the number of
x86 instructions of DDD that it emulates.
No, since all the emulator that only emulated a finite number of steps did not complete the job, and thus did NOT determine the actual mapping of that input, which is determined by RUNNING that DDD, or COMPLETELY emulating it, which will see the DDD call HHH(DDD) which will after emulationg that finite number of instructions return to DDD which will halt.
*This one seems to be good*
Each element of this set corresponds to one element of
the set of positive integers indicating the number of
x86 instructions of DDD that it emulates.
Right, but any number emulated that is less than the number of instructions that particular input needs to have run to reach a final state is just INCORRECT, since all the HHH that abort DO create an input that will halt in a finite number of steps, just at a value of N bigger than the number of steps that HHH emulated.
You just don't understand the question you claim to be answering.