Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connections
Warning: mysqli::query(): Couldn't fetch mysqli in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\index.php on line 66
Article <f72e844b62cabdec17b023af2cdfd17a55b87933@i2pn2.org>
Deutsch   English   Français   Italiano  
<f72e844b62cabdec17b023af2cdfd17a55b87933@i2pn2.org>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: Richard Damon <richard@damon-family.org>
Newsgroups: comp.theory
Subject: Re: Sequence of sequence, selection and iteration matters
Date: Tue, 9 Jul 2024 22:52:05 -0400
Organization: i2pn2 (i2pn.org)
Message-ID: <f72e844b62cabdec17b023af2cdfd17a55b87933@i2pn2.org>
References: <v6e7va$c4sv$1@dont-email.me> <v6g444$pdc2$1@dont-email.me>
 <v6go4d$sg7f$1@dont-email.me> <v6ikv5$19h6q$1@dont-email.me>
 <v6jguf$1ctoi$5@dont-email.me> <v6ji1d$1dpoc$1@dont-email.me>
 <v6jig0$1ctoi$11@dont-email.me> <v6jkib$1e3jq$1@dont-email.me>
 <v6jpe5$1eul0$1@dont-email.me> <v6jpqo$1e3jq$2@dont-email.me>
 <v6jqfg$1eul0$2@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 10 Jul 2024 02:52:05 -0000 (UTC)
Injection-Info: i2pn2.org;
	logging-data="2743986"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="diqKR1lalukngNWEqoq9/uFtbkm5U+w3w6FQ0yesrXg";
User-Agent: Mozilla Thunderbird
In-Reply-To: <v6jqfg$1eul0$2@dont-email.me>
X-Spam-Checker-Version: SpamAssassin 4.0.0
Content-Language: en-US
Bytes: 4839
Lines: 85

On 7/9/24 1:02 PM, olcott wrote:
> On 7/9/2024 11:51 AM, Fred. Zwarts wrote:
>> Op 09.jul.2024 om 18:44 schreef olcott:
>>> On 7/9/2024 10:21 AM, Fred. Zwarts wrote:
>>>> Op 09.jul.2024 om 16:46 schreef olcott:
>>>>> On 7/9/2024 9:38 AM, Fred. Zwarts wrote:
>>>>>> Indeed, no such HHH exists. This proves that HHH cannot possibly 
>>>>>> simulate itself correctly.
>>>>>
>>>>> "Correctly" means must do whatever the x86 code specifies.
>>>>
>>>> And since the x86 code never specifies an abort, it is incorrect to 
>>>> abort halfway a simulation that would halt. We know it would halt, 
>>>> because other simulators show that it halts when HHH is correctly 
>>>> simulated.
>>>> If you want to deny this truth, point to the specification of the 
>>>> x86 language where it says that a program must be aborted. It is 
>>>> irrational to defend an unneeded abort with a reference to the x86 
>>>> specifications.
>>>>
>>>>> You are in psychological denial causing you to be irrational.
>>>>
>>>> Illogical and irrelevant remarks ignored. I know olcott has problems 
>>>> to recognize the truth, so I do not feel offended.
>>>>
>>>>>
>>>>>>>
>>>>>>> _DDD()
>>>>>>> [00002163] 55         push ebp      ; housekeeping
>>>>>>> [00002164] 8bec       mov ebp,esp   ; housekeeping
>>>>>>> [00002166] 6863210000 push 00002163 ; push DDD
>>>>>>> [0000216b] e853f4ffff call 000015c3 ; call HHH(DDD)
>>>>>>> [00002170] 83c404     add esp,+04
>>>>>>> [00002173] 5d         pop ebp
>>>>>>> [00002174] c3         ret
>>>>>>> Size in bytes:(0018) [00002174]
>>>>>>>
>>>>>>> *When DDD is correctly emulated by any pure function*
>>>>>>> *HHH x86 emulator that can possibly exist* which calls
>>>>>>> an emulated HHH(DDD) to repeat this process until the
>>>>>>> emulated DDD is aborted.
>>>>>>
>>>>
>>>> And the fact *that* it aborts, makes the simulation incorrect (as 
>>>> Sipser would agree with), because the X86 code does not specify an 
>>>> abort at that point. Therefore, the only conclusion must be: No such 
>>>> HHH exists.
>>>
>>> HHH is fully operational in the x86utm operating system.
>>>
>>> _DDD()
>>> [00002163] 55         push ebp      ; housekeeping
>>> [00002164] 8bec       mov ebp,esp   ; housekeeping
>>> [00002166] 6863210000 push 00002163 ; push DDD
>>> [0000216b] e853f4ffff call 000015c3 ; call HHH(DDD)
>>> [00002170] 83c404     add esp,+04
>>> [00002173] 5d         pop ebp
>>> [00002174] c3         ret
>>> Size in bytes:(0018) [00002174]
>>>
>>> When DDD is correctly emulated by any pure function x86
>>> emulator HHH calls an emulated HHH(DDD) this call cannot
>>> possibly return. 
>>
>> HHH cannot possibly simulate itself to the end and return, which shows 
>> that 
> 
> the simulation is correct because that is what the x86
> code means when it says that DDD correctly emulated by HHH
> is stuck in recursive emulation.
> 

BNo, the simulation is INCORRECT because it is INCOMPLETE, because the 
definition of the execution of every instruction emulated included that 
the next instruction WILL execute, and thus stopping the emulation at 
that point is just INCORRECT.

> That people not sufficiently understanding the semantics
> of the x86 language say otherwise merely proves that their
> understanding is insufficient.
> 

No, YOU don't understand that fundamental nature or computers.

How would you like it if the programs on your computer suddenly decided 
they could just stop at arbitary points?