Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 23 |
Nodes: | 6 (0 / 6) |
Uptime: | 56:41:44 |
Calls: | 584 |
Calls today: | 1 |
Files: | 1,139 |
D/L today: |
179 files (27,921K bytes) |
Messages: | 112,128 |
On 09/08/2025 06:27, olcott wrote:
It is impossible to show how DD correctly simulated
by HHH can possibly reach its own emulated "ret"
instruction
So HHH never returns, so it fails to act as a termination analyzer
because it fails to report its finding.
On 8/9/2025 12:31 AM, Richard Heathfield wrote:
On 09/08/2025 06:27, olcott wrote:
It is impossible to show how DD correctly simulated
by HHH can possibly reach its own emulated "ret"
instruction
So HHH never returns, so it fails to act as a termination
analyzer because it fails to report its finding.
u32 Needs_To_Be_Aborted_Trace_HH
(Decoded_Line_Of_Code* execution_trace,
-aDecoded_Line_Of_Code *current);
Line 996 matches the
*recursive simulation non-halting behavior pattern* https://github.com/plolcott/x86utm/blob/master/Halt7.c
On 09/08/2025 14:08, olcott wrote:
On 8/9/2025 12:31 AM, Richard Heathfield wrote:
On 09/08/2025 14:08, olcott wrote:
On 8/9/2025 12:31 AM, Richard Heathfield wrote:
On 09/08/2025 06:27, olcott wrote:
It is impossible to show how DD correctly simulated
by HHH can possibly reach its own emulated "ret"
instruction
So HHH never returns, so it fails to act as a termination analyzer
because it fails to report its finding.
u32 Needs_To_Be_Aborted_Trace_HH
(Decoded_Line_Of_Code* execution_trace,
-a-aDecoded_Line_Of_Code *current);
Line 996 matches the
*recursive simulation non-halting behavior pattern*
https://github.com/plolcott/x86utm/blob/master/Halt7.c
If HHH doesn't have to report because its u32 needs to be aborted, you
can simplify the code immeasurably.
On 8/9/2025 8:14 AM, Richard Heathfield wrote:
On 09/08/2025 14:08, olcott wrote:
On 8/9/2025 12:31 AM, Richard Heathfield wrote:
On 09/08/2025 06:27, olcott wrote:
It is impossible to show how DD correctly simulated
by HHH can possibly reach its own emulated "ret"
instruction
So HHH never returns, so it fails to act as a termination
analyzer because it fails to report its finding.
u32 Needs_To_Be_Aborted_Trace_HH
(Decoded_Line_Of_Code* execution_trace,
-a-aDecoded_Line_Of_Code *current);
Line 996 matches the
*recursive simulation non-halting behavior pattern*
https://github.com/plolcott/x86utm/blob/master/Halt7.c
If HHH doesn't have to report because its u32 needs to be
aborted, you can simplify the code immeasurably.
*That return value is passed back to line 1143 of HHH*
-a if (Decide_Halting_HH(&Aborted, &execution_trace, &decoded,
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a code_end, End_Of_Code, &master_state,
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a &slave_state, &slave_stack, Root))
-a-a-a-a-a goto END_OF_CODE;
-a *Aborted-a-a-a-a-a-a-a-a = 0x90909090; // deprecated
-a *execution_trace = 0x90909090;
-a return 0;-a // Does not halt
END_OF_CODE:
-a *Aborted-a-a-a-a-a-a-a-a = 0x90909090; // deprecated
-a *execution_trace = 0x90909090;
-a return 1; // Input has normally terminated
}
On 09/08/2025 15:02, olcott wrote:
On 8/9/2025 8:14 AM, Richard Heathfield wrote:
On 09/08/2025 14:08, olcott wrote:
On 8/9/2025 12:31 AM, Richard Heathfield wrote:
On 09/08/2025 06:27, olcott wrote:
It is impossible to show how DD correctly simulated
by HHH can possibly reach its own emulated "ret"
instruction
So HHH never returns, so it fails to act as a termination analyzer
because it fails to report its finding.
u32 Needs_To_Be_Aborted_Trace_HH
(Decoded_Line_Of_Code* execution_trace,
-a-aDecoded_Line_Of_Code *current);
Line 996 matches the
*recursive simulation non-halting behavior pattern*
https://github.com/plolcott/x86utm/blob/master/Halt7.c
If HHH doesn't have to report because its u32 needs to be aborted,
you can simplify the code immeasurably.
*That return value is passed back to line 1143 of HHH*
-a-a if (Decide_Halting_HH(&Aborted, &execution_trace, &decoded,
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a code_end, End_Of_Code, &master_state,
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a &slave_state, &slave_stack, Root))
-a-a-a-a-a-a goto END_OF_CODE;
-a-a *Aborted-a-a-a-a-a-a-a-a = 0x90909090; // deprecated
-a-a *execution_trace = 0x90909090;
-a-a return 0;-a // Does not halt
END_OF_CODE:
-a-a *Aborted-a-a-a-a-a-a-a-a = 0x90909090; // deprecated
-a-a *execution_trace = 0x90909090;
-a-a return 1; // Input has normally terminated
}
So HHH /does/ return... with the wrong answer, a la Turing. QED.
On 8/9/2025 12:31 AM, Richard Heathfield wrote:
On 09/08/2025 06:27, olcott wrote:
It is impossible to show how DD correctly simulated
by HHH can possibly reach its own emulated "ret"
instruction
So HHH never returns, so it fails to act as a termination analyzer
because it fails to report its finding.
u32 Needs_To_Be_Aborted_Trace_HH
(Decoded_Line_Of_Code* execution_trace,
-aDecoded_Line_Of_Code *current);
Line 996 matches the
*recursive simulation non-halting behavior pattern* https://github.com/plolcott/x86utm/blob/master/Halt7.c
On 8/9/2025 9:11 AM, Richard Heathfield wrote:
On 09/08/2025 15:02, olcott wrote:
On 8/9/2025 8:14 AM, Richard Heathfield wrote:
On 09/08/2025 14:08, olcott wrote:
On 8/9/2025 12:31 AM, Richard Heathfield wrote:
On 09/08/2025 06:27, olcott wrote:
It is impossible to show how DD correctly simulated
by HHH can possibly reach its own emulated "ret"
instruction
So HHH never returns, so it fails to act as a termination analyzer >>>>>> because it fails to report its finding.
u32 Needs_To_Be_Aborted_Trace_HH
(Decoded_Line_Of_Code* execution_trace,
-a-aDecoded_Line_Of_Code *current);
Line 996 matches the
*recursive simulation non-halting behavior pattern*
https://github.com/plolcott/x86utm/blob/master/Halt7.c
If HHH doesn't have to report because its u32 needs to be aborted,
you can simplify the code immeasurably.
*That return value is passed back to line 1143 of HHH*
-a-a if (Decide_Halting_HH(&Aborted, &execution_trace, &decoded,
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a code_end, End_Of_Code, &master_state,
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a &slave_state, &slave_stack, Root))
-a-a-a-a-a-a goto END_OF_CODE;
-a-a *Aborted-a-a-a-a-a-a-a-a = 0x90909090; // deprecated
-a-a *execution_trace = 0x90909090;
-a-a return 0;-a // Does not halt
END_OF_CODE:
-a-a *Aborted-a-a-a-a-a-a-a-a = 0x90909090; // deprecated
-a-a *execution_trace = 0x90909090;
-a-a return 1; // Input has normally terminated
}
So HHH /does/ return... with the wrong answer, a la Turing. QED.
*It is only the wrong answer to the wrong problem*
Asking HHH to report on the behavior of the directly
executed DD() is like asking sum(3,5) to report on
the sum of 7 + 2.