Deutsch   English   Français   Italiano  
<v6qpcu$2uo3m$1@dont-email.me>

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

Path: ...!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Mikko <mikko.levanto@iki.fi>
Newsgroups: comp.theory
Subject: Re: DDD correctly emulated by HHH is correctly rejected as non-halting.
Date: Fri, 12 Jul 2024 11:27:10 +0300
Organization: -
Lines: 40
Message-ID: <v6qpcu$2uo3m$1@dont-email.me>
References: <v6m7si$1uq86$2@dont-email.me> <v6ntmh$2bd9a$1@dont-email.me> <v6oomc$2fuva$3@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 12 Jul 2024 10:27:11 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="807c282dc99f45cb4bf1613b1d698492";
	logging-data="3104886"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+z83PB5ZCFAUWAj53aPJd2"
User-Agent: Unison/2.2
Cancel-Lock: sha1:FVsi7Y0WmBMaueKUIMAHV7S3dAQ=
Bytes: 2124

On 2024-07-11 14:02:52 +0000, olcott said:

> On 7/11/2024 1:22 AM, Mikko wrote:
>> On 2024-07-10 15:03:46 +0000, olcott said:
>> 
>>> typedef void (*ptr)();
>>> int HHH(ptr P);
>>> 
>>> void DDD()
>>> {
>>>    HHH(DDD);
>>> }
>>> 
>>> int main()
>>> {
>>>    HHH(DDD);
>>> }
>>> 
>>> We stipulate that the only measure of a correct emulation
>>> is the semantics of the x86 programming language. By this
>>> measure when 1 to ∞ steps of DDD are correctly emulated by
>>> each pure function x86 emulator HHH (of the infinite set
>>> of every HHH that can possibly exist) then DDD cannot
>>> possibly reach past its own machine address of 0000216b
>>> and halt.
>> 
>> For every instruction that the C compiler generates the x86 language
>> specifies an unambiguous meaning, leaving no room for "can".
>> 
> 
> then DDD cannot possibly reach past its own machine
> address of 0000216b and halt.

As I already said, there is not room for "can". That means there is
no room for "cannot", either. The x86 semantics of the unshown code
determines unambigously what happens.

-- 
Mikko