Liste des Groupes | Revenir à theory |
On 7/12/2024 3:03 AM, Mikko wrote:On 2024-07-11 14:10:24 +0000, olcott said:On 7/11/2024 1:25 AM, Mikko wrote:On 2024-07-10 17:53:38 +0000, olcott said:On 7/10/2024 12:45 PM, Fred. Zwarts wrote:Op 10.jul.2024 om 17:03 schreef olcott:
The assembly is not concerned with aborting or halting.However, each of those instances has the same sequence of*That is counter-factual*
instructions that the x86 language specifies the same operational
meaning.
When DDD is correctly emulated by HHH according to the semantics of
the x86 programming language HHH must abort its emulation of DDD or
both HHH and DDD never halt.
The simple fact remains that if the behaviour of a program dependsHHH1(DDD) only halts because HHH(DDD) aborts its emulation thus provingWhen DDD is correctly emulated by HHH1 according to the semantics ofHowever, the program DDD is the same in both cases and therefore the
the x86 programming language HHH1 need not abort its emulation of DDD
because HHH has already done this.
its behavioral meaning per x86 semantics is also the same.
the the behaviors are different.
It does that in every (non-)simulation, no change there.If you stupidly ignore that DDD does call HHH in recursive emulation itThe behavior of DDD emulated by HHH1 is identical to the behavior ofWhich is the behaviour of DDD accordint to the semantics of x86
the directly executed DDD().
language.
might superfically seem that way.
Les messages affichés proviennent d'usenet.