Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.theory > #134092
| From | Kaz Kylheku <643-408-1753@kylheku.com> |
|---|---|
| Newsgroups | comp.theory |
| Subject | Re: D simulated by H cannot possibly reach past its own first line |
| Date | 2025-10-28 19:56 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <20251028123744.602@kylheku.com> (permalink) |
| References | (22 earlier) <20251027204814.246@kylheku.com> <10dpf7i$1j14m$1@dont-email.me> <20251027225453.725@kylheku.com> <10dqmrp$249fe$1@dont-email.me> <10dr41k$29u1f$1@dont-email.me> |
On 2025-10-28, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:
> On 10/28/2025 8:18 AM, Mike Terry wrote:
>> On 28/10/2025 06:02, Kaz Kylheku wrote:
>>> On 2025-10-28, olcott <polcott333@gmail.com> wrote:
>>>> On 10/27/2025 10:54 PM, Kaz Kylheku wrote:
>>>>> On 2025-10-28, olcott <polcott333@gmail.com> wrote:
>>>>>> On 10/27/2025 10:40 PM, Kaz Kylheku wrote:
>>>>>>> On 2025-10-28, olcott <polcott333@gmail.com> wrote:
>>>>>>>> Once H has correctly determines that its simulated
>>>>>>>> D cannot possibly reach its own simulated "return"
>>>>>>>> instruction final halt state it is nutty to do
>>>>>>>> anything else besides abort and reject the input.
>>>>>>>
>>>>>>> I have traces which prove otherwise.
>>>>>>
>>>>>> Then you can't be telling the truth.
>>>>>
>>>>> LOL!
>>>>>
>>>>> Have you forgotten? (Sigh, I'm afraid the answer is yes ...)
>>>>>
>>>>> - You used to post execution traces claiming that they
>>>>> proved you were right.
>>>>>
>>>>> - You used to deride others for not following your
>>>>> execution traces in detail (maybe they are not skilled
>>>>> engineers)
>>>>>
>>>>>>
>>>>>> int D()
>>>>>> {
>>>>>> int Halt_Status = H(D);
>>>>>> if (Halt_Status)
>>>>>> HERE: goto HERE;
>>>>>> return Halt_Status;
>>>>>> }
>>>>>>
>>>>>> H simulates D
>>>>>> that calls H(D) to simulate D
>>>>>
>>>>> This is just empty claptrap about an ill-defined program
>>>>> with a missing definition of H, not an execution trace.
>>>>>
>>>>
>>>> So you cannot begin to imagine WTF happens when D
>>>> is simulated by H?
>>>
>>> Of course I can. First H has to call Init_Halts_H to allocate resources
>>> for the simulation and do certain initialiations not particuliar to D.
>>>
>>> Then Init_Slave_State to point the simulation at D and prime its stack.
>>>
>>> Then a function called Decide_Halting is called that contains the
>>> main single stepping loop which checks for certain conditions with
>>> a helper function called Needs_To_Be_Aborted.
>>>
>>> Decide_Halting pushes each decoded instruction into the shared trace
>>> buffer which is examined by Needs_To_Be_Aborted.
>>>
>>> I've diescovered that this trace buffer can be virtually infinite; I
>>> turned it into a sliding window due to needing more space, but not
>>> wanting to modify the Halt7.obj whose compiled code establishes the
>>> trace buffer size.
>>>
>>> When the execution trace buffer fills up, we don't have to abort
>>> the x86utm. We can just trim old information at the front of
>>> the buffer and move it down. Unless I'm mistaken, The abort decisions
>>> are made by looking backwards from the end of the buffer; they don't
>>> need the full history.
>>>
>>
>> Hmm. The trace buffer can certainly be compressed significantly:
>>
>> a) Only the following are significant:
>> - call instructions
>> - unconditional branch instructions
>> - conditional branch instructions
>>
>> b) I can't see any need to ever go back further than the last
>> conditional branch instruction
>>
>> c) For a given call or branch instruction, having a given (instruction
>> address, target address) combination, the backwards scan for a such a
>> pair will never go back further than the latest call or branch
>> instruction that matches. So no harm in deleting earlier entries,
>> provided every branch/call instruction deleted has a subsequent matching
>> entry.
>>
>> Aside from the above (which are based on PO's pattern matching rules), I
>> don't think it would be safe to prune further. In principle, an earlier
>> call might not be matched until 30GB of trace later. (Of course, with
>> further knowledge about /what/ is being decided we might know better,
>> but in general (a)(b)(c) seems the best that is guaranteed for arbitrary
>> input.)
>>
>> But most of all I'm surprised PO's trace buffer would fill up, unless
>> there is an infinite loop in the picture.
>
> Humm... How many times does HHH(DD) return to dictate what DD should do,
> halt or not... If it just sits there recursing, it might never return to
During the initial simulation, we do see two DDD simulations fire up.
So we have the first level whose instructions are traced. It calls
into HHH, which goes into into a complicated x86emu, all of whose
numerous instructions are traced just to simulate one instruction
of the second level DDD.
Then when I resume the original DDD with "reckoning", two more DDD
simulations fire up again.
So by then there is enough shit circling the toilet bowl by then that a
clog is imminent.
> DD? If Olcott needs to artificially terminate the "internal" HHH(DD)
> recursion? Try to avoid blowing the stack in a sense... If it does
> return to DD, than BAM all of those return values are going to be
> exposed to DD via Halt_Status, DD will halt or hit that GOTO loop. It
> reminds me of a recursion with a limit. If that limit is breached, then
> Olcott says DD is non-halting! Well, that is totally wrong... DD can
> sometimes halt, other times, not-halt. Fair enough?
Launching a simulation isn't a recursive call though; control does
not pass from the master to the slave. Control passes from the master
into a loop which simulates the slave. In Olcott's system, the slave
gets its own stack, so it is like a cooperative thread. (He knows it;
he has referred to the x86utm as a cooperatively tasked OS.)
If we liberate the memory occupied by simualtions which have terminated,
it's possible that the tower could be capable executing forever in a
fixed amount of RAM, if there is a master loop which pushes it forward:
the reckoning module or something like it has to keep monitoring the
list of simulations and carefully pick the right ones to push forward.
Not all the simulations in the list are abandoned. E.g. in our above
scenario when the top DDD is abandoned, its child DDD is not abandoned;
it is still referenced by DDD.
If we track the parentage between simulations (seems easily dable) then
we can sweep through the list and identify a simulation which has no
parent that is still in the list. We can step that one to completion and
then remove it from the list, and repeat.
With the right test case, this should just run forever, in spite
of the individual simulations terminating.
One thing that must be considered is that the reckoning module does
not record execution traces.
>
>
>> (Your "infinite tower" would
>> constitute such a loop, I guess, but then by the time you need to
>> compress, isn't it clear there's such an infinite loop, so no point
>> going further?
>
> For some reason it makes me think of iteration vs. recursion. Humm...
The launch of a simulation is a function call if it is done
to completion: the caller who launched the simulation is suspended
until the simulation ends.
This kind of function call powers most of or modern tech stacks,
which make use of languages which are interpreted directly or via
virtual machines.
When an interpreted function is called, the caller actually starts
a simulation; it has called into a loop in the virtual machine.
Because there is no execution monitoring and no abort, we have
a perfect illusion that control has passed into the VM domain
and then returned.
VMs can allocate their resources on the "native" stack, so that
runaway recursion among VM functions can blow the real stack.
--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca
Back to comp.theory | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-25 12:53 -0500
Re: No human has been able to understand this simple C in three years Bonita Montero <Bonita.Montero@gmail.com> - 2025-10-25 20:05 +0200
Re: No human has been able to understand this simple C in three years dbush <dbush.mobile@gmail.com> - 2025-10-25 14:20 -0400
Re: No human has been able to understand this simple C in three years Richard Heathfield <rjh@cpax.org.uk> - 2025-10-25 20:44 +0100
Re: No human has been able to understand this simple C in three years dart200 <user7160@newsgrouper.org.invalid> - 2025-10-25 11:44 -0700
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-25 13:58 -0500
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-26 17:17 -0500
Re: No human has been able to understand this simple C in three years Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 00:44 +0000
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-26 19:51 -0500
Re: No human has been able to understand this simple C in three years dbush <dbush.mobile@gmail.com> - 2025-10-26 21:06 -0400
Re: No human has been able to understand this simple C in three years "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-26 18:09 -0700
Re: No human has been able to understand this simple C in three years Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 01:16 +0000
A dishonest dodge is all that Kaz has olcott <polcott333@gmail.com> - 2025-10-26 20:20 -0500
Re: A dishonest dodge is all that Kaz has dbush <dbush.mobile@gmail.com> - 2025-10-26 21:28 -0400
Re: A dishonest dodge is all that Kaz has olcott <polcott333@gmail.com> - 2025-10-26 20:32 -0500
Re: A dishonest dodge is all that Kaz has dbush <dbush.mobile@gmail.com> - 2025-10-26 21:38 -0400
Re: A dishonest dodge is all that Kaz has Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 01:50 +0000
Kaz is now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-26 20:58 -0500
Re: Kaz is now dishonored in his deceit Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 02:02 +0000
Re: Kaz is now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-26 21:04 -0500
Re: Kaz is now dishonored in his deceit Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 03:46 +0000
Kaz proves his deceit by dodging this simple point --- Is Kaz just a Liar ??? olcott <polcott333@gmail.com> - 2025-10-26 23:10 -0500
Re: Kaz proves his deceit by dodging this simple point --- Is Kaz just a Liar ??? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 04:52 +0000
Re: Kaz proves his deceit by dodging this simple point --- Is Kaz just a Liar ??? Richard Damon <Richard@Damon-Family.org> - 2025-10-27 20:59 -0400
Re: Kaz is now dishonored in his deceit André G. Isaak <agisaak@gm.invalid> - 2025-10-26 20:15 -0600
Re: Kaz is now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-26 21:20 -0500
Re: Kaz is now dishonored in his deceit "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-26 19:25 -0700
Re: Kaz is now dishonored in his deceit dbush <dbush.mobile@gmail.com> - 2025-10-26 22:35 -0400
Re: Kaz is now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-26 21:38 -0500
Re: Kaz is now dishonored in his deceit dbush <dbush.mobile@gmail.com> - 2025-10-26 22:43 -0400
Re: Kaz is now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-26 21:45 -0500
olcott tries to hide the evidence that he admitted the input to HHH(DD) is halting dbush <dbush.mobile@gmail.com> - 2025-10-26 22:47 -0400
dbush is now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-26 21:52 -0500
olcott tries to hide the evidence that he admitted the input to HHH(DD) is halting dbush <dbush.mobile@gmail.com> - 2025-10-26 22:57 -0400
dbush proves his deceit by dodging this simple point olcott <polcott333@gmail.com> - 2025-10-26 22:11 -0500
Can someone from comp.lang.c or comp.lang.c++ help out here? olcott <polcott333@gmail.com> - 2025-10-26 22:02 -0500
olcott tries to hide the evidence that he admitted the input to HHH(DD) is halting dbush <dbush.mobile@gmail.com> - 2025-10-26 23:04 -0400
dbush proves is deceit by dodging this simple point olcott <polcott333@gmail.com> - 2025-10-26 22:09 -0500
olcott tries to hide the evidence that he admitted the input to HHH(DD) is halting dbush <dbush.mobile@gmail.com> - 2025-10-26 23:14 -0400
dbush proves his deceit by dodging this simple point --- dbush is a bot? olcott <polcott333@gmail.com> - 2025-10-26 22:42 -0500
olcott tries to hide the evidence that he admitted the input to HHH(DD) is halting dbush <dbush.mobile@gmail.com> - 2025-10-27 07:25 -0400
Re: Kaz is now dishonored in his deceit Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 04:47 +0000
Re: Kaz is now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-26 23:54 -0500
Re: Kaz is now dishonored in his deceit dbush <dbush.mobile@gmail.com> - 2025-10-27 07:30 -0400
Re: Kaz is now dishonored in his deceit Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 18:36 +0000
Re: Kaz is now dishonored in his deceit "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-27 11:55 -0700
Re: Kaz is now dishonored in his deceit Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-10-27 05:59 +0000
Re: Kaz is now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-27 08:18 -0500
Re: Kaz is now dishonored in his deceit Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-10-27 16:50 +0000
Re: Kaz is now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-27 11:58 -0500
Re: Kaz is now dishonored in his deceit "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-27 11:48 -0700
Re: Kaz is now dishonored in his deceit Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-10-27 03:31 +0100
Re: Kaz is now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-26 21:36 -0500
Re: Kaz is now dishonored in his deceit cross@spitfire.i.gajendra.net (Dan Cross) - 2025-10-27 14:08 +0000
I am only in these groups because I have been cheated out of a fair review. olcott <polcott333@gmail.com> - 2025-10-27 09:48 -0500
Re: A dishonest dodge is all that Kaz has Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 01:38 +0000
Re: A dishonest dodge is all that Kaz has --- Now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-26 20:45 -0500
Re: A dishonest dodge is all that Kaz has --- Now dishonored in his deceit dbush <dbush.mobile@gmail.com> - 2025-10-26 21:49 -0400
dbush is now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-26 20:56 -0500
Re: dbush is now dishonored in his deceit dbush <dbush.mobile@gmail.com> - 2025-10-26 22:05 -0400
Re: dbush is now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-26 21:15 -0500
olcott tries to hide the evidence that he admitted the input to HHH(DD) is halting dbush <dbush.mobile@gmail.com> - 2025-10-26 22:33 -0400
Re: A dishonest dodge is all that Kaz has --- Now dishonored in his deceit Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 01:57 +0000
Kaz is now dishonored in his deceit olcott <polcott333@gmail.com> - 2025-10-26 20:59 -0500
Re: No human has been able to understand this simple C in three years Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-10-27 04:32 +0000
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-26 23:35 -0500
Re: No human has been able to understand this simple C in three years Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 16:45 +0000
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 11:53 -0500
Re: No human has been able to understand this simple C in three years Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 18:48 +0000
Re: No human has been able to understand this simple C in three years Richard Damon <Richard@Damon-Family.org> - 2025-10-25 21:20 -0400
Re: No human has been able to understand this simple C in three years Mikko Levanto <mikko.levanto@iki.fi> - 2025-10-26 11:06 +0200
Re: No human has been able to understand this simple C in three years Bonita Montero <Bonita.Montero@gmail.com> - 2025-10-27 09:11 +0100
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 08:15 -0500
Re: No human has been able to understand this simple C in three years Bonita Montero <Bonita.Montero@gmail.com> - 2025-10-27 16:04 +0100
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 10:19 -0500
Re: No human has been able to understand this simple C in three years Bonita Montero <Bonita.Montero@gmail.com> - 2025-10-27 17:41 +0100
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 11:52 -0500
Re: No human has been able to understand this simple C in three years Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 16:58 +0000
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 12:02 -0500
Re: No human has been able to understand this simple C in three years Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 18:42 +0000
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 13:53 -0500
Re: No human has been able to understand this simple C in three years dbush <dbush.mobile@gmail.com> - 2025-10-27 15:20 -0400
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 14:33 -0500
Re: No human has been able to understand this simple C in three years dbush <dbush.mobile@gmail.com> - 2025-10-27 15:40 -0400
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 14:53 -0500
Re: No human has been able to understand this simple C in three years dbush <dbush.mobile@gmail.com> - 2025-10-27 16:12 -0400
PO Meltdown? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 20:48 +0000
Re: PO Meltdown? dbush <dbush.mobile@gmail.com> - 2025-10-27 17:07 -0400
Re: PO Meltdown? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 21:14 +0000
Re: PO Meltdown? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 00:37 +0000
Kaz is a damned liar olcott <polcott333@gmail.com> - 2025-10-27 19:44 -0500
Re: Kaz is a damned liar Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 00:52 +0000
Re: Kaz is a damned liar "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-27 19:05 -0700
Kaz is a damned liar olcott <polcott333@gmail.com> - 2025-10-27 19:44 -0500
Re: PO Meltdown? Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-10-28 02:24 +0000
D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-10-27 22:18 -0500
Re: D simulated by H cannot possibly reach past its own first line dbush <dbush.mobile@gmail.com> - 2025-10-27 23:27 -0400
Re: D simulated by H cannot possibly reach past its own first line Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 03:40 +0000
Re: D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-10-27 22:45 -0500
Re: D simulated by H cannot possibly reach past its own first line dbush <dbush.mobile@gmail.com> - 2025-10-27 23:47 -0400
Re: D simulated by H cannot possibly reach past its own first line Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 03:54 +0000
Re: D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-10-27 23:01 -0500
Re: D simulated by H cannot possibly reach past its own first line Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 06:02 +0000
Re: D simulated by H cannot possibly reach past its own first line Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-10-28 15:18 +0000
Re: D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-10-28 11:21 -0500
Re: D simulated by H cannot possibly reach past its own first line Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 16:44 +0000
Re: D simulated by H cannot possibly reach past its own first line Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-10-28 17:24 +0000
Re: D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-10-28 15:15 -0500
Re: D simulated by H cannot possibly reach past its own first line dbush <dbush.mobile@gmail.com> - 2025-10-28 16:18 -0400
Re: D simulated by H cannot possibly reach past its own first line Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 20:23 +0000
Re: D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-10-28 16:00 -0500
Re: D simulated by H cannot possibly reach past its own first line Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 21:23 +0000
Re: D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-10-28 16:33 -0500
Re: D simulated by H cannot possibly reach past its own first line dbush <dbush.mobile@gmail.com> - 2025-10-28 18:01 -0400
Re: D simulated by H cannot possibly reach past its own first line "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-28 12:03 -0700
Re: D simulated by H cannot possibly reach past its own first line Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 19:56 +0000
Re: D simulated by H cannot possibly reach past its own first line "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-28 13:27 -0700
Re: D simulated by H cannot possibly reach past its own first line joes <noreply@example.org> - 2025-10-28 08:40 +0000
Re: D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-10-28 09:43 -0500
Re: D simulated by H cannot possibly reach past its own first line "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-28 12:08 -0700
Re: D simulated by H cannot possibly reach past its own first line joes <noreply@example.org> - 2025-11-03 14:06 +0000
Re: D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-11-03 10:13 -0600
Re: D simulated by H cannot possibly reach past its own first line dbush <dbush.mobile@gmail.com> - 2025-10-28 00:04 -0400
Re: D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-10-27 23:29 -0500
Re: D simulated by H cannot possibly reach past its own first line Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 05:48 +0000
Re: D simulated by H cannot possibly reach past its own first line "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-27 22:51 -0700
Re: D simulated by H cannot possibly reach past its own first line dbush <dbush.mobile@gmail.com> - 2025-10-28 07:48 -0400
Re: PO Meltdown? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 03:31 +0000
Re: PO Meltdown? wij <wyniijj5@gmail.com> - 2025-10-28 13:25 +0800
Re: PO Meltdown? olcott <polcott333@gmail.com> - 2025-10-28 00:32 -0500
Re: PO Meltdown? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 05:53 +0000
D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-10-28 09:27 -0500
Re: D simulated by H cannot possibly reach past its own first line Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 16:48 +0000
Re: D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-10-28 15:23 -0500
Re: D simulated by H cannot possibly reach past its own first line Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 21:26 +0000
D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-10-28 00:27 -0500
Re: D simulated by H cannot possibly reach past its own first line "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-27 22:46 -0700
D simulated by H cannot possibly reach past its own first line olcott <polcott333@gmail.com> - 2025-10-27 21:58 -0500
Re: D simulated by H cannot possibly reach past its own first line "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-27 19:59 -0700
Re: D simulated by H cannot possibly reach past its own first line dbush <dbush.mobile@gmail.com> - 2025-10-27 23:10 -0400
Kaz insists on dodging this point only because he knows it is irrefutable olcott <polcott333@gmail.com> - 2025-10-27 17:40 -0500
Re: Kaz insists on dodging this point only because he knows it is irrefutable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 00:23 +0000
Re: Kaz insists on dodging this point only because he knows it is irrefutable olcott <polcott333@gmail.com> - 2025-10-27 19:29 -0500
Re: Kaz insists on dodging this point only because he knows it is irrefutable dbush <dbush.mobile@gmail.com> - 2025-10-27 20:32 -0400
Re: Kaz insists on dodging this point only because he knows it is irrefutable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 00:41 +0000
Re: Kaz insists on dodging this point only because he knows it is irrefutable +++ olcott <polcott333@gmail.com> - 2025-10-27 19:48 -0500
Re: Kaz insists on dodging this point only because he knows it is irrefutable +++ dbush <dbush.mobile@gmail.com> - 2025-10-27 20:52 -0400
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 18:01 -0500
Re: No human has been able to understand this simple C in three years dbush <dbush.mobile@gmail.com> - 2025-10-27 19:05 -0400
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 18:11 -0500
Re: No human has been able to understand this simple C in three years "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-27 18:38 -0700
Re: No human has been able to understand this simple C in three years Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-28 03:21 +0000
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 22:44 -0500
Re: No human has been able to understand this simple C in three years dbush <dbush.mobile@gmail.com> - 2025-10-27 23:46 -0400
Re: No human has been able to understand this simple C in three years "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-27 22:38 -0700
Re: No human has been able to understand this simple C in three years dbush <dbush.mobile@gmail.com> - 2025-10-28 07:55 -0400
Re: No human has been able to understand this simple C in three years tTh <tth@none.invalid> - 2025-10-27 18:57 +0100
Re: No human has been able to understand this simple C in three years Mikko <mikko.levanto@iki.fi> - 2025-10-27 12:10 +0200
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 08:45 -0500
Re: No human has been able to understand this simple C in three years Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 17:03 +0000
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 12:05 -0500
Re: No human has been able to understand this simple C in three years tTh <tth@none.invalid> - 2025-10-27 19:00 +0100
Re: No human has been able to understand this simple C in three years Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-27 19:59 +0000
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-27 17:38 -0500
Re: No human has been able to understand this simple C in three years Mikko <mikko.levanto@iki.fi> - 2025-10-28 11:09 +0200
Re: No human has been able to understand this simple C in three years Richard Heathfield <rjh@cpax.org.uk> - 2025-10-28 10:06 +0000
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-28 09:52 -0500
Re: No human has been able to understand this simple C in three years Mikko <mikko.levanto@iki.fi> - 2025-10-29 13:02 +0200
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-29 11:29 -0500
Re: No human has been able to understand this simple C in three years "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-29 12:48 -0700
Re: No human has been able to understand this simple C in three years Mikko <mikko.levanto@iki.fi> - 2025-10-30 12:24 +0200
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-30 08:15 -0500
Re: No human has been able to understand this simple C in three years Mikko <mikko.levanto@iki.fi> - 2025-10-31 13:53 +0200
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-31 08:42 -0500
Re: No human has been able to understand this simple C in three years dbush <dbush.mobile@gmail.com> - 2025-10-31 10:13 -0400
Re: No human has been able to understand this simple C in three years Mikko <mikko.levanto@iki.fi> - 2025-11-01 11:22 +0200
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-11-01 08:27 -0500
Re: No human has been able to understand this simple C in three years dbush <dbush.mobile@gmail.com> - 2025-11-01 09:53 -0400
understand this simple C ? --- counter-factual assumptions olcott <polcott333@gmail.com> - 2025-11-01 09:22 -0500
Re: understand this simple C ? --- counter-factual assumptions dbush <dbush.mobile@gmail.com> - 2025-11-01 10:37 -0400
Re: understand this simple C ? --- counter-factual assumptions olcott <polcott333@gmail.com> - 2025-11-01 09:41 -0500
Re: understand this simple C ? --- counter-factual assumptions dbush <dbush.mobile@gmail.com> - 2025-11-01 11:24 -0400
Re: understand this simple C ? --- counter-factual assumptions olcott <polcott333@gmail.com> - 2025-11-01 10:32 -0500
Re: understand this simple C ? --- counter-factual assumptions dbush <dbush.mobile@gmail.com> - 2025-11-01 11:44 -0400
Re: understand this simple C ? --- counter-factual assumptions olcott <polcott333@gmail.com> - 2025-11-01 12:04 -0500
Re: understand this simple C ? --- counter-factual assumptions dbush <dbush.mobile@gmail.com> - 2025-11-01 14:14 -0400
Re: No human has been able to understand this simple C in three years Mikko <mikko.levanto@iki.fi> - 2025-11-02 14:35 +0200
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-11-03 17:31 -0600
Re: No human has been able to understand this simple C in three years Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-11-03 23:48 +0000
Re: No human has been able to understand this simple C in three years Mikko <mikko.levanto@iki.fi> - 2025-11-04 12:00 +0200
Re: No human has been able to understand this simple C in three years Mikko <mikko.levanto@iki.fi> - 2025-10-29 13:01 +0200
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-28 09:55 -0500
Re: No human has been able to understand this simple C in three years Mikko <mikko.levanto@iki.fi> - 2025-10-29 13:03 +0200
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-29 11:29 -0500
Re: No human has been able to understand this simple C in three years "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-29 12:49 -0700
Re: No human has been able to understand this simple C in three years Mikko <mikko.levanto@iki.fi> - 2025-10-30 12:29 +0200
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-30 08:17 -0500
Re: No human has been able to understand this simple C in three years Mikko <mikko.levanto@iki.fi> - 2025-10-31 14:02 +0200
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-10-31 08:50 -0500
Re: No human has been able to understand this simple C in three years "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-31 12:58 -0700
Re: No human has been able to understand this simple C in three years Mikko <mikko.levanto@iki.fi> - 2025-11-01 11:32 +0200
Re: No human has been able to understand this simple C in three years olcott <polcott333@gmail.com> - 2025-11-01 08:32 -0500
Re: No human has been able to understand this simple C in three years "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-27 18:50 -0700
csiph-web