Re: HHH maps its input to the behavior specified by it --- key error in all the proofs

Liste des GroupesRevenir à theory 
Sujet : Re: HHH maps its input to the behavior specified by it --- key error in all the proofs
De : polcott333 (at) *nospam* gmail.com (olcott)
Groupes : comp.theory
Date : 11. Aug 2024, 03:43:24
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v994vs$10cfm$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
User-Agent : Mozilla Thunderbird
On 8/10/2024 8:13 PM, Richard Damon wrote:
On 8/10/24 8:51 PM, olcott wrote:
On 8/10/2024 7:20 PM, Richard Damon wrote:
On 8/10/24 7:52 PM, olcott wrote:
On 8/10/2024 5:47 PM, Richard Damon wrote:
On 8/10/24 6:41 PM, olcott wrote:
On 8/10/2024 4:53 PM, Richard Damon wrote:
On 8/10/24 5:37 PM, olcott wrote:
On 8/10/2024 4:33 PM, Richard Damon wrote:
On 8/10/24 5:18 PM, olcott wrote:
On 8/10/2024 3:58 PM, Richard Damon wrote:
On 8/10/24 4:36 PM, olcott wrote:
>
As I have countlessly proven it only requires enough correctly
emulated steps to correctly infer that the input would never
reach is "return" instruction halt state.
>
Except that HHH does't do that, since if HHH decides to abort and return, then the DDD that it is emulating WILL return, just after HHH has stopped its emulation.
>
You just confuse the behavior of DDD with the PARTIAL emulation that HHH does, because you lie about your false "tautology".
>
>
>
Denying a tautology seems to make you a liar. I only
say "seems to" because I know that I am fallible.
>
Claiming a false statement is a tautology only make you a liar.
>
In this case, you lie is that the HHH that you are talking about do the "correct emulation" you base you claim on.
>
That is just a deception like the devil uses, has just a hint of truth, but the core is a lie.
>
>
What I say is provably correct on the basis of the
semantics of the x86 language.
>
Nope.
>
The x86 language says DDD will Halt if HHH(DDD) returns a value.
>
HHH is called by main() there is no directly executed DDD()
any where in the whole computation.
>
>
Except in your requirements, and we can see what it does by adding a call to DDD from main, since nothing in your system calls main.
>
>
All that you need to know is that there is not any
directly executed DDD() anywhere in the computation.
>
But there ccould be, and the behavior of it is what matters.
>
>
The key error of the halting problem proofs all of these
years has been the false assumption that a halt decider
must report on the behavior of the computation that itself
is contained within.
>
But it isn't a false assemption, but an actual requirement.
>
A Halt Decider must be able to correctly answer for ANY Turing Machine represented as its input.
>
ANY includes those that are built from a copy of itself.
>
So, a Halt Decider needs to be able to correctly answer about programs that include copies of itself, even with contrary behavior, which is what makes it impossible to compute.
>
You seem to confuse non-computable with invalid, it seems in part because you don't understand the difference between knowledge and truth.
>
>
Everyone has simply assumed that the behavior of the
input to a decider must exactly match the direct execution
of this input. They only did this because everyone rejected
simulation out-of-hand without review.
>
Because that is the DEFINITION of what it is to decide on.
>
You just don't understand what a requirement is.
>
Since the DEFINITION of "Correct Simulation" that you are trying to use (from a UTM) means a machine the EXACTLY reproduces the behavior of the direct exectution of the machine described by the input, the correct simulation must exactly match the behavior of the direct execution.
>
You can't get out of it by trying to lie about it being different.
>
>
This caused them to never notice that the input simulated
according to its correct semantics does call its own decider
in recursive simulation thus cannot possibly return to its
caller. The Linz proof is sufficiently isomorphic so this equally
applies to the Linz TM proof.
>
Nope, just shows you don't know what "Correct" means.
>
Your proof is NOT "sufficiently isomorphic" since by your own claims it is clearly not even Turing Complete, so no where near isomorphic.
>
>
If HHH were to report on the direct execution of DDD it would
be breaking the definition of a halt decider that only computes
the mapping from its input...
>
Nope. Since the mapping that it is supposed to compute is DEFINED as based on the direct exectut
>
>
No it never has been this. I has always been a mapping
from the behavior that the finite string specifies. It
has never been the behavior of the actual computation
that the decider is contained within.
  And thatg behavior is specified to be the behavior of the program the input represents. PERIOD.
 
That has never been true. It is always the case that every
decider of any kind only computes the mapping from its input
finite string and never gives a rat's ass about anything else
anywhere else.
Ben should have known this. He didn't. People here that pretend
to know computer science should know that. That they don't proves
that they are (to some degree) fakers.
The semantics of my 100% fully specified concrete example
conclusively proves that the behavior of DDD correctly emulated
by HHH is a different sequence that the directly executed DDD().
Even a pretty stupid person can see that each HHH does emulate
its input correctly even if it does this by wild guess. They
*merely have to bother to pay attention that the emulated lines*
*are the same lines as the x86 source code of DDD*
That after three years no one has bothered to do that can't seem
to have any plausible explanation besides playing sadistic trollish
head games.
_DDD()
[00002172] 55         push ebp      ; housekeeping
[00002173] 8bec       mov ebp,esp   ; housekeeping
[00002175] 6872210000 push 00002172 ; push DDD
[0000217a] e853f4ffff call 000015d2 ; call HHH(DDD)
[0000217f] 83c404     add esp,+04
[00002182] 5d         pop ebp
[00002183] c3         ret
Size in bytes:(0018) [00002183]
Begin Local Halt Decider Simulation   Execution Trace Stored at:1138cc
[00002172][001138bc][001138c0] 55         push ebp      ; housekeeping
[00002173][001138bc][001138c0] 8bec       mov ebp,esp   ; housekeeping
[00002175][001138b8][00002172] 6872210000 push 00002172 ; push DDD
[0000217a][001138b4][0000217f] e853f4ffff call 000015d2 ; call HHH(DDD)
New slave_stack at:14e2ec
[00002172][0015e2e4][0015e2e8] 55         push ebp      ; housekeeping
[00002173][0015e2e4][0015e2e8] 8bec       mov ebp,esp   ; housekeeping
[00002175][0015e2e0][00002172] 6872210000 push 00002172 ; push DDD
[0000217a][0015e2dc][0000217f] e853f4ffff call 000015d2 ; call HHH(DDD)
Local Halt Decider: Infinite Recursion Detected Simulation Stopped
--
Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer

Date Sujet#  Auteur
2 Aug 24 * Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?395olcott
2 Aug 24 +* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?11Richard Damon
3 Aug 24 i`* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?10olcott
3 Aug 24 i `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?9Richard Damon
3 Aug 24 i  `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?8olcott
3 Aug 24 i   `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?7Richard Damon
3 Aug 24 i    `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?6olcott
3 Aug 24 i     `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?5Richard Damon
3 Aug 24 i      `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?4olcott
3 Aug 24 i       `* Re: Olcott is too stupid to know that only the DDD correctly simulated by onlly the HHH that doesn't abort cannot possibly reach its own return instruction?3Richard Damon
3 Aug 24 i        `* Who here is too stupid to know that DDD correctly simulated,by HHH cannot possibly reach its own return instruction?2olcott
3 Aug 24 i         `- Re: Who here is too stupid to know that DDD correctly simulated,by HHH cannot possibly reach its own return instruction?1Richard Damon
3 Aug 24 +* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?287Fred. Zwarts
3 Aug 24 i`* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?286olcott
3 Aug 24 i +* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?284Fred. Zwarts
3 Aug 24 i i`* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?283olcott
3 Aug 24 i i +- Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?1Fred. Zwarts
3 Aug 24 i i `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?281Richard Damon
3 Aug 24 i i  `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?280olcott
3 Aug 24 i i   +* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?278Richard Damon
3 Aug 24 i i   i`* Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?277olcott
3 Aug 24 i i   i `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?276Richard Damon
3 Aug 24 i i   i  `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?275olcott
3 Aug 24 i i   i   +* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?29Richard Damon
3 Aug 24 i i   i   i`* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?28olcott
3 Aug 24 i i   i   i `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?27Richard Damon
3 Aug 24 i i   i   i  `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?26olcott
3 Aug 24 i i   i   i   `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?25Richard Damon
3 Aug 24 i i   i   i    `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?24olcott
3 Aug 24 i i   i   i     `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?23Richard Damon
3 Aug 24 i i   i   i      `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?22olcott
3 Aug 24 i i   i   i       `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD21Richard Damon
3 Aug 24 i i   i   i        `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD20olcott
3 Aug 24 i i   i   i         `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD19Richard Damon
3 Aug 24 i i   i   i          `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD18olcott
4 Aug 24 i i   i   i           `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD17Richard Damon
4 Aug 24 i i   i   i            `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD16olcott
4 Aug 24 i i   i   i             `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD15Richard Damon
4 Aug 24 i i   i   i              `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD14olcott
4 Aug 24 i i   i   i               `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD13Richard Damon
4 Aug 24 i i   i   i                `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD12olcott
4 Aug 24 i i   i   i                 `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD11Richard Damon
4 Aug 24 i i   i   i                  `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD10olcott
4 Aug 24 i i   i   i                   +* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD3Richard Damon
4 Aug 24 i i   i   i                   i`* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD2olcott
4 Aug 24 i i   i   i                   i `- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD1Richard Damon
5 Aug 24 i i   i   i                   `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD6Mikko
5 Aug 24 i i   i   i                    `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD5olcott
7 Aug 24 i i   i   i                     `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state? BUT ONLY that DDD4Mikko
7 Aug 24 i i   i   i                      `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?3olcott
8 Aug 24 i i   i   i                       +- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?1Richard Damon
8 Aug 24 i i   i   i                       `- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?1Mikko
4 Aug 24 i i   i   `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?245Fred. Zwarts
4 Aug 24 i i   i    `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?244olcott
4 Aug 24 i i   i     `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?243Richard Damon
4 Aug 24 i i   i      `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?242olcott
4 Aug 24 i i   i       +- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?1Richard Damon
5 Aug 24 i i   i       +* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?236Mikko
5 Aug 24 i i   i       i`* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?235olcott
6 Aug 24 i i   i       i +* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?25Richard Damon
6 Aug 24 i i   i       i i`* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?24olcott
6 Aug 24 i i   i       i i `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?23Richard Damon
6 Aug 24 i i   i       i i  `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?22olcott
6 Aug 24 i i   i       i i   +* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?4wij
6 Aug 24 i i   i       i i   i`* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?3olcott
6 Aug 24 i i   i       i i   i +- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?1Richard Damon
6 Aug 24 i i   i       i i   i `- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?1wij
6 Aug 24 i i   i       i i   +- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?1Richard Damon
6 Aug 24 i i   i       i i   `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?16Mike Terry
6 Aug 24 i i   i       i i    +* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?14olcott
6 Aug 24 i i   i       i i    i+* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?5Richard Damon
6 Aug 24 i i   i       i i    ii`* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?4olcott
6 Aug 24 i i   i       i i    ii `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?3Richard Damon
6 Aug 24 i i   i       i i    ii  `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?2olcott
6 Aug 24 i i   i       i i    ii   `- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?1Richard Damon
6 Aug 24 i i   i       i i    i`* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?8Mike Terry
6 Aug 24 i i   i       i i    i `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?7olcott
6 Aug 24 i i   i       i i    i  +* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?5Mike Terry
6 Aug 24 i i   i       i i    i  i+* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?3olcott
6 Aug 24 i i   i       i i    i  ii`* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?2Mike Terry
6 Aug 24 i i   i       i i    i  ii `- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?1olcott
6 Aug 24 i i   i       i i    i  i`- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?1olcott
7 Aug 24 i i   i       i i    i  `- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?1Richard Damon
6 Aug 24 i i   i       i i    `- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?1Richard Damon
7 Aug 24 i i   i       i `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?209Mikko
7 Aug 24 i i   i       i  `* HHH computes the mapping from its input finite sting to the actual behavior specified by this finite string208olcott
7 Aug 24 i i   i       i   +* Re: HHH maps its input to the behavior specified by it206joes
7 Aug 24 i i   i       i   i+* Re: HHH maps its input to the behavior specified by it204olcott
8 Aug 24 i i   i       i   ii`* Re: HHH maps its input to the behavior specified by it203Richard Damon
8 Aug 24 i i   i       i   ii `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state202olcott
8 Aug 24 i i   i       i   ii  `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state201Richard Damon
8 Aug 24 i i   i       i   ii   +* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state2olcott
8 Aug 24 i i   i       i   ii   i`- Re: HHH maps its input to the behavior specified by it --- HHH never reaches its halt state so never decides, or it decides wrong.1Richard Damon
8 Aug 24 i i   i       i   ii   +* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state2olcott
8 Aug 24 i i   i       i   ii   i`- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state1Richard Damon
8 Aug 24 i i   i       i   ii   +* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state2olcott
8 Aug 24 i i   i       i   ii   i`- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state1Richard Damon
8 Aug 24 i i   i       i   ii   +* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state2olcott
8 Aug 24 i i   i       i   ii   i`- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state1Richard Damon
8 Aug 24 i i   i       i   ii   +* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state2olcott
8 Aug 24 i i   i       i   ii   i`- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state1Richard Damon
8 Aug 24 i i   i       i   ii   +* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state186olcott
8 Aug 24 i i   i       i   ii   +* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state2olcott
8 Aug 24 i i   i       i   ii   `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state2olcott
8 Aug 24 i i   i       i   i`- Re: HHH maps its input to the behavior specified by it1Mikko
8 Aug 24 i i   i       i   `- Re: HHH computes the mapping from its input finite sting to the actual behavior specified by this finite string (Which is the results of running the input)1Richard Damon
7 Aug 24 i i   i       `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?4Keith Thompson
4 Aug 24 i i   `- Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?1Fred. Zwarts
3 Aug 24 i `- Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?1Richard Damon
3 Aug 24 `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?96Mikko

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal