| Deutsch English Français Italiano |
|
<101r0p5$15d1h$4@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: dbush <dbush.mobile@gmail.com> Newsgroups: comp.theory Subject: Re: DDD emulated by HHH diverges from DDD emulated by HHH1 Date: Wed, 4 Jun 2025 22:52:21 -0400 Organization: A noiseless patient Spider Lines: 84 Message-ID: <101r0p5$15d1h$4@dont-email.me> References: <101khcl$3bfvj$6@dont-email.me> <101o96g$db96$3@dont-email.me> <101ob1t$hd6o$3@dont-email.me> <101obrf$hlr6$1@dont-email.me> <101ocan$hd6o$6@dont-email.me> <101ochl$i3m6$1@dont-email.me> <101oda2$hd6o$8@dont-email.me> <101oe1m$i3m6$3@dont-email.me> <101oee0$hd6o$9@dont-email.me> <101oeik$i3m6$4@dont-email.me> <101ofvi$inkg$1@dont-email.me> <101pask$pv5r$1@dont-email.me> <101porr$ta6v$1@dont-email.me> <101qb4p$11sr2$1@dont-email.me> <101qbtj$11qlg$1@dont-email.me> <101qc32$11sr2$3@dont-email.me> <101qhst$13bo7$1@dont-email.me> <101qicm$11sr2$4@dont-email.me> <101qjki$13i0e$1@dont-email.me> <101qn7s$14gq1$1@dont-email.me> <101qnp3$14gff$1@dont-email.me> <101qo1g$14gq1$2@dont-email.me> <101qoia$14gff$2@dont-email.me> <101qp3h$14gq1$3@dont-email.me> <101qqn5$14gff$4@dont-email.me> <101qrrc$14gq1$4@dont-email.me> <101qsfp$15bg8$1@dont-email.me> <101qt22$15d1h$1@dont-email.me> <101qu35$15bg8$2@dont-email.me> <101quas$15d1h$2@dont-email.me> <101qvrq$15bg8$5@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Thu, 05 Jun 2025 04:52:22 +0200 (CEST) Injection-Info: dont-email.me; posting-host="0260837afa1e5d49ba06ebc772534096"; logging-data="1225777"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18dXStqrWMZA0Zshcuw+JRO" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:8M3N5W6+8BOBeQ8VYJ+vCNUmHUE= Content-Language: en-US In-Reply-To: <101qvrq$15bg8$5@dont-email.me> Bytes: 5350 On 6/4/2025 10:36 PM, olcott wrote: > On 6/4/2025 9:10 PM, dbush wrote: >> On 6/4/2025 10:06 PM, olcott wrote: >>> On 6/4/2025 8:48 PM, dbush wrote: >>>> On 6/4/2025 9:39 PM, olcott wrote: >>>>> On 6/4/2025 8:28 PM, dbush wrote: >>> >>>> >>>> DDD emulated by HHH1 emulating HHH DDD emulated by HHH emulating HHH >>>> [00002183] push ebp ; [00002183] push ebp ; >>>> [00002184] mov ebp,esp ; [00002184] mov ebp,esp ; >>>> [00002186] push 00002183 ; DDD [00002186] push 00002183 ; DDD >>>> [0000218b] call 000015c3 ; HHH [0000218b] call 000015c3 ; HHH >>>> ### HHH aborts ### >>>> >>> >>> *That is dishonest* >> >> No, that is the *fact* of what happens when HHH1 emulates DDD >> >>> HHH1 emulates DDD once and this matches >> The one time that the outer HHH emulates DDD, up to the point that HHH >> aborts >> >>> >>> DDD emulated by HHH1 DDD emulated by HHH >>> [00002183] push ebp [00002183] push ebp >>> [00002184] mov ebp,esp [00002184] mov ebp,esp >>> [00002186] push 00002183 ; DDD [00002186] push 00002183 ; DDD >>> [0000218b] call 000015c3 ; HHH [0000218b] call 000015c3 ; HHH >>> >>> *THE MATCHING IS NOW USED UP* >>> *THE MATCHING IS NOW USED UP* >>> *THE MATCHING IS NOW USED UP* >> >> False. HHH1 is still simulating the left side by simulating HHH as >> shown above. >> > > The is not the way that side-by-side comparisons of > DDD simulated by HHH1 versus DDD simulated by HHH > are made. False. That is *exactly* how they are made. Anything that the directly executed HHH1 emulates, at any level, is part of the emulation by HHH1. And it is being compared against the emulation made by the direct execution HHH, *not* against any simulated HHH which is really part of DDD. > > There is a list of DDD instructions that are directly > simulated by HHH1 and directly simulated by HHH right > here: > > DDD emulated by HHH1 DDD emulated by HHH > [00002183] push ebp [00002183] push ebp > [00002184] mov ebp,esp [00002184] mov ebp,esp > [00002186] push 00002183 ; DDD [00002186] push 00002183 ; DDD > [0000218b] call 000015c3 ; HHH [0000218b] call 000015c3 ; HHH > > HHH1 never directly emulates any other DDD. > Another instance of HHH does directly emulate DDD. Irrelevant. The directly executed instance of HHH1 and the directly executed instance of HHH do exactly the same thing up to the point that HHH aborts, as you have *explicitly* admitted: On 6/4/2025 12:38 PM, olcott wrote: > On 6/4/2025 4:20 AM, Fred. Zwarts wrote: >> >> That did not answer the question: WHAT INSTRUCTION, correctly simulated did that? > > When HHH1(DDD) simulates DDD it never simulates itself. > When HHH(DDD) simulates DDD then simulates itself simulating > DDD the first instruction that this simulated HHH simulates > diverges from the simulation that HHH1 did. > >> You cannot point to any instruction interpreted differently by the two simulators. > > There are no instructions interpreted differently.