https://chatgpt.com/share/6709e046-4794-8011-98b7-27066fb49f3e
This link is live for the world. You can click on it
and try to convince ChatGPT that HHH is wrong to reject
DDD because the executed DDD does halt.
It will explain your mistake in clear simple language.
*The paper that this refers to*
Simulating Termination Analyzer H is Not Fooled by Pathological Input D https://www.researchgate.net/ publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D
https://chatgpt.com/share/6709e046-4794-8011-98b7-27066fb49f3e
This link is live for the world. You can click on it
and try to convince ChatGPT that HHH is wrong to reject
DDD because the executed DDD does halt.
It will explain your mistake in clear simple language.
*The paper that this refers to*
Simulating Termination Analyzer H is Not Fooled by Pathological Input D https://www.researchgate.net/ publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D
On 10/11/2024 7:50 PM, olcott wrote:
2024-10-12, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> schrieb:
On 10/11/2024 7:50 PM, olcott wrote:
[Schnipp]
As I see it, the main Halting Problem is Olcott not halting.
On 12.10.2024 11:32, Jan van den Broek wrote:
2024-10-12, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> schrieb:
On 10/11/2024 7:50 PM, olcott wrote:
[Schnipp]
As I see it, the main Halting Problem is Olcott not halting.
LOL! - A very nice one. Thanks for that. :-)
https://chatgpt.com/share/6709e046-4794-8011-98b7-27066fb49f3e
This link is live for the world. You can click on it
and try to convince ChatGPT that HHH is wrong to reject
DDD because the executed DDD does halt.
It will explain your mistake in clear simple language.
*The paper that this refers to*
Simulating Termination Analyzer H is Not Fooled by Pathological Input D https://www.researchgate.net/ publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D
Fully operational code is here. https://github.com/plolcott/x86utm/blob/master/Halt7.c
On 10/13/24 03:03, olcott wrote:
Fully operational code is here.
https://github.com/plolcott/x86utm/blob/master/Halt7.c
tth@redlady:~/Desktop$ gcc -Wall Halt7.c
Halt7.c: In function ‘Decide_Halting0’:
Halt7.c:239:32: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
PushBack(*execution_trace, (u32)*decoded, sizeof(Decoded_Line_Of_Code));
^
[...]
Halt7.c:847: Error: too many memory references for `mov'
Halt7.c:848: Error: too many memory references for `mov'
Halt7.c:928: Error: too many memory references for `lea'
Halt7.c:929: Error: too many memory references for `mov'
Halt7.c:930: Error: too many memory references for `lea'
Halt7.c:931: Error: too many memory references for `mov'
Halt7.c:932: Error: too many memory references for `mov'
Halt7.c:933: Error: too many memory references for `mov' tth@redlady:~/Desktop$
OK boomer.
On 10/12/2024 11:28 AM, Janis Papanagnou wrote:
On 12.10.2024 11:32, Jan van den Broek wrote:
2024-10-12, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> schrieb: >>>> On 10/11/2024 7:50 PM, olcott wrote:
[Schnipp]
As I see it, the main Halting Problem is Olcott not halting.
LOL! - A very nice one. Thanks for that. :-)
I second that. :^)
Compiles with Microsoft Visual Studio Community Edition 2017
This file has all the details https://github.com/plolcott/x86utm/blob/master/__Run_7.bat
Halt7.c is compiled and not linked with this line
cl /GS- /FA /FaHalt7.asm /c /arch:IA32 Halt7.c
The x86utm operating system is compiled and linked with this line
cl.exe /EHsc x86utm.cpp api.c decode.c mem.c ops.c ops2.c prim_ops.c
x86utm emulates the object code of Halt7.obj with this line:
x86utm Halt7.obj > Halt7out.txt
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 991 |
Nodes: | 10 (0 / 10) |
Uptime: | 119:32:47 |
Calls: | 12,958 |
Files: | 186,574 |
Messages: | 3,265,636 |