Path: ...!Xl.tags.giganews.com!local-3.nntp.ord.giganews.com!nntp.brightview.co.uk!news.brightview.co.uk.POSTED!not-for-mail
NNTP-Posting-Date: Fri, 26 Jul 2024 20:49:07 +0000
Subject: Re: This function proves that only the outermost HHH examines the
 execution trace
Newsgroups: comp.theory
References: <v80h07$2su8m$3@dont-email.me>
 <c38a02c9a30d640b44756d6e636b76f57a4b46f2@i2pn2.org>
From: Mike Terry <news.dead.person.stones@darjeeling.plus.com>
Date: Fri, 26 Jul 2024 21:49:05 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Firefox/91.0 SeaMonkey/2.53.17
MIME-Version: 1.0
In-Reply-To: <c38a02c9a30d640b44756d6e636b76f57a4b46f2@i2pn2.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <JpqdnXraq5Jeljn7nZ2dnZfqn_udnZ2d@brightview.co.uk>
Lines: 58
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-V63212OuzfsJSna+nYGmZjAXRnBcvUER6NG8NSk5IYpWUSbNtrQZzTWHErbBLpnF3R1puXES+njBPra!I8wNIr/dpipLvhhrnoVR7fsfNP5Esdk90+MZIHAhATdSVqjQLliwqZ3yJ7t3uF9J1j9GokEAbps+!/8Sa56VKtJS9XejJmDLwfbYtd5c=
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
Bytes: 3477

On 26/07/2024 20:24, joes wrote:
> Am Fri, 26 Jul 2024 10:56:55 -0500 schrieb olcott:
>> This is meant for Mike, Joes and Fred don't have the technical
>> competence to understand it.
> Fuck you too.
> 
>> Mike: It seems that HHH has been a pure function of its inputs and never
>> has provided data downward to its slaves that corrupts their halt status
>> decision. They don't even make a halt status decision thus cannot make a
>> corrupted one.
> The indirectly called HHH's most certainly make a decision.
> 
>> I could change the code so that the slave instances can and do try to
>> form a halt status decision on the basis of the execution trace that
>> they do have.
>> There is no sense in doing that because they can't possibly have enough
>> data, they will always be one whole execution trace behind the next
>> outer instance of HHH.
> That's kinda the point.
> 
>> u32 Decide_Halting_HH(u32**                   Aborted,
>>                         u32**                   execution_trace,
>>                         Decoded_Line_Of_Code**  decoded,
>>                         u32                     code_end,
>>                         u32                     End_Of_Code, Registers**
>>                                    master_state, Registers**
>>                         slave_state, u32**                   slave_stack,
>>                         u32                     Root)
>> {
>>     u32 aborted_temp = 0;  // 2024-06-05 u32
>>     Current_Length_Of_Execution_Trace = 0;
>>     while (aborted_temp == 0) // 2024-06-05 {
> 
>>       if (Root)  // Master UTM halt decider {
> There it is.
> Where is this passed from?

Indeed - it comes from HHH.  It is 1 for first HHH invocation and 0 subsequently, as determined 
using static variables in HHH.

I think this GitHub link has all the code:  <https://github.com/plolcott/x86utm>

PO has previously published a zip file with everything in, but I think it's the same content, with 
GitHub being a bit more recent.

Mike.






> 
>>     if (aborted_temp == 1) // 2021-01-26 Must be aborted
>>       return 0;
>>     return 1;           // 2021-01-26 Need not be aborted
>> }
>