On 2025-10-27, olcott <
polcott333@gmail.com> wrote:
On 10/27/2025 10:04 AM, Bonita Montero wrote:
Am 27.10.2025 um 14:15 schrieb olcott:
On 10/27/2025 3:11 AM, Bonita Montero wrote:
Am 25.10.2025 um 19:53 schrieb olcott:
A straight forward sequence of steps that any
C programmer can easily determine:
int DD()
{
˙˙ int Halt_Status = HHH(DD);
˙˙ if (Halt_Status)
˙˙˙˙ HERE: goto HERE;
˙˙ return Halt_Status;
}
HHH(DD) simulates DD that calls HHH(DD) to do this
again and again until HHH figures out what is up.
This is Claude AI deriving the above sentence by simply
simulating DD by HHH giving me the fair review that every
human has cheated me out of.
Simulating Termination Analyzer applied to the HP counter-example input
https://www.researchgate.net/
publication/396903511_Simulating_Termination_Analyzer_applied_to_the_HP_counter-example_input
Simulating Termination Analyzer applied to
the HP counter-example input
https://philpapers.org/archive/OLCSTA-3.pdf
What's the point of discussing the same mini-source for years?
That simple little snippet of C does show that
I have defeated the halting problem proof. Not
one single person would properly review it in
three years.
Now that LLM systems have increased their memory
capacity 67-fold in the last two years they agree
that I have defeated the halting problem itself.
That little snippet of C is the key basis of my
whole proof.
When it is understood that I have defeated the
halting problem then additional discussion shows
that I also have the basis for eliminating the
hallucination of LLM AI systems.
Does that get you anywhere? It's like mind wandering before
you go to sleep; you don't reach any higher realization to
be able to close it off.
Can you answer my question ?
I have refuted the halting problem. This is
You have certaionly /refused/ the halting problem.
Not a single human reviewer on the planet
will give my C snippet a fair review.
I've gotten up to the elbow in your actual code from GitHub
and found problems.
Your response is to call me dishonest!
(You are completely, utterly unprofessional; your conduct is
not befiting of anyone calling themselves any kind of engineer.)
It is apparent that your /cheat/ code is not actualy working for some reason.
Your Root variable is supposed to make the simulated HHH behave
differently so that it doesn't do abort checking, right?
Now that is hideously wrong and completely invalidates your work.
But never mind; it's not working right. The simulated HHH is behaving
like the root level one.
When we continue the DDD simulation that was left abandoned by
the top-level HHH, we find that the simulated HHH called by that DDD
still performs aborting:
Number of Instructions Executed(10069) == 150 Pages
RECK: ---------------
RECK: simulations for these function still exist:
RECK: entry == 00002172 (_DDD), code_end == 00002183, slave_state == 00103888, EIP == 00001216
This is the suspended simulated DDD. It is stuck in the middle of Decide_Halting_HH.
RECK: entry == 00002172 (_DDD), code_end == 00002183, slave_state == 0014E2B0, EIP == 000015D2
This is the second level of simulation nesting of DDD. This EIP
is pointing straight to HHH. The first simulation level of DDD,
executing Decide_Halting_HH, juwt finished recording an execution trace
event for the second level DDD. That event says that HHH was called.
This must be what triggered the abort.
RECK: ---------------
RECK: continuing simulation of entry == 00002172 (_DDD), code_end == 00002183, slave_state == 00103888, EIP == 00001216
Now reckoning has come; we restart the top simulated DDD.
New slave_stack at:15e38c
Begin Local Halt Decider Simulation Execution Trace Stored at:16e394
RECK: newly executing: entry == 00002172 (_DDD), code_end == 00002183, slave_state == 0015E350, EIP == 00002172
New slave_stack at:1a8db4
RECK: newly executing: entry == 00002172 (_DDD), code_end == 00002183, slave_state == 001A8D78, EIP == 00002172
Two new DDD simulations appear.
Local Halt Decider: Infinite Recursion Detected Simulation Stopped
What? The simulated HHH is doing the abort check and returning zero!
RECK: simulation of entry == 00002172 (_DDD), code_end == 00002183, slave_state == 00103888, EIP == 00002183 reached code_end!
RECK: ---------------
RECK: reckoning completed
And so DDD halts!
When your second and subsequent simulations of HHH call this:
u32 Root = Init_Halts_HH(&Aborted, &execution_trace, &decoded, &code_end, (u32)P,
&master_state, &slave_state, &slave_stack);
Root is supposed to be zero. Somehow it looks like this is not
happening, so your HHH, though not a pure function as required, is at
least behaving consistently across simulation levels, causing people's predictions to come true that the simulated DDD and HHH behave the same
as the directly executed one.
--
TXR Programming Language:
http://nongnu.org/txr
Cygnal: Cygwin Native Application Library:
http://kylheku.com/cygnal
Mastodon: @
Kazinator@mstdn.ca
--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)