| Deutsch English Français Italiano |
|
<a6dd00c5734a5df50234affe9f0d9790b17e233e@i2pn2.org> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder9.news.weretis.net!news.nk.ca!rocksolid2!i2pn2.org!.POSTED!not-for-mail From: Richard Damon <richard@damon-family.org> Newsgroups: comp.theory Subject: Re: DDD correctly emulated by EEE --- Correct Emulation Defined Date: Mon, 24 Mar 2025 21:28:26 -0400 Organization: i2pn2 (i2pn.org) Message-ID: <a6dd00c5734a5df50234affe9f0d9790b17e233e@i2pn2.org> References: <vrfuob$256og$1@dont-email.me> <vrmirg$5bpl$1@dont-email.me> <ca0a3e4701bc62fa38f1138064feff7628ff5b48@i2pn2.org> <vrmtrn$cvat$7@dont-email.me> <678373dd34320b3c8250f1e75c849a16316d8ae8@i2pn2.org> <vro0rb$1c9ia$2@dont-email.me> <vroj7a$21s06$1@dont-email.me> <vrpfao$2qbhf$1@dont-email.me> <vrr1mf$db46$1@dont-email.me> <vrrp0r$11a56$3@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Tue, 25 Mar 2025 01:28:26 -0000 (UTC) Injection-Info: i2pn2.org; logging-data="1621106"; mail-complaints-to="usenet@i2pn2.org"; posting-account="diqKR1lalukngNWEqoq9/uFtbkm5U+w3w6FQ0yesrXg"; User-Agent: Mozilla Thunderbird In-Reply-To: <vrrp0r$11a56$3@dont-email.me> X-Spam-Checker-Version: SpamAssassin 4.0.0 Content-Language: en-US Bytes: 4649 Lines: 81 On 3/24/25 10:08 AM, olcott wrote: > On 3/24/2025 2:30 AM, Mikko wrote: >> On 2025-03-23 17:10:48 +0000, olcott said: >> >>> On 3/23/2025 4:11 AM, Mikko wrote: >>>> On 2025-03-23 03:57:30 +0000, olcott said: >>>> >>>>> On 3/22/2025 9:53 PM, Richard Damon wrote: >>>>>> On 3/22/25 2:00 PM, olcott wrote: >>>>>>> On 3/22/2025 12:34 PM, Richard Damon wrote: >>>>>>>> On 3/22/25 10:52 AM, olcott wrote: >>>>>>>>> _DD() >>>>>>>>> [00002133] 55 push ebp ; housekeeping >>>>>>>>> [00002134] 8bec mov ebp,esp ; housekeeping >>>>>>>>> [00002136] 51 push ecx ; make space for local >>>>>>>>> [00002137] 6833210000 push 00002133 ; push DD >>>>>>>>> [0000213c] e882f4ffff call 000015c3 ; call EEE(DD) >>>>>>>>> [00002141] 83c404 add esp,+04 >>>>>>>>> [00002144] 8945fc mov [ebp-04],eax >>>>>>>>> [00002147] 837dfc00 cmp dword [ebp-04],+00 >>>>>>>>> [0000214b] 7402 jz 0000214f >>>>>>>>> [0000214d] ebfe jmp 0000214d >>>>>>>>> [0000214f] 8b45fc mov eax,[ebp-04] >>>>>>>>> [00002152] 8be5 mov esp,ebp >>>>>>>>> [00002154] 5d pop ebp >>>>>>>>> [00002155] c3 ret >>>>>>>>> Size in bytes:(0035) [00002155] >>>>>>>>> >>>>>>>>> When finite integer N instructions of the above x86 >>>>>>>>> machine language DD are emulated by each x86 emulator >>>>>>>>> EEE[N] at machine address [000015c3] according to the >>>>>>>>> semantics of the x86 language no DD ever reaches its own >>>>>>>>> "ret" instruction at machine address [00002155] and >>>>>>>>> terminates normally. >>>>>>>>> >>>>>>>> >>>>>>>> Your can't emulate the above code for N > 4, as you get into >>>>>>>> undefine memory. >>>>>>>> >>>>>>> >>>>>>> I have already addressed this objection dozens of times. >>>>>>> >>>>>> >>>>>> No you haven't. You have given several different LIES about it. >>>>>> >>>>>> As I have pointed out, if you don't include Halt7.c as part of the >>>>>> definition, then you can't do it as you are looking at undefined >>>>>> memory. >>>>>> >>>>> >>>>> Your lack of technical competence is showing. >>>>> (1) We are talking about a hypothetical infinite >>>>> set of pure x86 emulators that have no decider code. >>>>> >>>>> (2) The memory space of x86 machine code is not >>>>> in the C source file, it is in the object file. >>>> >>>> It isn't in the object file, either. Only the initial values of some >>>> memory locations are there. The object file does not even specify >>>> where in the memory space those locations are. The execution of a >>>> program requires a memory space larger than the object file. >>>> >>> >>> I patch the Halt7.obj file so that functions >>> are at a fixed address. This file is never linked. >> >> Doesn't affect the fact that important parts of the memory space are not >> containted in the object file. >> i > > Richard stupidly complained that III could not call EEE > because he stupidly believed that there were in different > memory spaces. > LIAR. I said it can't call EEE if the code for EEE isn't made part of the progran, and thus needs to be part of the input describing it. You are just proving that you are nothing but a pathological liar that is too stupid t understand the meaning of the words you use.