Path: ...!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: olcott Newsgroups: comp.theory Subject: Re: HHH(DDD) computes the mapping from its input to HHH emulating itself emulating DDD --- anyone that says otherwise is a liar Date: Mon, 18 Nov 2024 15:46:43 -0600 Organization: A noiseless patient Spider Lines: 56 Message-ID: References: <1faff0266d203c301ed017aa69027ffd166f32ad@i2pn2.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Mon, 18 Nov 2024 22:46:44 +0100 (CET) Injection-Info: dont-email.me; posting-host="9eeddbf0661af45b9b764b78cd434096"; logging-data="1525898"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX197zQ+mDw0ttUXBCORoosrx" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:vYRtmq1JJD2HUROcGe/o34CO7iU= In-Reply-To: <1faff0266d203c301ed017aa69027ffd166f32ad@i2pn2.org> X-Antivirus-Status: Clean X-Antivirus: Norton (VPS 241118-8, 11/18/2024), Outbound message Content-Language: en-US Bytes: 3489 On 11/18/2024 3:36 PM, Richard Damon wrote: > On 11/18/24 3:42 PM, olcott wrote: >> On 11/18/2024 3:41 AM, Mikko wrote: >>> The "the mapping" on the subject line is not correct. The subject line >>> does not specify which mapping and there is no larger context that could >>> specify that. Therefore it should be "a mapping". >>> >>> On 2024-11-17 18:36:17 +0000, olcott said: >>> >>>> void DDD() >>>> { >>>>    HHH(DDD); >>>>    return; >>>> } >>>> >>>> _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] >>>> >>>> DDD emulated by any encoding of HHH that emulates N >>>> to infinity number of steps of DDD cannot possibly >>>> reach its "return" instruction final halt state. >>> >>> Because it cannot reach the instructions before tha return. >>> Because it cannot reach the instruction after the HHH call. >>> Because it cannot reach return instruction of HHH. >>> >>>> This applies to every DDD emulated by any HHH no >>>> matter the recursive depth of emulation. Thus it is >>>> a verified fact that the input to HHH never halts. >>> >>> That is too vague to be regareded true or false. It is perfectly possibe >>> to define two programs and call them DDD and HHH >> >> What a jackass. DDD and HHH have been fully specified >> for many months. > > No, you keep on changing them, after all, you say there is one set of > code, but an infinite set of pairings, and even though for every one of > them the HHH that DDD calls gives the wrong answer, you want to define > it as correct. > Top of page 2 Jackass https://www.researchgate.net/publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D -- Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius hits a target no one else can see." Arthur Schopenhauer