Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| Subject | Re: SOLUTION TO THE HALTING PROBLEM! |
|---|---|
| Newsgroups | comp.theory, comp.ai.philosophy |
| References | (14 earlier) <BG0nH.97951$Ml5.89653@fx24.iad> <8bOdnWNsDbi_NAHCnZ2dnUU7-RHNnZ2d@giganews.com> <Ud4nH.249495$d95.157166@fx06.iad> <GNadnZINrb8LSwHCnZ2dnUU7-KHNnZ2d@giganews.com> <0693f701-f156-4bd8-a498-b73ba863b8f4n@googlegroups.com> |
| From | olcott <NoOne@NoWhere.com> |
| Date | 2020-10-30 22:41 -0500 |
| Message-ID | <I5KdnSxGodF0QQHCnZ2dnUU7-RPNnZ2d@giganews.com> (permalink) |
Cross-posted to 2 groups.
On 10/30/2020 10:25 PM, Graham Cooper wrote:
> On Saturday, October 31, 2020 at 1:14:38 PM UTC+10, olcott wrote:
>
>> void H_Hat(u32 P)
>> {
>> if (Aborted_Because_Non_Halting_Behavior_Detected(P, P))
>> MOV_EAX_1 // Execution of P(P) has been aborted
>> else
>> {
>> MOV_EAX_0 // P(P) has halted
>> HERE: goto HERE;
>> }
>> HALT
>> }
>
>
> that looks RIGHT!
>
> Im not going through the Rest
>
> youve made a POINT (after 5000 man hours of ppls time)
Yes. I have been working on this since 2004 and there are 11,679
messages from me in this group since then.
I finally have the essence of the proof so simple that a bright high
school student knowing nothing about computer science can understand it.
I had to create a whole x86utm operating system to make sure that every
detail of my understanding could be empirically validated.
It is a system that executes UTM equivalent virtual machines that have
the x86 language as their machine description language.
x86 language ≡ von Neumann architecture ≡ UTM ≡ RASP Machine
As soon as I fix one little bug in the OS I can finally write the actual
halt deciding code that implements my 2018-12-13 @ 7:00 PM virtual
machine for deciding the Peter Linz H_Hat().
>> void H(u32 P, u32 I)
>> {
>> if (Aborted_Because_Non_Halting_Behavior_Detected(P, I))
>> MOV_EAX_1 // Execution of P(I) has been aborted
>> else
>> MOV_EAX_0 // P(I) has halted
>> HALT
>> }
>>
>>
>> int main()
>> {
>> u32 P = (u32)H_Hat;
>> H(P, P); // MOV_EAX_0
>> HALT
>> }
>>
>> The above code specifies one instance of H()
>> two instances of H_Hat() and two instances of
>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, 32 I)
>>
>> Each instance is in its own process context with its own memory and its
>> own stack. The outermost instance of the above function has seen a
>> longer execution trace than the inner instance. This allows the outer
>> instance to decide halting before the inner intance has a chance to
>> decide halting.
>>
>> The outermost instance (the one called in in H) of this function:
>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, 32 I)
>> returns true for its first parameter, in this case that is the outermost
>> instance of H_Hat.
>>
>> 2018-12-13 @ 7:00 PM solution.
>> The halt decider detects the non-halting behavior of the Linz H_Hat
>> equivalent when it calls the halt decider from the same machine address
>> a second time and there are no conditional branches in the H_Hat
>> execution trace that would terminate this otherwise infinite recursion.
>> x86 language ≡ von Neumann architecture ≡ UTM ≡ RASP Machine
>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I);
>> Stops executing and Accepts any and all non-halting inputs and Rejects
>> any and all halting inputs.
>>> Sometimes it seems that you halt the program
>>> because non-halting behavior was detected in the halt-detection logic
>>> (which you ar3 terming recurssion), but either the halt detector failed
>>> its requirement to be always halting (negating its ability to be a
>>> refutal to the proof) or it includes code that made it stop the infinite
>>> execution, thus the halt detector isn't working on itself properly, and
>>> is calling its own apparent non-halt (but actually halting) behavior as
>>> non-halting.
>>>
>>> This is causing your H to misdetect the proper operation of H_Hat2.
>>> Note, since I described a working methodology for handling H_Hat2 in a
>>> halt detector, you can't claim that the error in inevitable, it only
>>> comes from a flaw in the design of YOU version of H.
>>>
>>> Now, yes, if you are going to totally redefine the question so it is
>>> really about what H did, and not about what the machine M(N) will do,
>>> then yes, you can make all sorts of claims, but in doing so you have
>>> left the realm of being anywhere useful to answer the question being put
>>> to the Halt Decider in Linz, and thus you have no impact on it.
>>>
>>> You are going to need to make a decision about what track you want to
>>> make. Either you are going to make you statements be applicable to Linz,
>>> in which case the results really need to be about M(N), and hot about
>>> internal details of a particular H(), which will mean you need to be
>>> able to get the right answer for H_Hat2, which is clearly Halting (so
>>> not needing to be aborted).
>>>
>>> The other option is to continue to talk about this particular H you are
>>> defining with a LOT of work (but still sounds like you haven't figured
>>> out the really hard part of how to detect the non-halting behavior), and
>>> forgo that it is actually applicable to Linz, but see if this decider is
>>> userul for anything.
>>>
>>> Maybe you can build an arguement that it is ok for H to get wrong the
>>> exceptional cases where it can be shown that the M(N) is using H(M, N)
>>> to act contrary to it, but to be similar to the H in Linz, it MUST get
>>> all other Turing Machines right. Maybe this machine needs 3 terminal
>>> states, the Turing Machine will Halt, the Turning Machine will never
>>> Halt, and the Turing Machine is going to be Contradictory. If you can
>>> actually make or even describe how to build such a machine it would be
>>> fantastic and change mathematics. If you can even show that it is
>>> plausable that such a machine could be made, but there are a few issue
>>> that need details worked out, woudl be good. Even describing how you
>>> will detect the Contrary case (fully) might be an accomplishment, but if
>>> you try, be prepared for people to be throwing cases at you that you
>>> didn't think of.
>>>
>>> My first guess is that even this modified halt detector would be shown
>>> to be impossible by some of the other halt decider proofs.
>>>
>> --
>> Copyright 2020 Pete Olcott
>
>
>
> http://minibase.com/index.php?q=look++_
>
>
--
Copyright 2020 Pete Olcott
"Great spirits have always encountered violent opposition from mediocre
minds." Einstein
Back to comp.theory | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
SOLUTION TO THE HALTING PROBLEM! Graham Cooper <grahamcooper7@gmail.com> - 2020-10-28 17:36 -0700
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-28 20:24 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Graham Cooper <grahamcooper7@gmail.com> - 2020-10-28 19:44 -0700
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-28 22:17 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Graham Cooper <grahamcooper7@gmail.com> - 2020-10-28 23:13 -0700
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-29 07:14 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Graham Cooper <grahamcooper7@gmail.com> - 2020-10-29 05:49 -0700
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-29 07:57 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Richard Damon <Richard@Damon-Family.org> - 2020-10-29 08:51 -0400
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-29 08:04 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Richard Damon <Richard@Damon-Family.org> - 2020-10-29 09:22 -0400
Re: SOLUTION TO THE HALTING PROBLEM! Graham Cooper <grahamcooper7@gmail.com> - 2020-10-29 10:22 -0700
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-29 15:39 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Richard Damon <Richard@Damon-Family.org> - 2020-10-30 00:13 -0400
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-29 23:51 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Richard Damon <Richard@Damon-Family.org> - 2020-10-30 09:12 -0400
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-30 11:05 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Richard Damon <Richard@Damon-Family.org> - 2020-10-30 16:27 -0400
Re: SOLUTION TO THE HALTING PROBLEM! Graham Cooper <grahamcooper7@gmail.com> - 2020-10-30 14:44 -0700
Re: SOLUTION TO THE HALTING PROBLEM! Richard Damon <Richard@Damon-Family.org> - 2020-10-30 18:50 -0400
Re: SOLUTION TO THE HALTING PROBLEM! Graham Cooper <grahamcooper7@gmail.com> - 2020-10-30 16:04 -0700
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-30 16:58 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Richard Damon <Richard@Damon-Family.org> - 2020-10-30 18:43 -0400
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-30 19:00 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Graham Cooper <grahamcooper7@gmail.com> - 2020-10-30 17:07 -0700
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-30 19:14 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Graham Cooper <grahamcooper7@gmail.com> - 2020-10-30 17:29 -0700
Re: SOLUTION TO THE HALTING PROBLEM! Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-31 01:26 +0000
Re: SOLUTION TO THE HALTING PROBLEM! Richard Damon <Richard@Damon-Family.org> - 2020-10-30 22:46 -0400
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-30 22:14 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Graham Cooper <grahamcooper7@gmail.com> - 2020-10-30 20:25 -0700
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-30 22:41 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Graham Cooper <grahamcooper7@gmail.com> - 2020-10-30 23:30 -0700
Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-29 23:56 -0500
Stop crossposting you imbecil spammer (Was: SOLUTION TO THE HALTING PROBLEM!) Mostowski Collapse <janburse@fastmail.fm> - 2020-10-29 14:01 +0100
Re: Stop crossposting you imbecil spammer (Re: SOLUTION TO THE HALTING PROBLEM! Mostowski Collapse <janburse@fastmail.fm> - 2020-10-29 19:39 +0100
Re: Stop crossposting you imbecil spammer (Re: SOLUTION TO THE HALTING PROBLEM! olcott <NoOne@NoWhere.com> - 2020-10-29 13:43 -0500
Re: SOLUTION TO THE HALTING PROBLEM! Mostowski Collapse <janburse@fastmail.fm> - 2020-10-29 20:49 +0100
Re: SOLUTION TO THE HALTING PROBLEM! Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-29 13:09 -0700
csiph-web