• Re: DD specifies non-terminating behavior to HHH --- COMPLETE PROOF

    From Richard Damon@21:1/5 to olcott on Sat Feb 15 20:38:20 2025
    On 2/15/25 8:13 PM, olcott wrote:
    On 2/15/2025 2:49 AM, Mikko wrote:
    On 2025-02-14 12:40:04 +0000, olcott said:

    On 2/14/2025 2:58 AM, Mikko wrote:
    On 2025-02-14 00:07:23 +0000, olcott said:

    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:

    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>> article
    before or when HHH

    That paper and its code are the only thing that I have been
    talking about in this forum for several years.

    Doesn't matter when you don't say that you are talking about
    that paper.

    Anyway, that is irrelevant to the fact that the subject line
    contains
    a false claim.

    It is a truism and not one person on the face of the
    Earth can possibly show otherwise.

    The fact that the claim on subject line is false is not a truism.
    In order to determine the claim is false one needs some knowledge
    that is not obvious.

    When you try to show the steps attempting to show that
    it is false I will point out the error.

    Step 1: Find people who know C.
    Step 2: Show them DD of OP and ask.

    This is the only topic that I will discuss and any

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    int main()
    {
       HHH(DD);
    }

    DD  correctly simulated by HHH cannot possibly terminate normally.

    That claim has already shown to be false. Nothing above shows that
    HHH does not return 0. If it does DD also returns 0.


    *You (and everyone else) is proven wrong by the following*

    918-1156  // All of the lines of termination analyzer HHH
    1355-1370 // DD() through main()

    Which are not part of the above, and thus not part of the input, or what
    you call "DD".

    Sorry, you just don't understand the RULES for a program.


    https://github.com/plolcott/x86utm/blob/master/Halt7.c

    The assembly language source code of every function in Halt7.c https://github.com/plolcott/x86utm/blob/master/Halt7out.txt

    This shows the complete execution trace of
    (a) main
    (b) DD

    It does not show the 171 pages of execution trace of HHH.
    This can be much more easily verified by the provided
    239 lines of source code: 918-1156

    Although the code for HHH is very difficult to understand
    (Only Mike has ever really tried to understand it)
    At least now it is all in one single contiguous block.

    The x86utm operating system functions that it calls
    are found here:
    https://github.com/plolcott/x86utm/blob/master/x86utm.cpp

    https://github.com/plolcott/x86utm/blob/master/include/Read_COFF_Object.h


    Which all just proves that you are lying about what you claim, likely
    because you are too stupid to understand what you mean, but just
    recklessly disregard the truth that has been pointed out to you.

    Pulling in things, while at the same time excluding them is just proof
    that you are just a lying fraud.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Sun Feb 16 11:35:04 2025
    On 2025-02-16 01:13:56 +0000, olcott said:

    On 2/15/2025 2:49 AM, Mikko wrote:
    On 2025-02-14 12:40:04 +0000, olcott said:

    On 2/14/2025 2:58 AM, Mikko wrote:
    On 2025-02-14 00:07:23 +0000, olcott said:

    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:

    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that article >>>>>>>>>> before or when HHH

    That paper and its code are the only thing that I have been talking >>>>>>>>> about in this forum for several years.

    Doesn't matter when you don't say that you are talking about that paper.

    Anyway, that is irrelevant to the fact that the subject line contains >>>>>>>> a false claim.

    It is a truism and not one person on the face of the
    Earth can possibly show otherwise.

    The fact that the claim on subject line is false is not a truism.
    In order to determine the claim is false one needs some knowledge
    that is not obvious.

    When you try to show the steps attempting to show that
    it is false I will point out the error.

    Step 1: Find people who know C.
    Step 2: Show them DD of OP and ask.

    This is the only topic that I will discuss and any

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    int main()
    {
       HHH(DD);
    }

    DD  correctly simulated by HHH cannot possibly terminate normally.

    That claim has already shown to be false. Nothing above shows that
    HHH does not return 0. If it does DD also returns 0.

    *You (and everyone else) is proven wrong by the following*

    Wrong, as shown below.

    918-1156 // All of the lines of termination analyzer HHH

    Not mentioned above.
    Not specified by DD as shown above.

    1355-1370 // DD() through main()

    Not mentioned above. In this discussion DD and main are as shown above.

    https://github.com/plolcott/x86utm/blob/master/Halt7.c

    Not mentioned above and not specified by DD.

    The assembly language source code of every function in Halt7.c https://github.com/plolcott/x86utm/blob/master/Halt7out.txt

    Irrelevant as not specified by DD.

    This shows the complete execution trace of
    (a) main
    (b) DD

    Main calls HHH, not DD. The execution trace of DD is not shown.

    It does not show the 171 pages of execution trace of HHH.
    This can be much more easily verified by the provided
    239 lines of source code: 918-1156

    Although the code for HHH is very difficult to understand
    (Only Mike has ever really tried to understand it)
    At least now it is all in one single contiguous block.

    The x86utm operating system functions that it calls
    are found here:
    https://github.com/plolcott/x86utm/blob/master/x86utm.cpp

    https://github.com/plolcott/x86utm/blob/master/include/Read_COFF_Object.h

    No statement about anyone being proven wrong or contradicting anything
    is inferred. Because of the errors identified above such inrefence would
    be wrong anyway.

    Therefore the claim quoted above is wrong.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Tue Feb 25 18:13:17 2025
    Althogh the subject line has the words "COMPLETE PROOF" there is no
    proof or pointer to proof below.

    On 2025-02-16 01:13:56 +0000, olcott said:

    On 2/15/2025 2:49 AM, Mikko wrote:
    On 2025-02-14 12:40:04 +0000, olcott said:

    On 2/14/2025 2:58 AM, Mikko wrote:
    On 2025-02-14 00:07:23 +0000, olcott said:

    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:

    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that article >>>>>>>>>> before or when HHH

    That paper and its code are the only thing that I have been talking >>>>>>>>> about in this forum for several years.

    Doesn't matter when you don't say that you are talking about that paper.

    Anyway, that is irrelevant to the fact that the subject line contains >>>>>>>> a false claim.

    It is a truism and not one person on the face of the
    Earth can possibly show otherwise.

    The fact that the claim on subject line is false is not a truism.
    In order to determine the claim is false one needs some knowledge
    that is not obvious.

    When you try to show the steps attempting to show that
    it is false I will point out the error.

    Step 1: Find people who know C.
    Step 2: Show them DD of OP and ask.

    This is the only topic that I will discuss and any

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    The above does not specify whether the behaviour is terminating or non-terminating. It only specifies how it depends on HHH: if HHH
    returns 0 the specified behaviour is terminating. If HHH returns
    something else the behaviour is non-terminating. If HHH does not
    terminate the specified behaviour is non-terminating. If HHH
    termintes abnormally the specified behaviour is an abnormal
    termination.

    int main()
    {
       HHH(DD);
    }

    DD  correctly simulated by HHH cannot possibly terminate normally.

    That claim has already shown to be false. Nothing above shows that
    HHH does not return 0. If it does DD also returns 0.

    *You (and everyone else) is proven wrong by the following*

    918-1156 // All of the lines of termination analyzer HHH
    1355-1370 // DD() through main()

    That does not prove (or even claim) about anything quoted above.

    https://github.com/plolcott/x86utm/blob/master/Halt7.c

    From that it is possible to infer that HHH(DD) returns 0, which makes
    DD to terminate, as already observed above.

    The assembly language source code of every function in Halt7.c https://github.com/plolcott/x86utm/blob/master/Halt7out.txt

    This shows the complete execution trace of
    (a) main
    (b) DD

    No, it does not. It shows the excution trace of another main that
    does not call DD.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Tue Feb 25 18:07:08 2025
    Am Tue, 25 Feb 2025 12:01:12 -0600 schrieb olcott:
    On 2/25/2025 10:13 AM, Mikko wrote:
    Althogh the subject line has the words "COMPLETE PROOF" there is no
    proof or pointer to proof below.

    typedef void (*ptr)();
    int HHH(ptr P);
    int DD()
    {
    int Halt_Status = HHH(DD);
    if (Halt_Status)
    HERE: goto HERE;
    return Halt_Status;
    }
    int main()
    {
    HHH(DD);
    }

    The above does specify that DD simulated by HHH cannot possibly
    terminate normally by reaching its own "return" instruction.
    This depends entirely on HHH not aborting *in every invocation*.

    Ignoring the code in main() seemed dishonest.
    --
    Am Sat, 20 Jul 2024 12:35:31 +0000 schrieb WM in sci.math:
    It is not guaranteed that n+1 exists for every n.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue Feb 25 18:41:11 2025
    On 2/25/25 1:01 PM, olcott wrote:
    On 2/25/2025 10:13 AM, Mikko wrote:
    Althogh the subject line has the words "COMPLETE PROOF" there is no
    proof or pointer to proof below.



    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
      int Halt_Status = HHH(DD);
      if (Halt_Status)
        HERE: goto HERE;
      return Halt_Status;
    }

    int main()
    {
      HHH(DD);
    }

    The above does specify that DD simulated by HHH
    cannot possibly terminate normally by reaching its
    own "return" instruction.

    That this may be beyond your technical skill level.
    is less than no rebuttal at all.

    Ignoring the code in main() seemed dishonest.


    Since it isn't part of the problem, why is that?

    Thje question is about DD as a Turing Machine (eqquivalent), if the main scafolding is needed for your equivalence system, it isn't really part
    of the original problem.

    When converting the requirments from Turing Machines to your C Language version, the question being ask of the decider, is would the full
    program defined by the input (and it needs to be a full program) return
    to main when main directly calls it or not?

    The fact that you need to alter-is (and thus LIE) about the problem to
    be about HHH emulating the input, when the problem NEVER stated
    emulation, and especially not by a partial (and thus incorrrect)
    emulation, so you are just showing that you are just a liar.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue Feb 25 23:21:34 2025
    On 2/25/25 9:09 PM, olcott wrote:
    On 2/25/2025 5:41 PM, Richard Damon wrote:
    On 2/25/25 1:25 PM, olcott wrote:
    On 2/25/2025 12:07 PM, joes wrote:
    Am Tue, 25 Feb 2025 12:01:12 -0600 schrieb olcott:
    On 2/25/2025 10:13 AM, Mikko wrote:
    Althogh the subject line has the words "COMPLETE PROOF" there is no >>>>>> proof or pointer to proof below.

    typedef void (*ptr)();
    int HHH(ptr P);
    int DD()
    {
        int Halt_Status = HHH(DD);
        if (Halt_Status)
          HERE: goto HERE;
        return Halt_Status;
    }
    int main()
    {
        HHH(DD);
    }

    The above does specify that DD simulated by HHH cannot possibly
    terminate normally by reaching its own "return" instruction.

    This depends entirely on HHH not aborting *in every invocation*.


    Whether HHH aborts or never aborts DD simulated by
    HHH never terminates normally.

    No, becuawe "DD" is the program as it behaves when run or correctly
    simulated.


    _DD()
    [00002133] 55         push ebp      ; housekeeping
    [00002134] 8bec       mov ebp,esp   ; housekeeping
    [00002136] 51         push ecx      ; make space for local [00002137] 6833210000 push 00002133 ; push DD
    [0000213c] e882f4ffff call 000015c3 ; call HHH(DD)
    [00002141] 83c404     add esp,+04
    [00002144] 8945fc     mov [ebp-04],eax
    [00002147] 837dfc00   cmp dword [ebp-04],+00
    [0000214b] 7402       jz 0000214f
    [0000214d] ebfe       jmp 0000214d
    [0000214f] 8b45fc     mov eax,[ebp-04]
    [00002152] 8be5       mov esp,ebp
    [00002154] 5d         pop ebp
    [00002155] c3         ret
    Size in bytes:(0035) [00002155]

    In other words you are trying to get away with saying
    that the above DD emulated by HHH can somehow jump
    over machine address 0000213c and still be a correct
    emulation.



    That is NOT what I am saying, but that is just your strawman lie.

    Since your HHH doesn't correctly emulate the input, your statement is
    just nonsense.

    What I am saying is that the actual correct emulation of the full input,
    which needs to include the definition of your actual HHH that gives your claimed answer, will reach the final state.

    The fact that you keep on conditioning your "proof" with an impossible
    statment just shows your stupidity.

    And you are the one that claims OTHERS put forward "nonsense"
    statements, when you are the champion of that operation.

    Remember your words about the fate of liar, and try to resolve that with
    your own lies about the actual behavior of HHH. Sorry, but you are due
    for a hot time in the old town some point soon.

    All you are doing is totally proving your utter ignorance and total
    stupidity in what you write.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Wed Feb 26 10:58:52 2025
    On 2025-02-25 18:01:12 +0000, olcott said:

    On 2/25/2025 10:13 AM, Mikko wrote:
    Althogh the subject line has the words "COMPLETE PROOF" there is no
    proof or pointer to proof below.



    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
    int Halt_Status = HHH(DD);
    if (Halt_Status)
    HERE: goto HERE;
    return Halt_Status;
    }

    int main()
    {
    HHH(DD);
    }

    The above does specify that DD simulated by HHH
    cannot possibly terminate normally by reaching its
    own "return" instruction.

    No, it does not. It does not specify whether DD simulated by HHH is
    the DD shown above or something else. It does not specify whether
    HHH returns nor what value it returns if it returns. The DD above
    does specifies neither terminating nor non-terminating status as
    that depends on HHH. Nothing above specifies about HHH anithing other
    than the call interface about HHH. Therefore it is possible to link
    any HHH that has the same call interface to those programs.

    Ignoring the code in main() seemed dishonest.

    Not at all. The subject line mentions DD but not main. Therefore
    the discussion is about what DD specifies, not what main specifies.

    The main does not output anything. It either terminates normally,
    terminates abnormally, or does not terminate at all. Which is does
    depends on HHH, which is not the topic of this discussion.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)