Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.theory > #24043 > unrolled thread

The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ]

Started byolcott <NoOne@NoWhere.com>
First post2020-10-20 11:33 -0500
Last post2020-10-29 14:01 +0100
Articles 20 on this page of 499 — 17 participants

Back to article view | Back to comp.theory


Contents

  The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-20 11:33 -0500
    Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-20 19:11 +0100
      Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-20 13:40 -0500
        Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-20 14:19 -0500
        Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-21 02:57 +0100
          Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-20 22:07 -0500
            Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-21 16:28 +0100
              Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-21 16:52 +0100
              Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-21 11:48 -0500
                Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-21 20:30 +0100
                  Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-21 15:27 -0500
                    Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] André G. Isaak <agisaak@gm.invalid> - 2020-10-21 14:57 -0600
                      Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-21 16:12 -0500
                        Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] André G. Isaak <agisaak@gm.invalid> - 2020-10-21 15:54 -0600
                          Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-21 17:20 -0500
                            Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 00:16 +0100
                              Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] olcott <NoOne@NoWhere.com> - 2020-10-21 18:28 -0500
                                Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 00:55 +0100
                                Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] olcott <NoOne@NoWhere.com> - 2020-10-22 09:20 -0500
                    Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-21 23:10 +0100
                      Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] olcott <NoOne@NoWhere.com> - 2020-10-21 17:55 -0500
                        Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-22 03:38 +0100
                          Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] olcott <NoOne@NoWhere.com> - 2020-10-21 21:54 -0500
                            Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-22 04:38 +0100
                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-21 23:33 -0500
                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 11:05 +0100
                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 09:44 -0500
                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 16:14 +0100
                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-22 08:00 -0400
                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 09:36 -0500
                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 15:57 +0100
                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 10:44 -0500
                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 00:34 +0100
                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 18:55 -0500
                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 03:09 +0100
                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 21:31 -0500
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 04:44 +0100
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 23:13 -0500
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 16:03 +0100
                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 10:40 -0500
                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 00:40 +0100
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-23 17:18 +0100
                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 17:28 +0100
                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:40 -0500
                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 11:38 -0500
                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-22 16:25 +0100
                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 16:45 +0100
                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-22 17:57 +0100
                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 12:26 -0500
                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 21:15 +0100
                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 15:36 -0500
                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 11:38 -0500
                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 09:56 -0700
                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 12:09 -0500
                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 10:27 -0700
                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 12:32 -0500
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 18:33 +0100
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 10:58 -0700
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:19 -0500
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:30 -0500
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 19:34 +0100
                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 20:53 +0100
                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 15:24 -0500
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 13:28 -0700
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 16:25 -0500
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 00:51 +0100
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 19:09 -0500
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 02:50 +0100
                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-22 21:27 -0500
                                                        Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 05:00 +0100
                                                          Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-22 23:31 -0500
                                                            Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 17:19 +0100
                                                            Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 21:22 -0400
                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 20:36 -0500
                                                                Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 22:50 -0400
                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 22:18 -0500
                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 10:00 -0400
                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-24 11:04 -0500
                                                          Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 00:12 -0500
                                                            Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 03:47 -0700
                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 08:57 -0500
                                                                Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 07:34 -0700
                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 10:12 -0500
                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 16:20 +0100
                                                                Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 11:55 -0500
                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 00:52 +0100
                                                                Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 09:59 -0700
                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:20 -0500
                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 21:02 +0100
                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 13:29 -0700
                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 15:56 -0500
                                                                        Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 14:12 -0700
                                                                          Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 16:58 -0500
                                                                            Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 21:35 -0400
                                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 20:45 -0500
                                                                                Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2020-10-23 19:54 -0700
                                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 22:22 -0500
                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 12:46 +0100
                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Andy Walker <anw@cuboid.co.uk> - 2020-10-24 16:43 +0100
                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-24 14:01 -0500
                                                                                        Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Andy Walker <anw@cuboid.co.uk> - 2020-10-24 23:14 +0100
                                                                                          Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-24 17:35 -0500
                                                                                            Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Andy Walker <anw@cuboid.co.uk> - 2020-10-25 16:33 +0000
                                                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-25 12:37 -0500
                                                                                                Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] André G. Isaak <agisaak@gm.invalid> - 2020-10-25 12:10 -0600
                                                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-25 15:27 -0500
                                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-25 15:42 -0500
                                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 23:11 +0000
                                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] André G. Isaak <agisaak@gm.invalid> - 2020-10-26 03:18 -0600
                                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] André G. Isaak <agisaak@gm.invalid> - 2020-10-26 03:21 -0600
                                                                                Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 22:58 -0400
                                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 22:28 -0500
                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2020-10-23 21:03 -0700
                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 23:13 -0500
                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 13:27 -0400
                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-24 14:08 -0500
                                                                                        Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-24 19:54 +0000
                                                                                          Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-24 15:48 -0500
                                                                                            Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-24 21:41 +0000
                                                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 14:47 -0700
                                                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-24 17:20 -0500
                                                                                                Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-26 13:37 +0000
                                                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 11:30 -0500
                                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] André G. Isaak <agisaak@gm.invalid> - 2020-10-26 10:43 -0600
                                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 12:44 -0500
                                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-26 17:38 +0000
                                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 13:13 -0500
                                                                                                        Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-26 19:28 +0000
                                                                                                          Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 14:46 -0500
                                                                                                            Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 15:43 -0500
                                                                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-26 21:07 +0000
                                                                                                                Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 16:27 -0500
                                                                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-27 07:03 +0000
                                                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-27 09:53 -0500
                                                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Mostowski Collapse <janburse@fastmail.fm> - 2020-10-27 21:07 +0100
                                                                                                                Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 16:57 -0500
                                                                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] André G. Isaak <agisaak@gm.invalid> - 2020-10-27 04:53 -0600
                                                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 14:30 +0000
                                                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 07:52 -0700
                                                                                                                        Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-27 10:28 -0500
                                                                                                                        Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 15:30 +0000
                                                                                                                          Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 08:45 -0700
                                                                                                                            Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 16:05 +0000
                                                                                                                            Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-27 11:05 -0500
                                                                                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 09:53 -0700
                                                                                                                                Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-27 13:36 -0500
                                                                                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 12:05 -0700
                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-27 14:44 -0500
                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-27 16:05 -0400
                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-28 03:41 +0000
                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-28 02:57 -0700
                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-28 15:54 +0000
                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] David Kleinecke <dkleinecke@gmail.com> - 2020-10-28 09:25 -0700
                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-28 18:31 -0500
                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-29 00:02 +0000
                                                                                                                                            Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 07:55 -0500
                                                                                                                                              Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Richard Damon <Richard@Damon-Family.org> - 2020-10-29 09:28 -0400
                                                                                                                                                Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 10:49 -0500
                                                                                                                                                  Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Richard Damon <Richard@Damon-Family.org> - 2020-10-29 12:32 -0400
                                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 12:41 -0500
                                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Richard Damon <Richard@Damon-Family.org> - 2020-10-29 16:01 -0400
                                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 15:58 -0500
                                                                                                                                              Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-29 06:28 -0700
                                                                                                                                                Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 10:59 -0500
                                                                                                                                                  Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-29 09:50 -0700
                                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 12:48 -0500
                                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-29 11:51 -0700
                                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 14:09 -0500
                                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-29 13:12 -0700
                                                                                                                                                            Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 16:08 -0500
                                                                                                                                              Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-29 22:51 +0000
                                                                                                                                                Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-29 18:15 -0500
                                                                                                                                                  Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-30 01:05 +0000
                                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-29 20:32 -0500
                                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-30 02:16 +0000
                                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-29 21:36 -0500
                                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-29 21:51 -0500
                                                                                                                                                            Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 03:44 -0700
                                                                                                                                                              Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 06:32 -0500
                                                                                                                                                                Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 06:40 -0500
                                                                                                                                                                  Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-30 22:08 +0000
                                                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 17:21 -0500
                                                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-31 00:46 +0000
                                                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 20:07 -0500
                                                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-31 02:30 +0000
                                                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-31 02:44 +0000
                                                                                                                                                                            Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 21:56 -0500
                                                                                                                                                                              Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-31 16:41 +0000
                                                                                                                                                                                Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Jeff Barnett <jbb@notatt.com> - 2020-10-31 11:16 -0600
                                                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 23:40 -0500
                                                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-31 16:28 +0000
                                                                                                                                                                            Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 12:56 -0500
                                                                                                                                                                              Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-31 20:49 +0000
                                                                                                                                                                                Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 16:07 -0500
                                                                                                                                                                                  Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-31 14:55 -0700
                                                                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 17:09 -0500
                                                                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-31 15:22 -0700
                                                                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 17:30 -0500
                                                                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-31 16:00 -0700
                                                                                                                                                                                            Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 18:13 -0500
                                                                                                                                                                                              Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-11-01 13:56 +0000
                                                                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Alan Mackenzie <acm@muc.de> - 2020-10-31 22:23 +0000
                                                                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 17:37 -0500
                                                                                                                                                                                  Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 19:18 -0400
                                                                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 18:40 -0500
                                                                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 20:12 -0400
                                                                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 21:29 -0400
                                                                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 22:34 -0400
                                                                                                                                                                                            Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 21:38 -0500
                                                                                                                                                                                              Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 08:13 -0500
                                                                                                                                                                                                Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 12:18 -0500
                                                                                                                                                                                                  Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-11-01 12:05 -0600
                                                                                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-11-01 10:43 -0800
                                                                                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-11-01 12:56 -0600
                                                                                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ x86 machine description language ] olcott <NoOne@NoWhere.com> - 2020-11-01 13:32 -0600
                                                                                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 17:37 -0500
                                                                                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-11-01 17:41 -0600
                                                                                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 19:09 -0500
                                                                                                                                                                                                  Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-11-01 12:43 -0600
                                                                                                                                                                                            Re: The key aspects of x86utm are now finally complete [ execution trace described ] olcott <NoOne@NoWhere.com> - 2020-10-31 23:36 -0500
                                                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 00:05 -0500
                                                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-31 16:40 +0000
                                                                                                                                                                Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 05:36 -0700
                                                                                                                                                                  Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 10:32 -0500
                                                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 08:54 -0700
                                                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 11:30 -0500
                                                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 16:22 -0700
                                                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 18:41 -0500
                                                                                                                                                                            Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 16:48 -0700
                                                                                                                                                                              Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 18:50 -0500
                                                                                                                                                                                Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 16:59 -0700
                                                                                                                                                                                  Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 19:07 -0500
                                                                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 17:23 -0700
                                                                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 19:34 -0500
                                                                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-31 02:26 +0000
                                                                                                                                                                                        Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-31 03:05 -0700
                                                                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-31 12:23 +0000
                                                                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 09:22 -0500
                                                                                                                                                          Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-30 14:26 +0000
                                                                                                                                                            Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 10:49 -0500
                                                                                                                                                              Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-31 01:26 +0000
                                                                                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-28 08:31 -0700
                                                                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Jeff Barnett <jbb@notatt.com> - 2020-10-28 10:57 -0600
                                                                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-28 12:05 -0700
                                                                                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-27 13:09 -0400
                                                                                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] André G. Isaak <agisaak@gm.invalid> - 2020-10-27 13:57 -0600
                                                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-27 11:00 -0500
                                                                                                                        Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 16:53 +0000
                                                                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] key definitions provided olcott <NoOne@NoWhere.com> - 2020-10-27 10:20 -0500
                                                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] key definitions provided Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 15:56 +0000
                                                                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] key definitions provided André G. Isaak <agisaak@gm.invalid> - 2020-10-27 12:53 -0600
                                                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 01:25 +0100
                                                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Andy Walker <anw@cuboid.co.uk> - 2020-10-25 18:38 +0000
                                                                                                Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-25 20:49 +0000
                                                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 23:26 +0000
                                                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Andy Walker <anw@cuboid.co.uk> - 2020-10-25 23:57 +0000
                                                                      Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 22:43 +0100
                                                                        Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 17:10 -0500
                                                                          Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 00:27 +0100
                                                                            Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:34 -0500
                                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 01:15 +0100
                                                            Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 16:46 +0100
                                                              Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:36 -0500
                                                                Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 01:05 +0100
                                                                  Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 19:15 -0500
                                                                    Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 01:29 +0100
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-22 23:41 -0400
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 23:02 -0500
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Tim Woodall <news001@woodall.me.uk> - 2020-10-23 07:05 +0000
                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 08:38 -0500
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 11:02 +0100
                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 08:45 -0500
                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 15:56 +0100
                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 10:30 -0500
                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 00:32 +0100
                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:36 -0500
                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 21:52 -0400
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-23 13:03 -0700
                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 15:24 -0500
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 02:29 -0700
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 08:43 -0500
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 15:51 +0100
                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 10:19 -0500
                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-22 23:14 +0100
                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 18:05 -0500
                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 16:55 -0700
                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 19:29 -0500
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 18:06 -0700
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 20:26 -0500
                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-23 23:51 +0100
                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 16:03 -0700
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:14 -0500
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 01:10 +0100
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 00:17 +0100
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:31 -0500
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 16:39 -0700
                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:54 -0500
                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 16:58 -0700
                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 19:13 -0500
                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 17:24 -0700
                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 01:43 +0100
                                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 02:37 -0700
                                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 10:41 -0500
                                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 09:04 -0700
                                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 13:46 -0500
                                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 00:54 +0100
                                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 22:03 +0100
                                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 14:35 -0700
                                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 01:23 +0000
                                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-25 00:45 -0700
                                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 09:35 -0500
                                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-25 07:39 -0700
                                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 10:33 -0500
                                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-25 12:14 -0400
                                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation Key Details] olcott <NoOne@NoWhere.com> - 2020-10-25 13:42 -0500
                                                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation Key Details] Richard Damon <Richard@Damon-Family.org> - 2020-10-25 16:55 -0400
                                                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation Key Details] olcott <NoOne@NoWhere.com> - 2020-10-25 16:07 -0500
                                                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation Key Details] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 23:51 +0000
                                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-25 17:26 +0000
                                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 14:16 -0500
                                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-25 13:55 -0700
                                                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 15:56 -0500
                                                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-25 17:35 -0400
                                                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-25 14:43 -0700
                                                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 16:55 -0500
                                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 14:43 +0000
                                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-25 08:36 -0700
                                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 12:23 -0500
                                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 22:54 +0000
                                                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-25 16:19 -0700
                                                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 18:35 -0500
                                                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 18:40 -0500
                                                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-26 01:17 +0000
                                                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-26 02:49 +0000
                                                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-26 03:56 +0000
                                                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-26 02:37 -0700
                                                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-26 12:10 +0000
                                                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-26 06:45 -0700
                                                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-26 17:24 +0000
                                                                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-26 10:38 -0700
                                                                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-27 00:51 +0000
                                                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 11:16 -0500
                                                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-26 15:41 +0000
                                                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-26 17:28 +0000
                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 19:52 -0500
                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 01:21 +0100
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 01:06 +0100
                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 19:39 -0500
                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 04:27 +0100
                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 22:40 -0500
                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 23:02 -0500
                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 16:58 +0100
                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 13:38 -0500
                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 01:17 +0100
                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:06 -0500
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 00:38 +0100
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:46 -0500
                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 01:03 -0500
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-24 08:04 -0600
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 11:25 -0500
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 15:38 +0100
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 10:36 -0500
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 17:37 +0100
                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 12:49 -0500
                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 19:32 +0100
                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 11:40 -0700
                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 13:42 -0500
                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 20:00 +0100
                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 14:05 -0500
                                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 20:44 +0100
                                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 15:41 -0500
                                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 21:57 +0100
                                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 16:05 -0500
                                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 22:44 +0100
                                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 17:01 -0500
                                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-26 16:11 +0000
                                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 14:12 -0500
                                                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-26 19:38 +0000
                                                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 14:53 -0500
                                                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-26 13:50 -0700
                                                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 16:01 -0500
                                                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-26 14:08 -0700
                                                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-26 14:26 -0700
                                                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 16:35 -0500
                                                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-26 20:59 -0400
                                                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 20:35 -0500
                                                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 02:19 -0700
                                                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 16:31 -0500
                                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 17:08 -0500
                                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 15:16 -0700
                                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 18:30 -0400
                                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 15:47 -0700
                                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 18:08 -0500
                                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 17:45 -0500
                                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-26 16:29 +0000
                                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 13:03 -0500
                                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction olcott <NoOne@NoWhere.com> - 2020-10-26 13:14 -0500
                                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 00:06 +0000
                                                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-26 17:16 -0700
                                                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 00:46 +0000
                                                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 20:11 -0500
                                                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 02:48 +0000
                                                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 22:38 -0500
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 13:36 -0400
                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 14:13 -0500
                                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 16:55 -0400
                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 14:06 -0700
                                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 16:31 -0500
                                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 18:17 -0400
                                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 18:00 -0500
                                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 19:48 -0400
                                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 19:29 -0500
                                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 16:24 -0500
                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 11:52 -0500
                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-22 10:45 -0700
                Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-21 22:42 +0100
                Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Richard Damon <Richard@Damon-Family.org> - 2020-10-21 21:22 -0400
                  Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ] olcott <NoOne@NoWhere.com> - 2020-10-21 21:14 -0500
                    Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ] Richard Damon <Richard@Damon-Family.org> - 2020-10-22 08:12 -0400
                      Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ] olcott <NoOne@NoWhere.com> - 2020-10-22 09:41 -0500
                        Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ] André G. Isaak <agisaak@gm.invalid> - 2020-10-22 13:43 -0600
                          Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ] olcott <NoOne@NoWhere.com> - 2020-10-22 14:54 -0500
                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 15:13 -0500
                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-22 14:34 -0600
                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 16:28 -0500
                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-22 15:34 -0600
                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 16:47 -0500
                      Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ] Andy Walker <anw@cuboid.co.uk> - 2020-10-22 16:20 +0100
          Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Richard Damon <Richard@Damon-Family.org> - 2020-10-21 09:09 -0400
            Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-21 14:36 +0100
        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 12:19 -0500
          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 18:21 +0100
            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 12:27 -0500
              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 18:30 +0100
                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 12:35 -0500
                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 18:43 +0100
                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:08 -0500
                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 19:12 +0100
                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 11:17 -0700
                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:21 -0500
                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 11:30 -0700
                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:35 -0500
                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Jeff Barnett <jbb@notatt.com> - 2020-10-22 11:59 -0600
                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 10:45 -0700
                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:13 -0500
                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 19:17 +0100
                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:24 -0500
          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 19:40 -0500
            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2020-10-22 17:44 -0700
              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 19:49 -0500
                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2020-10-22 17:59 -0700
                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 18:13 -0700
                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 20:15 -0500
                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 00:10 -0400
                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 23:28 -0500
                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 22:22 -0400
                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 21:51 -0500
                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 13:07 +0100
                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 11:40 -0500
                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 02:07 +0000
                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 06:29 -0600
                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 09:10 -0500
                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 08:30 -0600
                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 09:52 -0500
                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 09:04 -0600
                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 10:49 -0500
                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 10:06 -0600
                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 11:48 -0500
                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 11:04 -0600
                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:31 -0500
                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 12:00 -0600
                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 13:12 -0500
                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 12:35 -0600
                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 14:04 -0500
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 15:34 -0600
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 17:05 -0500
                                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 22:32 -0400
                                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 21:55 -0500
                                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 09:50 -0400
                                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 11:14 -0500
                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 11:15 -0700
                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 13:49 -0500
                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-23 17:37 +0100
                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 11:43 -0500
                                Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-23 17:49 +0100
                                  Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:06 -0500
                                    Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-23 18:10 +0100
                                      Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:24 -0500
                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-23 18:35 +0100
                                          Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:46 -0500
                                            Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-23 18:53 +0100
                                              Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 13:06 -0500
    Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 17:54 +0100
      Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-22 11:57 -0500
        Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 18:05 +0100
          Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2020-10-22 12:55 -0600
            Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 19:59 +0100
              Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2020-10-22 19:13 +0000
    Stop crossposting you imbecil spammer (Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ]) Mostowski Collapse <janburse@fastmail.fm> - 2020-10-29 14:01 +0100

Page 20 of 25 — ← Prev page 1 … 18 19 [20] 21 22 … 25  Next page →


#24490 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-26 16:01 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<IaOdnfLQANyOpArCnZ2dnUU7-V3NnZ2d@giganews.com>
In reply to#24489
On 10/26/2020 3:50 PM, Malcolm McLean wrote:
> On Monday, 26 October 2020 at 19:54:05 UTC, olcott wrote:
>> On 10/26/2020 2:38 PM, Mike Terry wrote:
>>> On 26/10/2020 19:12, olcott wrote:
>>>> On 10/26/2020 11:11 AM, Mike Terry wrote:
>>>>> On 24/10/2020 23:01, olcott wrote:
>>> [... snip ...]
>>>>>>
>>>>>> Your trace is based on false assumptions my trace is based on working
>>>>>> code. Although I don't have the halt decider code completed yet because
>>>>>> the x86utm operating system is completed I can see exactly how the halt
>>>>>> deciding code would work.
>>>>>>
>>>>>
>>>>> What are the false assumptions? It is not ok in a discussion to say
>>>>> "you're wrong because you've made a false assumption, but I'm not
>>>>> going to say what that is!".
>>>>>
>>>>> My trace /is/ based on the assumption that Was_Its_Execution_Aborted()
>>>>> detects non-halting behaviour and returns ABORTS to H() and H_Hat().
>>>>> Is that my false assumption?
>>>>>
>>>>> Mike.
>>>>
>>>>
>>>> void H_Hat(u32 M)
>>>> {
>>>> if (Aborted_Because_Non_Halting_Behavior_Detected(M, M))
>>>> MOV_EAX_1 // Execution of M(M) has been aborted
>>>> else
>>>> {
>>>> MOV_EAX_0 // M(M) has halted
>>>> HERE: goto HERE;
>>>> }
>>>> HALT
>>>> }
>>>>
>>>>
>>>> void H(u32 M, u32 N)
>>>> {
>>>> if (Aborted_Because_Non_Halting_Behavior_Detected(M, M))
>>>> MOV_EAX_1 // Execution of M(N) has been aborted
>>>> else
>>>> MOV_EAX_0 // M(N) has halted
>>>> HALT
>>>> }
>>>>
>>>>
>>>> int main()
>>>> {
>>>> u32 M = (u32)H_Hat;
>>>> H(M, M);
>>>> H_Hat(M);
>>>> HALT
>>>> }
>>>>
>>>> In each of the two cases above:
>>>> Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
>>>> Does provide the correct decision for its input.
>>>>
>>>
>>> So what was my false assumption you were referring to?
>>> Mike.
>> This answer may be too difficult to understand without an actual
>> execution trace of fully operational code. I have already explained it
>> again and again and no one has understood.
>>
>> The key summation of all of these execution trace answers is that
>> bool Aborted_Because_Non_Halting_Behavior_Detected(M, M)
>> always decides its input correctly and cannot be shown otherwise.
>>
> So the code is this
> 
> int eax = 1;
> 
> bool Aborted_Because_Non_Halting_Behaviour_Detected(u32 *program, U32 *input)
> {
>      if (program == H_Hat && input == H_Hat)
>      {
>          eax = 0;
>          return true;
>      }
>      /* rest of logic unimportant */
> }
> 
> void H_Hat(u32 *input)
> {
>      if (Aborted_Because_Non_Halting_Behaviour_Detected(input, input))
>          return;
>      else
>          while(1);
> }
> 
> int main(void)
> {
>      Aborted_Because_Non_Halting_Beahviour_Detected(H_Hat, H_hat);
>      if (eax == 0)
>          printf("aborted\n");
>      else
>         printf("Not aborted\n");
>      eax  = 1;
>      H_Hat(H_Hat);
>      if (eax == 0)
>          printf("aborted\n");
>     else
>         printf("Not aborted\n");
> }
> 


You have only shown how to encode this function incorrectly:
bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)

You have not shown any input where the following design necessarily gets 
the wrong answer:

The redefined halt decider UTM executes its subordinate UTM one state 
transition at a time until it detects non-halting behavior or its 
subordinate UTM has terminated normally.

If the halt decider UTM detects non-halting behavior of its subordinate 
UTM it simply stops executing the subordinate and transitions to its own 
final state of ABORTED_NON_TERMINATING_BEHAVIOR.

If the subordinate UTM terminates normally the halt decider UTM 
transitions to its own final state of SUBORDINATE_HAS_TERMINATED.


-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24492 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-26 14:08 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<b78b2845-70a8-4ee0-8cf1-81d3ecbee3bdn@googlegroups.com>
In reply to#24490
On Monday, 26 October 2020 at 21:01:15 UTC, olcott wrote:
> On 10/26/2020 3:50 PM, Malcolm McLean wrote: 
> > On Monday, 26 October 2020 at 19:54:05 UTC, olcott wrote: 
> >> On 10/26/2020 2:38 PM, Mike Terry wrote: 
> >>> On 26/10/2020 19:12, olcott wrote: 
> >>>> On 10/26/2020 11:11 AM, Mike Terry wrote: 
> >>>>> On 24/10/2020 23:01, olcott wrote: 
> >>> [... snip ...] 
> >>>>>> 
> >>>>>> Your trace is based on false assumptions my trace is based on working 
> >>>>>> code. Although I don't have the halt decider code completed yet because 
> >>>>>> the x86utm operating system is completed I can see exactly how the halt 
> >>>>>> deciding code would work. 
> >>>>>> 
> >>>>> 
> >>>>> What are the false assumptions? It is not ok in a discussion to say 
> >>>>> "you're wrong because you've made a false assumption, but I'm not 
> >>>>> going to say what that is!". 
> >>>>> 
> >>>>> My trace /is/ based on the assumption that Was_Its_Execution_Aborted() 
> >>>>> detects non-halting behaviour and returns ABORTS to H() and H_Hat(). 
> >>>>> Is that my false assumption? 
> >>>>> 
> >>>>> Mike. 
> >>>> 
> >>>> 
> >>>> void H_Hat(u32 M) 
> >>>> { 
> >>>> if (Aborted_Because_Non_Halting_Behavior_Detected(M, M)) 
> >>>> MOV_EAX_1 // Execution of M(M) has been aborted 
> >>>> else 
> >>>> { 
> >>>> MOV_EAX_0 // M(M) has halted 
> >>>> HERE: goto HERE; 
> >>>> } 
> >>>> HALT 
> >>>> } 
> >>>> 
> >>>> 
> >>>> void H(u32 M, u32 N) 
> >>>> { 
> >>>> if (Aborted_Because_Non_Halting_Behavior_Detected(M, M)) 
> >>>> MOV_EAX_1 // Execution of M(N) has been aborted 
> >>>> else 
> >>>> MOV_EAX_0 // M(N) has halted 
> >>>> HALT 
> >>>> } 
> >>>> 
> >>>> 
> >>>> int main() 
> >>>> { 
> >>>> u32 M = (u32)H_Hat; 
> >>>> H(M, M); 
> >>>> H_Hat(M); 
> >>>> HALT 
> >>>> } 
> >>>> 
> >>>> In each of the two cases above: 
> >>>> Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) 
> >>>> Does provide the correct decision for its input. 
> >>>> 
> >>> 
> >>> So what was my false assumption you were referring to? 
> >>> Mike. 
> >> This answer may be too difficult to understand without an actual 
> >> execution trace of fully operational code. I have already explained it 
> >> again and again and no one has understood. 
> >> 
> >> The key summation of all of these execution trace answers is that 
> >> bool Aborted_Because_Non_Halting_Behavior_Detected(M, M) 
> >> always decides its input correctly and cannot be shown otherwise. 
> >> 
> > So the code is this 
> > 
> > int eax = 1; 
> > 
> > bool Aborted_Because_Non_Halting_Behaviour_Detected(u32 *program, U32 *input) 
> > { 
> > if (program == H_Hat && input == H_Hat) 
> > { 
> > eax = 0; 
> > return true; 
> > } 
> > /* rest of logic unimportant */ 
> > } 
> > 
> > void H_Hat(u32 *input) 
> > { 
> > if (Aborted_Because_Non_Halting_Behaviour_Detected(input, input)) 
> > return; 
> > else 
> > while(1); 
> > } 
> > 
> > int main(void) 
> > { 
> > Aborted_Because_Non_Halting_Beahviour_Detected(H_Hat, H_hat); 
> > if (eax == 0) 
> > printf("aborted\n"); 
> > else 
> > printf("Not aborted\n"); 
> > eax = 1; 
> > H_Hat(H_Hat); 
> > if (eax == 0) 
> > printf("aborted\n"); 
> > else 
> > printf("Not aborted\n"); 
> > } 
> >
> You have only shown how to encode this function incorrectly:
>
It's a function. So it always behaves the same way when called with the
same arguments. Therefore it can be replaced with this stub.
That's useless for a real halt decider, but we only need one which works
on one set of inputs - H_Hat, H_Hat.
>
> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
> You have not shown any input where the following design necessarily gets 
> the wrong answer:
>
I'm not disagreeing with you. I'm trying to clarify what you say.

[toc] | [prev] | [next] | [standalone]


#24493 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2020-10-26 14:26 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<87d014vfto.fsf@nosuchdomain.example.com>
In reply to#24492
Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:
[...]
>> You have only shown how to encode this function incorrectly:
>>
> It's a function. So it always behaves the same way when called with the
> same arguments.

That is not generally true of C functions, whose behavior can depend on
data defined outside the function.

Malcolm has his own meaning for the word "function", which is
inconsistent with the C meaning of the word.

Malcolm, please make it clear when you're using your own definition of
"function", and what that definition is -- especially when C code is
begin discussed.  Readers of comp.theory might not be familiar with the
way you use words.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips Healthcare
void Void(void) { Void(); } /* The recursive call of the void */

[toc] | [prev] | [next] | [standalone]


#24496 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-26 16:35 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<ROednbivfvyY3ArCnZ2dnUU7-VnNnZ2d@giganews.com>
In reply to#24493
On 10/26/2020 4:26 PM, Keith Thompson wrote:
> Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:
> [...]
>>> You have only shown how to encode this function incorrectly:
>>>
>> It's a function. So it always behaves the same way when called with the
>> same arguments.
> 
> That is not generally true of C functions, whose behavior can depend on
> data defined outside the function.
> 
> Malcolm has his own meaning for the word "function", which is
> inconsistent with the C meaning of the word.
> 
> Malcolm, please make it clear when you're using your own definition of
> "function", and what that definition is -- especially when C code is
> begin discussed.  Readers of comp.theory might not be familiar with the
> way you use words.
> 

Upon a suggestion of another poster we can hypothetically assume that 
the x86utm language does not provide any user code access to global 
data. This change would seem to make what Malcolm said true.

-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24503 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromRichard Damon <Richard@Damon-Family.org>
Date2020-10-26 20:59 -0400
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<rhKlH.139716$1a1.119007@fx18.iad>
In reply to#24493
On 10/26/20 5:26 PM, Keith Thompson wrote:
> Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:
> [...]
>>> You have only shown how to encode this function incorrectly:
>>>
>> It's a function. So it always behaves the same way when called with the
>> same arguments.
> 
> That is not generally true of C functions, whose behavior can depend on
> data defined outside the function.
> 
> Malcolm has his own meaning for the word "function", which is
> inconsistent with the C meaning of the word.
> 
> Malcolm, please make it clear when you're using your own definition of
> "function", and what that definition is -- especially when C code is
> begin discussed.  Readers of comp.theory might not be familiar with the
> way you use words.
> 

BUT, a Turing Machine will always give the same output for the same
machine and same input.

A C function can only give differing outputs if there is state hidden
elsewhere, for a Turing machine, that state would be explicit in the
machine or input.

[toc] | [prev] | [next] | [standalone]


#24506 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-26 20:35 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<6-SdnRjlAoL45ArCnZ2dnUU7-cudnZ2d@giganews.com>
In reply to#24503
On 10/26/2020 7:59 PM, Richard Damon wrote:
> On 10/26/20 5:26 PM, Keith Thompson wrote:
>> Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:
>> [...]
>>>> You have only shown how to encode this function incorrectly:
>>>>
>>> It's a function. So it always behaves the same way when called with the
>>> same arguments.
>>
>> That is not generally true of C functions, whose behavior can depend on
>> data defined outside the function.
>>
>> Malcolm has his own meaning for the word "function", which is
>> inconsistent with the C meaning of the word.
>>
>> Malcolm, please make it clear when you're using your own definition of
>> "function", and what that definition is -- especially when C code is
>> begin discussed.  Readers of comp.theory might not be familiar with the
>> way you use words.
>>
> 
> BUT, a Turing Machine will always give the same output for the same
> machine and same input.
> 
> A C function can only give differing outputs if there is state hidden
> elsewhere, for a Turing machine, that state would be explicit in the
> machine or input.
> 

Good answer, better than mine.

-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24515 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-27 02:19 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<4ac861ce-5780-409e-adef-77d9fc735964n@googlegroups.com>
In reply to#24503
On Tuesday, 27 October 2020 at 00:59:07 UTC, Richard Damon wrote:
> On 10/26/20 5:26 PM, Keith Thompson wrote: 
> > Malcolm McLean <malcolm.ar...@gmail.com> writes: 
> > [...] 
> >>> You have only shown how to encode this function incorrectly: 
> >>> 
> >> It's a function. So it always behaves the same way when called with the 
> >> same arguments. 
> > 
> > That is not generally true of C functions, whose behavior can depend on 
> > data defined outside the function. 
> > 
> > Malcolm has his own meaning for the word "function", which is 
> > inconsistent with the C meaning of the word. 
> > 
> > Malcolm, please make it clear when you're using your own definition of 
> > "function", and what that definition is -- especially when C code is 
> > begin discussed. Readers of comp.theory might not be familiar with the 
> > way you use words. 
> >
> BUT, a Turing Machine will always give the same output for the same 
> machine and same input. 
> 
> A C function can only give differing outputs if there is state hidden 
> elsewhere, for a Turing machine, that state would be explicit in the 
> machine or input.
>
I made the mistake of using the term "function" in its normal rather
than C language sense on comp.lang.c. That created an inordinate 
amount of fuss.
A "function" is a mapping of an input set to an output set such that 
for each member of the input set, there is one an only one member 
of the output set. However members of the output set may be chosen
multiple times.
In computer science, the sets are usually restricted to sets of bits,
and, loosely, we also refer to the code that peforms the mapping
as the "function".

[toc] | [prev] | [next] | [standalone]


#24495 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-26 16:31 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<4PCdnRWFxu2t3QrCnZ2dnUU7-dXNnZ2d@giganews.com>
In reply to#24492
On 10/26/2020 4:08 PM, Malcolm McLean wrote:
> On Monday, 26 October 2020 at 21:01:15 UTC, olcott wrote:
>> On 10/26/2020 3:50 PM, Malcolm McLean wrote:
>>> On Monday, 26 October 2020 at 19:54:05 UTC, olcott wrote:
>>>> On 10/26/2020 2:38 PM, Mike Terry wrote:
>>>>> On 26/10/2020 19:12, olcott wrote:
>>>>>> On 10/26/2020 11:11 AM, Mike Terry wrote:
>>>>>>> On 24/10/2020 23:01, olcott wrote:
>>>>> [... snip ...]
>>>>>>>>
>>>>>>>> Your trace is based on false assumptions my trace is based on working
>>>>>>>> code. Although I don't have the halt decider code completed yet because
>>>>>>>> the x86utm operating system is completed I can see exactly how the halt
>>>>>>>> deciding code would work.
>>>>>>>>
>>>>>>>
>>>>>>> What are the false assumptions? It is not ok in a discussion to say
>>>>>>> "you're wrong because you've made a false assumption, but I'm not
>>>>>>> going to say what that is!".
>>>>>>>
>>>>>>> My trace /is/ based on the assumption that Was_Its_Execution_Aborted()
>>>>>>> detects non-halting behaviour and returns ABORTS to H() and H_Hat().
>>>>>>> Is that my false assumption?
>>>>>>>
>>>>>>> Mike.
>>>>>>
>>>>>>
>>>>>> void H_Hat(u32 M)
>>>>>> {
>>>>>> if (Aborted_Because_Non_Halting_Behavior_Detected(M, M))
>>>>>> MOV_EAX_1 // Execution of M(M) has been aborted
>>>>>> else
>>>>>> {
>>>>>> MOV_EAX_0 // M(M) has halted
>>>>>> HERE: goto HERE;
>>>>>> }
>>>>>> HALT
>>>>>> }
>>>>>>
>>>>>>
>>>>>> void H(u32 M, u32 N)
>>>>>> {
>>>>>> if (Aborted_Because_Non_Halting_Behavior_Detected(M, M))
>>>>>> MOV_EAX_1 // Execution of M(N) has been aborted
>>>>>> else
>>>>>> MOV_EAX_0 // M(N) has halted
>>>>>> HALT
>>>>>> }
>>>>>>
>>>>>>
>>>>>> int main()
>>>>>> {
>>>>>> u32 M = (u32)H_Hat;
>>>>>> H(M, M);
>>>>>> H_Hat(M);
>>>>>> HALT
>>>>>> }
>>>>>>
>>>>>> In each of the two cases above:
>>>>>> Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
>>>>>> Does provide the correct decision for its input.
>>>>>>
>>>>>
>>>>> So what was my false assumption you were referring to?
>>>>> Mike.
>>>> This answer may be too difficult to understand without an actual
>>>> execution trace of fully operational code. I have already explained it
>>>> again and again and no one has understood.
>>>>
>>>> The key summation of all of these execution trace answers is that
>>>> bool Aborted_Because_Non_Halting_Behavior_Detected(M, M)
>>>> always decides its input correctly and cannot be shown otherwise.
>>>>
>>> So the code is this
>>>
>>> int eax = 1;
>>>
>>> bool Aborted_Because_Non_Halting_Behaviour_Detected(u32 *program, U32 *input)
>>> {
>>> if (program == H_Hat && input == H_Hat)
>>> {
>>> eax = 0;
>>> return true;
>>> }
>>> /* rest of logic unimportant */
>>> }
>>>
>>> void H_Hat(u32 *input)
>>> {
>>> if (Aborted_Because_Non_Halting_Behaviour_Detected(input, input))
>>> return;
>>> else
>>> while(1);
>>> }
>>>
>>> int main(void)
>>> {
>>> Aborted_Because_Non_Halting_Beahviour_Detected(H_Hat, H_hat);
>>> if (eax == 0)
>>> printf("aborted\n");
>>> else
>>> printf("Not aborted\n");
>>> eax = 1;
>>> H_Hat(H_Hat);
>>> if (eax == 0)
>>> printf("aborted\n");
>>> else
>>> printf("Not aborted\n");
>>> }
>>>
>> You have only shown how to encode this function incorrectly:
>>
> It's a function. So it always behaves the same way when called with the
> same arguments. Therefore it can be replaced with this stub.
> That's useless for a real halt decider, but we only need one which works
> on one set of inputs - H_Hat, H_Hat.
>>
>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
>> You have not shown any input where the following design necessarily gets
>> the wrong answer:
>>
> I'm not disagreeing with you. I'm trying to clarify what you say.
> 

Great!

Please try and find a counter-example where a halt decider defined as 
follows would necessarily fail, or agree that the conventional halting 
problem proof trick no longer works on such a halt decider:

The redefined halt decider UTM executes its subordinate UTM one state 
transition at a time until it detects non-halting behavior or its 
subordinate UTM has terminated normally.

If the halt decider UTM detects non-halting behavior of its subordinate 
UTM it simply stops executing the subordinate and transitions to its own 
final state of ABORTED_NON_TERMINATING_BEHAVIOR.

If the subordinate UTM terminates normally the halt decider UTM 
transitions to its own final state of SUBORDINATE_HAS_TERMINATED.




-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24358 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-24 17:08 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<XvqdnaMd-fRJOAnCnZ2dnUU7-Q_NnZ2d@giganews.com>
In reply to#24344
On 10/24/2020 3:57 PM, Mike Terry wrote:
> On 24/10/2020 21:41, olcott wrote:
>> On 10/24/2020 2:44 PM, Mike Terry wrote:
>>> On 24/10/2020 20:05, olcott wrote:
>>>> On 10/24/2020 2:00 PM, Mike Terry wrote:
>>>>> On 24/10/2020 19:42, olcott wrote:
>>>>>> On 10/24/2020 1:32 PM, Mike Terry wrote:
>>>>>>> On 24/10/2020 18:49, olcott wrote:
>>>>>>>> On 10/24/2020 11:37 AM, Mike Terry wrote:
>>>>>>>>> On 24/10/2020 16:36, olcott wrote:
>>>>>>>>>> On 10/24/2020 9:38 AM, Mike Terry wrote:
>>>>>>>>>>> On 24/10/2020 07:03, olcott wrote:
>>>>>>>>>>>> On 10/23/2020 5:51 PM, Mike Terry wrote:
>>>>>>>>>>>>> On 23/10/2020 00:05, olcott wrote:
>>>>>>>>>>>>>> On 10/22/2020 5:14 PM, Mike Terry wrote:
>>>>>>>>>>>>>>> On 22/10/2020 17:38, olcott wrote:
>>>>>>>>>>>>>>>> On 10/22/2020 10:25 AM, Mike Terry wrote:
>>>>>>>>>>>>>>>>> On 22/10/2020 15:36, olcott wrote:
>>>>>>>>>>>>>>>>>> On 10/22/2020 7:00 AM, Richard Damon wrote:
>>>>>>>>>>>>>>>>>>> On 10/22/20 12:33 AM, olcott wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> The difference is that it is no longer possible for
>>>>>>>>>>>>>>>>>>>> H_Hat()
>>>>>>>>>>>>>>>>>>>> to do
>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>> opposite of what H() decides. This transforms an
>>>>>>>>>>>>>>>>>>>> undecidable
>>>>>>>>>>>>>>>>>>>> problem
>>>>>>>>>>>>>>>>>>>> into a decidable problem.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> If H_Hat no longer does what the proof defined, then 
>>>>>>>>>>>>>>>>>>> your
>>>>>>>>>>>>>>>>>>> demonstration
>>>>>>>>>>>>>>>>>>> is no longer applicable to the proof.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> If the halt decider is to report whether or not its input
>>>>>>>>>>>>>>>>>> halts
>>>>>>>>>>>>>>>>>> another
>>>>>>>>>>>>>>>>>> program can be constructed on the the basis of this halt
>>>>>>>>>>>>>>>>>> decider
>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>> does the opposite of whatever the halt decider decides.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> This is how H() and H_Hat() are defined in the Linz 
>>>>>>>>>>>>>>>>>> proof.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> If the halt decider is to report whether or not it
>>>>>>>>>>>>>>>>>> aborted its
>>>>>>>>>>>>>>>>>> input
>>>>>>>>>>>>>>>>>> program because its input program would otherwise cause
>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>> halt
>>>>>>>>>>>>>>>>>> decider
>>>>>>>>>>>>>>>>>> to get stuck in infinite execution then this other 
>>>>>>>>>>>>>>>>>> program
>>>>>>>>>>>>>>>>>> can no
>>>>>>>>>>>>>>>>>> longer
>>>>>>>>>>>>>>>>>> fool its halt decider and do the opposite of whatever it
>>>>>>>>>>>>>>>>>> decides.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> If H() aborts the execution of H_Hat() then H_Hat() 
>>>>>>>>>>>>>>>>>> cannot
>>>>>>>>>>>>>>>>>> continue to
>>>>>>>>>>>>>>>>>> execute because H() has complete control over H_Hat.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> The end result of this slight change is that the halting
>>>>>>>>>>>>>>>>>> problem
>>>>>>>>>>>>>>>>>> can no
>>>>>>>>>>>>>>>>>> longer be shown to be undecidable.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> It is suspicious that in none of this have you ever stated
>>>>>>>>>>>>>>>>> what is
>>>>>>>>>>>>>>>>> actually wrong in the Linz proof.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> When the halting problem is defined as:
>>>>>>>>>>>>>>>> bool Does_It_Halt(u32 P, u32 I)
>>>>>>>>>>>>>>>> another program can be constructed on the basis of
>>>>>>>>>>>>>>>> Does_It_Halt()
>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>> does the opposite of whatever Does_It_Halt() decides.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Yes, regardless of the internal details of Does_It_Halt().
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> When the halting problem is defined as:
>>>>>>>>>>>>>>>> bool Was_Its_Execution_Aborted(u32 P, u32 I)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> another program CANNOT be constructed on the basis of
>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() that does the opposite of
>>>>>>>>>>>>>>>> whatever
>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() decides.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Sure, if you interpret your question literally as asking
>>>>>>>>>>>>>>> whether P
>>>>>>>>>>>>>>> would actually be aborted if it executes under the UTM 
>>>>>>>>>>>>>>> within
>>>>>>>>>>>>>>> Was_Its_Execution_Aborted()!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> However, another program CAN be constructed on the basis of
>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() that:
>>>>>>>>>>>>>>> -   halts if Was_Its_Execution_Aborted() decides "aborted"
>>>>>>>>>>>>>>> -   loops if Was_Its_Execution_Aborted() decides "halted"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> (right?)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Wrong.
>>>>>>>>>>>>>
>>>>>>>>>>>>> No, right.  To avoid a silly pantomine argument, here is an
>>>>>>>>>>>>> example of
>>>>>>>>>>>>> such a function:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> int H_Hat(u32 M)
>>>>>>>>>>>>> {
>>>>>>>>>>>>>     if (Was_Its_Execution_Aborted(M, M))
>>>>>>>>>>>>>     {
>>>>>>>>>>>>>       // Was_Its_Execution_Aborted says that M(M) was aborted
>>>>>>>>>>>>>       HALT;       // so we halt
>>>>>>>>>>>>>     }
>>>>>>>>>>>>>     else
>>>>>>>>>>>>>     {
>>>>>>>>>>>>>       // Was_Its_Execution_Aborted says that M(M) halted
>>>>>>>>>>>>>       HERE: goto HERE;   // so we loop
>>>>>>>>>>>>>     }
>>>>>>>>>>>>> }
>>>>>>>>>>>>>
>>>>>>>>>>>>> and for completeness, here is the function being invoked from
>>>>>>>>>>>>> main():
>>>>>>>>>>>>>
>>>>>>>>>>>>> int main()
>>>>>>>>>>>>> {
>>>>>>>>>>>>>     u32 M = (u32)H_Hat;
>>>>>>>>>>>>>
>>>>>>>>>>>>>     H_Hat(M);       // run H_Hat with input H_Hat
>>>>>>>>>>>>>     HALT;
>>>>>>>>>>>>> }
>>>>>>>>>>>>>
>>>>>>>>>>>>> You see, H_Hat /is/ constructed so that if
>>>>>>>>>>>>> Was_Its_Execution_Aborted(M, M) returns "aborted" (nonzero),
>>>>>>>>>>>>> H_Hat
>>>>>>>>>>>>> will halt, and if Was_Its_Execution_Aborted(M, M) returns
>>>>>>>>>>>>> "halted"
>>>>>>>>>>>>> (zero), H_Hat will loop.  Just like I said.  Thre is no subtle
>>>>>>>>>>>>> philosophical point here, just beginner knowledge of the C
>>>>>>>>>>>>> programming
>>>>>>>>>>>>> language.
>>>>>>>>>>>>>
>>>>>>>>>>>>> (To save you making a silly response, yes IF we were to run 
>>>>>>>>>>>>> the
>>>>>>>>>>>>> program under a debugger or emulator of some kind, and we
>>>>>>>>>>>>> aborted the
>>>>>>>>>>>>> run at the "if (Abort)" statement or earlier, then of 
>>>>>>>>>>>>> course we
>>>>>>>>>>>>> would
>>>>>>>>>>>>> not get to see what it actually does next.  (Duh.)  That's
>>>>>>>>>>>>> irrelevent
>>>>>>>>>>>>> because regardless of this, H_Hat as constructed meets the
>>>>>>>>>>>>> conditions
>>>>>>>>>>>>> just as I described.)
>>>>>>>>>>>>>
>>>>>>>>>>>>>  > There is no way to make the revised halting question
>>>>>>>>>>>>> contradictory.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> DebugTrace() either reports that it has aborted the execution
>>>>>>>>>>>>>> of its
>>>>>>>>>>>>>> input or it reports that its input has not been aborted after
>>>>>>>>>>>>>> its
>>>>>>>>>>>>>> input
>>>>>>>>>>>>>> has terminated.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>  > [A quick observation: you've flipped to talking about
>>>>>>>>>>>>> DebugTrace()
>>>>>>>>>>>>> rather than Was_Its_Execution_Aborted() which we were
>>>>>>>>>>>>> discussing.
>>>>>>>>>>>>> I'll just take it they're the same thing, and continue saying
>>>>>>>>>>>>> Was_Its_Execution_Aborted().]
>>>>>>>>>>>>
>>>>>>>>>>>> OK good. I like that. Make the function say what it really
>>>>>>>>>>>> means.
>>>>>>>>>>>> That is good software engineering.
>>>>>>>>>>>>
>>>>>>>>>>>>> I never said otherwise.
>>>>>>>>>>>>>
>>>>>>>>>>>>> BUT bear in mind that H (as opposed to
>>>>>>>>>>>>> Was_Its_Execution_Aborted())
>>>>>>>>>>>>> plays the role in all this of a Linz *Halt Decider*, and so is
>>>>>>>>>>>>> required to deliver its HD decision *HALT* or *NOT_HALT*.
>>>>>>>>>>>>
>>>>>>>>>>>> No, not at all. Not in the least little bit.
>>>>>>>>>>>> This takes my solution of removing the pathological
>>>>>>>>>>>> self-reference
>>>>>>>>>>>> from
>>>>>>>>>>>> the halting decision and tosses this solution in the trash.
>>>>>>>>>>>
>>>>>>>>>>> Maybe, and that would be the right thing to do if your
>>>>>>>>>>> solution is
>>>>>>>>>>> wrong.  In any case, if you can't refute the Linz proof without
>>>>>>>>>>> changing the meaning of "Halt Decider", then your solution is
>>>>>>>>>>> wrong.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I am refuting that the Linz proof proves that the halting
>>>>>>>>>> problem is
>>>>>>>>>> undecidable by finding another way to define the halt decider 
>>>>>>>>>> that
>>>>>>>>>> cannot be contradicted.
>>>>>>>>>
>>>>>>>>> The Linz halt decider corresponds to the correct (HP) definition
>>>>>>>>> of a
>>>>>>>>> halt decider.  If you change this definition you are not
>>>>>>>>> discussing HP.
>>>>>>>>
>>>>>>>> As long as a halt decider cannot be shown to make this decision
>>>>>>>> incorrectly for any of its inputs then the halting problem 
>>>>>>>> cannot be
>>>>>>>> shown to be undecidable:
>>>>>>>>
>>>>>>>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
>>>>>>>
>>>>>>> The Linz proof shows HP to be undecidable.  Your refuting code
>>>>>>> conforms with the Linz conclusion, and does not refute anything.
>>>>>>
>>>>>> Unless you can concretely show how this function would get the wrong
>>>>>> answer all of your rebuttal is ultimately totally vacuous:
>>>>>>
>>>>>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
>>>>>>
>>>>>
>>>>> In your code, the function answers "non halting behaviour detected"
>>>>> for input which actually halts, and so by any reasonable definition of
>>>>> the words, it has decided incorrectly.
>>>>
>>>> Bullshit. The actual question that it always correctly answers is:
>>>> Does the input have to be aborted to prevent infinite execution?
>>>
>>> I provided the traces which back up what I said, so it's not bullshit.
>>> You have snipped them because you don't want to look stupid, so I'm
>>> going to restore them:
>>>
>>> H_Hat machine trace
>>> -------------------
>>>
>>> H_Hat starts (main() calls H_Hat(H_Hat))
>>>     H_Hat calls Was_Its_Execution_Aborted(H_Hat,H_Hat)
>>>       Was_Its_Execution_Aborted emulates H_Hat(H_Hat)
>>>       Was_Its_Execution_Aborted decides the emulated program ..
>>>                  .. will never terminate if not aborted
>>>       Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>>     H_Hat *halts*
>>>
>>> OK, so the H_Hat calculation halts...
>>
>> In this case we have an outer instance of H_Hat() an inner instance of
>> H_Hat(). The outer instance of H_Hat() is executed in the master UTM
>> process context of x86utm.
>>
>> This outer instance of H_Hat() invokes
>> Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) which
>> creates the inner instance of H_Hat() in its own process context and
>> executes it. It then returns true to the outer instance of H_Hat() after
>> aborting the inner instance.
> 
> ..*and then terminates*
> 
> The calculation H_Hat(H_Hat) halts.  So if 
> Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) says there 
> was "non-halting behaviour" it was wrong.
> 
> No point in saying this over and over....
> 
> 
>>
>>> H machine trace
>>>
>>> ---------------
>>> H starts (main() calls H(H_Hat,H_Hat))
>>>     H calls Was_Its_Execution_Aborted(H_Hat,H_Hat)
>>>       Was_Its_Execution_Aborted emulates H_Hat(H_Hat)
>>>       Was_Its_Execution_Aborted decides the emulated program ..
>>>                  .. will never terminate if not aborted
>>>       Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>>     H halts, with EAX=0 [= *NOT_HALT* decision]
>>>
>>
>> In this case we have an instance of H() and an instance of H_Hat(). The
>>  instance of H() is executed in the master UTM process context of x86utm.
>>
>> H() invokes Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
>> which creates the instance of H_Hat() and executes it. It then returns
>> true to H() after aborting the instance of _H_Hat().
> 
> Again, returning true to H is supposed to say it detected non-halting 
> behaviour, but the calculation it is examining actually halts.
> 
> There, I said it again! :)  (last time, really...)
Apparently this whole inner invocation of H_Hat() and outer invocation 
of H_Hat() is against your religion. None-the-less an actual execution 
trace would show that the outer invocation does abort the inner 
invocation thus allowing the outer invocation to terminate normally.



-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24360 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-24 15:16 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<61fe65be-5e7a-4f3c-b622-03f74b8c9595n@googlegroups.com>
In reply to#24358
On Saturday, 24 October 2020 at 23:08:28 UTC+1, olcott wrote:
> On 10/24/2020 3:57 PM, Mike Terry wrote: 
> 
> > 
> > There, I said it again! :) (last time, really...)
> Apparently this whole inner invocation of H_Hat() and outer invocation 
> of H_Hat() is against your religion. None-the-less an actual execution 
> trace would show that the outer invocation does abort the inner 
> invocation thus allowing the outer invocation to terminate normally.
> 
The outer invocation H_Hat is the function we are interested in. If it
terminates normally, that's another way of saying it halts. So H() must
return "not aborted".
have you been following my posts? The way round this problem is to 
say the H aborts itself. i.e. it smashes the machine (abortion is equivalent
to taking a sledgehammed to the machine). Now H_Hat doesn't halt.

[toc] | [prev] | [next] | [standalone]


#24363 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromRichard Damon <Richard@Damon-Family.org>
Date2020-10-24 18:30 -0400
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<SV1lH.239578$d95.66004@fx06.iad>
In reply to#24360
On 10/24/20 6:16 PM, Malcolm McLean wrote:
> On Saturday, 24 October 2020 at 23:08:28 UTC+1, olcott wrote:
>> On 10/24/2020 3:57 PM, Mike Terry wrote: 
>>
>>>
>>> There, I said it again! :) (last time, really...)
>> Apparently this whole inner invocation of H_Hat() and outer invocation 
>> of H_Hat() is against your religion. None-the-less an actual execution 
>> trace would show that the outer invocation does abort the inner 
>> invocation thus allowing the outer invocation to terminate normally.
>>
> The outer invocation H_Hat is the function we are interested in. If it
> terminates normally, that's another way of saying it halts. So H() must
> return "not aborted".
> have you been following my posts? The way round this problem is to 
> say the H aborts itself. i.e. it smashes the machine (abortion is equivalent
> to taking a sledgehammed to the machine). Now H_Hat doesn't halt.
> 

Except that then H isn't the Halt decider of the theory. By definition,
H needs to be a Turing Machine that starts at a state, traditionally
named q0, and eventually, and in finite time, in end up in one of two
terminal states, traditionally named something like qhalt, and qnonhalt.
If it doesn't end up, in finite time, in one of those two states, it has
failed to meet its requirements.

H_Hat then modifies the state transition table to make qhalting
non-terminal, and adds an infinite loop off that state (Which are legal
state transformation for a Turing Machine).

Thus if the Turing Machine H 'aborted' itself, it didn't meet the
requirements.

[toc] | [prev] | [next] | [standalone]


#24366 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-24 15:47 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<08753fef-eed2-482b-878d-717719c8074an@googlegroups.com>
In reply to#24363
On Saturday, 24 October 2020 at 23:30:13 UTC+1, Richard Damon wrote:
> On 10/24/20 6:16 PM, Malcolm McLean wrote: 
> > On Saturday, 24 October 2020 at 23:08:28 UTC+1, olcott wrote: 
> >> On 10/24/2020 3:57 PM, Mike Terry wrote: 
> >> 
> >>> 
> >>> There, I said it again! :) (last time, really...) 
> >> Apparently this whole inner invocation of H_Hat() and outer invocation 
> >> of H_Hat() is against your religion. None-the-less an actual execution 
> >> trace would show that the outer invocation does abort the inner 
> >> invocation thus allowing the outer invocation to terminate normally. 
> >> 
> > The outer invocation H_Hat is the function we are interested in. If it 
> > terminates normally, that's another way of saying it halts. So H() must 
> > return "not aborted". 
> > have you been following my posts? The way round this problem is to 
> > say the H aborts itself. i.e. it smashes the machine (abortion is equivalent 
> > to taking a sledgehammed to the machine). Now H_Hat doesn't halt. 
> >
> Except that then H isn't the Halt decider of the theory. By definition, 
> H needs to be a Turing Machine that starts at a state, traditionally 
> named q0, and eventually, and in finite time, in end up in one of two 
> terminal states, traditionally named something like qhalt, and qnonhalt. 
> If it doesn't end up, in finite time, in one of those two states, it has 
> failed to meet its requirements. 
>
Yes, we have to relax the requirement that H be a Turing machine
to construct an H which stands up to the Linz test case. 
>
> H_Hat then modifies the state transition table to make qhalting 
> non-terminal, and adds an infinite loop off that state (Which are legal 
> state transformation for a Turing Machine). 
> 
> Thus if the Turing Machine H 'aborted' itself, it didn't meet the 
> requirements.
>
No it doesn't. A Turing machine is not allowed to smash the machine 
it is runnning on. However if we ignore this requirement, it is no longer
possible for a test function to invert the result of calling H 
(assuming it detects non-halting). The machine doesn't exist
any longer.

[toc] | [prev] | [next] | [standalone]


#24368 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-24 18:08 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<Wu6dnVBObadlLgnCnZ2dnUU7-Y3NnZ2d@giganews.com>
In reply to#24366
On 10/24/2020 5:47 PM, Malcolm McLean wrote:
> On Saturday, 24 October 2020 at 23:30:13 UTC+1, Richard Damon wrote:
>> On 10/24/20 6:16 PM, Malcolm McLean wrote:
>>> On Saturday, 24 October 2020 at 23:08:28 UTC+1, olcott wrote:
>>>> On 10/24/2020 3:57 PM, Mike Terry wrote:
>>>>
>>>>>
>>>>> There, I said it again! :) (last time, really...)
>>>> Apparently this whole inner invocation of H_Hat() and outer invocation
>>>> of H_Hat() is against your religion. None-the-less an actual execution
>>>> trace would show that the outer invocation does abort the inner
>>>> invocation thus allowing the outer invocation to terminate normally.
>>>>
>>> The outer invocation H_Hat is the function we are interested in. If it
>>> terminates normally, that's another way of saying it halts. So H() must
>>> return "not aborted".
>>> have you been following my posts? The way round this problem is to
>>> say the H aborts itself. i.e. it smashes the machine (abortion is equivalent
>>> to taking a sledgehammed to the machine). Now H_Hat doesn't halt.
>>>
>> Except that then H isn't the Halt decider of the theory. By definition,
>> H needs to be a Turing Machine that starts at a state, traditionally
>> named q0, and eventually, and in finite time, in end up in one of two
>> terminal states, traditionally named something like qhalt, and qnonhalt.
>> If it doesn't end up, in finite time, in one of those two states, it has
>> failed to meet its requirements.
>>
> Yes, we have to relax the requirement that H be a Turing machine
> to construct an H which stands up to the Linz test case.

No we don't not at all.
It is merely that the 100,000 very low level Turing Machine Description 
state transitions would be utterly incomprehensible.

When we write these same steps as their von Neumann architecture 
equivalent and have this equivalent shown in the much higher abstraction 
of C then we can see on a single page what all the key details are.

The messiest part of actual Turing Machines seems to be the lack of 
random access. With a machine having 1 MB of tape every access to data 
that takes one x86 language step could take a million steps.

>> H_Hat then modifies the state transition table to make qhalting
>> non-terminal, and adds an infinite loop off that state (Which are legal
>> state transformation for a Turing Machine).
>>
>> Thus if the Turing Machine H 'aborted' itself, it didn't meet the
>> requirements.
>>
> No it doesn't. A Turing machine is not allowed to smash the machine
> it is runnning on. However if we ignore this requirement, it is no longer
> possible for a test function to invert the result of calling H
> (assuming it detects non-halting). The machine doesn't exist
> any longer.
> 

Machines are only allowed to destroy the process tree of processes that 
they create.

-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24365 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-24 17:45 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<Yo-dnRiBK5MJMwnCnZ2dnUU7-d_NnZ2d@giganews.com>
In reply to#24360
On 10/24/2020 5:16 PM, Malcolm McLean wrote:
> On Saturday, 24 October 2020 at 23:08:28 UTC+1, olcott wrote:
>> On 10/24/2020 3:57 PM, Mike Terry wrote:
>>
>>>
>>> There, I said it again! :) (last time, really...)
>> Apparently this whole inner invocation of H_Hat() and outer invocation
>> of H_Hat() is against your religion. None-the-less an actual execution
>> trace would show that the outer invocation does abort the inner
>> invocation thus allowing the outer invocation to terminate normally.
>>
> The outer invocation H_Hat is the function we are interested in. If it
> terminates normally, that's another way of saying it halts. So H() must
> return "not aborted".

The outer invocation of H_Hat() is an entirely different process having 
much more data than the inner invocation.

> have you been following my posts? 
Yes I read all of the ones replying to me and all but one of the others.

> The way round this problem is to
> say the H aborts itself. i.e. it smashes the machine (abortion is equivalent
> to taking a sledgehammed to the machine). Now H_Hat doesn't halt.
> 

In the invocation of H_Hat(H_Hat) the inner process tree including an 
inner Aborted_Because_Non_Halting_Behavior_Detected(M, N) process are 
aborted before any of them can complete.

So even though both instances of H_Hat() have identical source code 
because they do not have identical data they can have different 
execution traces.

Because the inner H_Hat() is forced to terminate before it gets any 
return value from its instance of 
Aborted_Because_Non_Halting_Behavior_Detected(M, N) the outer instance 
of H_Hat() can have a different execution trace and terminate normally.


-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24465 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMike Terry <news.dead.person.stones@darjeeling.plus.com>
Date2020-10-26 16:29 +0000
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<P_Odnc_rDqDxZAvCnZ2dnUU78IPNnZ2d@brightview.co.uk>
In reply to#24358
On 24/10/2020 23:08, olcott wrote:
> On 10/24/2020 3:57 PM, Mike Terry wrote:
>> On 24/10/2020 21:41, olcott wrote:
>>> On 10/24/2020 2:44 PM, Mike Terry wrote:
>>>> On 24/10/2020 20:05, olcott wrote:
>>>>> On 10/24/2020 2:00 PM, Mike Terry wrote:
>>>>>> On 24/10/2020 19:42, olcott wrote:
>>>>>>> On 10/24/2020 1:32 PM, Mike Terry wrote:
>>>>>>>> On 24/10/2020 18:49, olcott wrote:
>>>>>>>>> On 10/24/2020 11:37 AM, Mike Terry wrote:
>>>>>>>>>> On 24/10/2020 16:36, olcott wrote:
>>>>>>>>>>> On 10/24/2020 9:38 AM, Mike Terry wrote:
>>>>>>>>>>>> On 24/10/2020 07:03, olcott wrote:
>>>>>>>>>>>>> On 10/23/2020 5:51 PM, Mike Terry wrote:
>>>>>>>>>>>>>> On 23/10/2020 00:05, olcott wrote:
>>>>>>>>>>>>>>> On 10/22/2020 5:14 PM, Mike Terry wrote:
>>>>>>>>>>>>>>>> On 22/10/2020 17:38, olcott wrote:
>>>>>>>>>>>>>>>>> On 10/22/2020 10:25 AM, Mike Terry wrote:
>>>>>>>>>>>>>>>>>> On 22/10/2020 15:36, olcott wrote:
>>>>>>>>>>>>>>>>>>> On 10/22/2020 7:00 AM, Richard Damon wrote:
>>>>>>>>>>>>>>>>>>>> On 10/22/20 12:33 AM, olcott wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> The difference is that it is no longer possible for
>>>>>>>>>>>>>>>>>>>>> H_Hat()
>>>>>>>>>>>>>>>>>>>>> to do
>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>> opposite of what H() decides. This transforms an
>>>>>>>>>>>>>>>>>>>>> undecidable
>>>>>>>>>>>>>>>>>>>>> problem
>>>>>>>>>>>>>>>>>>>>> into a decidable problem.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> If H_Hat no longer does what the proof defined, then
>>>>>>>>>>>>>>>>>>>> your
>>>>>>>>>>>>>>>>>>>> demonstration
>>>>>>>>>>>>>>>>>>>> is no longer applicable to the proof.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> If the halt decider is to report whether or not its
>>>>>>>>>>>>>>>>>>> input
>>>>>>>>>>>>>>>>>>> halts
>>>>>>>>>>>>>>>>>>> another
>>>>>>>>>>>>>>>>>>> program can be constructed on the the basis of this halt
>>>>>>>>>>>>>>>>>>> decider
>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>> does the opposite of whatever the halt decider decides.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> This is how H() and H_Hat() are defined in the Linz
>>>>>>>>>>>>>>>>>>> proof.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> If the halt decider is to report whether or not it
>>>>>>>>>>>>>>>>>>> aborted its
>>>>>>>>>>>>>>>>>>> input
>>>>>>>>>>>>>>>>>>> program because its input program would otherwise cause
>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> halt
>>>>>>>>>>>>>>>>>>> decider
>>>>>>>>>>>>>>>>>>> to get stuck in infinite execution then this other
>>>>>>>>>>>>>>>>>>> program
>>>>>>>>>>>>>>>>>>> can no
>>>>>>>>>>>>>>>>>>> longer
>>>>>>>>>>>>>>>>>>> fool its halt decider and do the opposite of whatever it
>>>>>>>>>>>>>>>>>>> decides.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> If H() aborts the execution of H_Hat() then H_Hat()
>>>>>>>>>>>>>>>>>>> cannot
>>>>>>>>>>>>>>>>>>> continue to
>>>>>>>>>>>>>>>>>>> execute because H() has complete control over H_Hat.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> The end result of this slight change is that the halting
>>>>>>>>>>>>>>>>>>> problem
>>>>>>>>>>>>>>>>>>> can no
>>>>>>>>>>>>>>>>>>> longer be shown to be undecidable.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> It is suspicious that in none of this have you ever
>>>>>>>>>>>>>>>>>> stated
>>>>>>>>>>>>>>>>>> what is
>>>>>>>>>>>>>>>>>> actually wrong in the Linz proof.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> When the halting problem is defined as:
>>>>>>>>>>>>>>>>> bool Does_It_Halt(u32 P, u32 I)
>>>>>>>>>>>>>>>>> another program can be constructed on the basis of
>>>>>>>>>>>>>>>>> Does_It_Halt()
>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>> does the opposite of whatever Does_It_Halt() decides.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Yes, regardless of the internal details of Does_It_Halt().
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> When the halting problem is defined as:
>>>>>>>>>>>>>>>>> bool Was_Its_Execution_Aborted(u32 P, u32 I)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> another program CANNOT be constructed on the basis of
>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() that does the opposite of
>>>>>>>>>>>>>>>>> whatever
>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() decides.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Sure, if you interpret your question literally as asking
>>>>>>>>>>>>>>>> whether P
>>>>>>>>>>>>>>>> would actually be aborted if it executes under the UTM
>>>>>>>>>>>>>>>> within
>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted()!
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> However, another program CAN be constructed on the basis of
>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() that:
>>>>>>>>>>>>>>>> -   halts if Was_Its_Execution_Aborted() decides "aborted"
>>>>>>>>>>>>>>>> -   loops if Was_Its_Execution_Aborted() decides "halted"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> (right?)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Wrong.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> No, right.  To avoid a silly pantomine argument, here is an
>>>>>>>>>>>>>> example of
>>>>>>>>>>>>>> such a function:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> int H_Hat(u32 M)
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>     if (Was_Its_Execution_Aborted(M, M))
>>>>>>>>>>>>>>     {
>>>>>>>>>>>>>>       // Was_Its_Execution_Aborted says that M(M) was aborted
>>>>>>>>>>>>>>       HALT;       // so we halt
>>>>>>>>>>>>>>     }
>>>>>>>>>>>>>>     else
>>>>>>>>>>>>>>     {
>>>>>>>>>>>>>>       // Was_Its_Execution_Aborted says that M(M) halted
>>>>>>>>>>>>>>       HERE: goto HERE;   // so we loop
>>>>>>>>>>>>>>     }
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> and for completeness, here is the function being invoked from
>>>>>>>>>>>>>> main():
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>     u32 M = (u32)H_Hat;
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>     H_Hat(M);       // run H_Hat with input H_Hat
>>>>>>>>>>>>>>     HALT;
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> You see, H_Hat /is/ constructed so that if
>>>>>>>>>>>>>> Was_Its_Execution_Aborted(M, M) returns "aborted" (nonzero),
>>>>>>>>>>>>>> H_Hat
>>>>>>>>>>>>>> will halt, and if Was_Its_Execution_Aborted(M, M) returns
>>>>>>>>>>>>>> "halted"
>>>>>>>>>>>>>> (zero), H_Hat will loop.  Just like I said.  Thre is no
>>>>>>>>>>>>>> subtle
>>>>>>>>>>>>>> philosophical point here, just beginner knowledge of the C
>>>>>>>>>>>>>> programming
>>>>>>>>>>>>>> language.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> (To save you making a silly response, yes IF we were to
>>>>>>>>>>>>>> run the
>>>>>>>>>>>>>> program under a debugger or emulator of some kind, and we
>>>>>>>>>>>>>> aborted the
>>>>>>>>>>>>>> run at the "if (Abort)" statement or earlier, then of
>>>>>>>>>>>>>> course we
>>>>>>>>>>>>>> would
>>>>>>>>>>>>>> not get to see what it actually does next.  (Duh.)  That's
>>>>>>>>>>>>>> irrelevent
>>>>>>>>>>>>>> because regardless of this, H_Hat as constructed meets the
>>>>>>>>>>>>>> conditions
>>>>>>>>>>>>>> just as I described.)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>  > There is no way to make the revised halting question
>>>>>>>>>>>>>> contradictory.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> DebugTrace() either reports that it has aborted the
>>>>>>>>>>>>>>> execution
>>>>>>>>>>>>>>> of its
>>>>>>>>>>>>>>> input or it reports that its input has not been aborted
>>>>>>>>>>>>>>> after
>>>>>>>>>>>>>>> its
>>>>>>>>>>>>>>> input
>>>>>>>>>>>>>>> has terminated.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>  > [A quick observation: you've flipped to talking about
>>>>>>>>>>>>>> DebugTrace()
>>>>>>>>>>>>>> rather than Was_Its_Execution_Aborted() which we were
>>>>>>>>>>>>>> discussing.
>>>>>>>>>>>>>> I'll just take it they're the same thing, and continue saying
>>>>>>>>>>>>>> Was_Its_Execution_Aborted().]
>>>>>>>>>>>>>
>>>>>>>>>>>>> OK good. I like that. Make the function say what it really
>>>>>>>>>>>>> means.
>>>>>>>>>>>>> That is good software engineering.
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I never said otherwise.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> BUT bear in mind that H (as opposed to
>>>>>>>>>>>>>> Was_Its_Execution_Aborted())
>>>>>>>>>>>>>> plays the role in all this of a Linz *Halt Decider*, and
>>>>>>>>>>>>>> so is
>>>>>>>>>>>>>> required to deliver its HD decision *HALT* or *NOT_HALT*.
>>>>>>>>>>>>>
>>>>>>>>>>>>> No, not at all. Not in the least little bit.
>>>>>>>>>>>>> This takes my solution of removing the pathological
>>>>>>>>>>>>> self-reference
>>>>>>>>>>>>> from
>>>>>>>>>>>>> the halting decision and tosses this solution in the trash.
>>>>>>>>>>>>
>>>>>>>>>>>> Maybe, and that would be the right thing to do if your
>>>>>>>>>>>> solution is
>>>>>>>>>>>> wrong.  In any case, if you can't refute the Linz proof without
>>>>>>>>>>>> changing the meaning of "Halt Decider", then your solution is
>>>>>>>>>>>> wrong.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I am refuting that the Linz proof proves that the halting
>>>>>>>>>>> problem is
>>>>>>>>>>> undecidable by finding another way to define the halt decider
>>>>>>>>>>> that
>>>>>>>>>>> cannot be contradicted.
>>>>>>>>>>
>>>>>>>>>> The Linz halt decider corresponds to the correct (HP) definition
>>>>>>>>>> of a
>>>>>>>>>> halt decider.  If you change this definition you are not
>>>>>>>>>> discussing HP.
>>>>>>>>>
>>>>>>>>> As long as a halt decider cannot be shown to make this decision
>>>>>>>>> incorrectly for any of its inputs then the halting problem
>>>>>>>>> cannot be
>>>>>>>>> shown to be undecidable:
>>>>>>>>>
>>>>>>>>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
>>>>>>>>
>>>>>>>> The Linz proof shows HP to be undecidable.  Your refuting code
>>>>>>>> conforms with the Linz conclusion, and does not refute anything.
>>>>>>>
>>>>>>> Unless you can concretely show how this function would get the wrong
>>>>>>> answer all of your rebuttal is ultimately totally vacuous:
>>>>>>>
>>>>>>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
>>>>>>>
>>>>>>
>>>>>> In your code, the function answers "non halting behaviour detected"
>>>>>> for input which actually halts, and so by any reasonable
>>>>>> definition of
>>>>>> the words, it has decided incorrectly.
>>>>>
>>>>> Bullshit. The actual question that it always correctly answers is:
>>>>> Does the input have to be aborted to prevent infinite execution?
>>>>
>>>> I provided the traces which back up what I said, so it's not bullshit.
>>>> You have snipped them because you don't want to look stupid, so I'm
>>>> going to restore them:
>>>>
>>>> H_Hat machine trace
>>>> -------------------
>>>>
>>>> H_Hat starts (main() calls H_Hat(H_Hat))
>>>>     H_Hat calls Was_Its_Execution_Aborted(H_Hat,H_Hat)
>>>>       Was_Its_Execution_Aborted emulates H_Hat(H_Hat)
>>>>       Was_Its_Execution_Aborted decides the emulated program ..
>>>>                  .. will never terminate if not aborted
>>>>       Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>>>     H_Hat *halts*
>>>>
>>>> OK, so the H_Hat calculation halts...
>>>
>>> In this case we have an outer instance of H_Hat() an inner instance of
>>> H_Hat(). The outer instance of H_Hat() is executed in the master UTM
>>> process context of x86utm.
>>>
>>> This outer instance of H_Hat() invokes
>>> Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) which
>>> creates the inner instance of H_Hat() in its own process context and
>>> executes it. It then returns true to the outer instance of H_Hat() after
>>> aborting the inner instance.
>>
>> ..*and then terminates*
>>
>> The calculation H_Hat(H_Hat) halts.  So if
>> Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) says there
>> was "non-halting behaviour" it was wrong.
>>
>> No point in saying this over and over....
>>
>>
>>>
>>>> H machine trace
>>>>
>>>> ---------------
>>>> H starts (main() calls H(H_Hat,H_Hat))
>>>>     H calls Was_Its_Execution_Aborted(H_Hat,H_Hat)
>>>>       Was_Its_Execution_Aborted emulates H_Hat(H_Hat)
>>>>       Was_Its_Execution_Aborted decides the emulated program ..
>>>>                  .. will never terminate if not aborted
>>>>       Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>>>     H halts, with EAX=0 [= *NOT_HALT* decision]
>>>>
>>>
>>> In this case we have an instance of H() and an instance of H_Hat(). The
>>>  instance of H() is executed in the master UTM process context of
>>> x86utm.
>>>
>>> H() invokes Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
>>> which creates the instance of H_Hat() and executes it. It then returns
>>> true to H() after aborting the instance of _H_Hat().
>>
>> Again, returning true to H is supposed to say it detected non-halting
>> behaviour, but the calculation it is examining actually halts.
>>
>> There, I said it again! :)  (last time, really...)
> Apparently this whole inner invocation of H_Hat() and outer invocation
> of H_Hat() is against your religion.

Why do you say that?  I understand perfectly about outer and inner 
invocations of H_Hat().  I understand it better than you, because I lack 
your confusions on what's going on.

Incidentally, I believe I've realised where you are going wrong in your 
thinking!  (If I'm right, it will come out in your answer to the 
question below...)

> None-the-less an actual execution
> trace would show that the outer invocation does abort the inner
> invocation thus allowing the outer invocation to terminate normally.

That's fine.

If the outer invocation aborts the inner invocation, that implies that 
the H_Hat(H_Hat) calculation halts.  [When I say a calculation halts, I 
mean that there is a number n such that after n steps the calculation 
reaches a halt state.  It is nothing to do with anything being emulated, 
or run on some physical computer.]

Do you agree with this?

Mike.

[toc] | [prev] | [next] | [standalone]


#24476 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-26 13:03 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<GJ-dnb_eE6sUkgrCnZ2dnUU7-L3NnZ2d@giganews.com>
In reply to#24465
On 10/26/2020 11:29 AM, Mike Terry wrote:
> On 24/10/2020 23:08, olcott wrote:
>> On 10/24/2020 3:57 PM, Mike Terry wrote:
>>> On 24/10/2020 21:41, olcott wrote:
>>>> On 10/24/2020 2:44 PM, Mike Terry wrote:
>>>>> On 24/10/2020 20:05, olcott wrote:
>>>>>> On 10/24/2020 2:00 PM, Mike Terry wrote:
>>>>>>> On 24/10/2020 19:42, olcott wrote:
>>>>>>>> On 10/24/2020 1:32 PM, Mike Terry wrote:
>>>>>>>>> On 24/10/2020 18:49, olcott wrote:
>>>>>>>>>> On 10/24/2020 11:37 AM, Mike Terry wrote:
>>>>>>>>>>> On 24/10/2020 16:36, olcott wrote:
>>>>>>>>>>>> On 10/24/2020 9:38 AM, Mike Terry wrote:
>>>>>>>>>>>>> On 24/10/2020 07:03, olcott wrote:
>>>>>>>>>>>>>> On 10/23/2020 5:51 PM, Mike Terry wrote:
>>>>>>>>>>>>>>> On 23/10/2020 00:05, olcott wrote:
>>>>>>>>>>>>>>>> On 10/22/2020 5:14 PM, Mike Terry wrote:
>>>>>>>>>>>>>>>>> On 22/10/2020 17:38, olcott wrote:
>>>>>>>>>>>>>>>>>> On 10/22/2020 10:25 AM, Mike Terry wrote:
>>>>>>>>>>>>>>>>>>> On 22/10/2020 15:36, olcott wrote:
>>>>>>>>>>>>>>>>>>>> On 10/22/2020 7:00 AM, Richard Damon wrote:
>>>>>>>>>>>>>>>>>>>>> On 10/22/20 12:33 AM, olcott wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> The difference is that it is no longer possible for
>>>>>>>>>>>>>>>>>>>>>> H_Hat()
>>>>>>>>>>>>>>>>>>>>>> to do
>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>> opposite of what H() decides. This transforms an
>>>>>>>>>>>>>>>>>>>>>> undecidable
>>>>>>>>>>>>>>>>>>>>>> problem
>>>>>>>>>>>>>>>>>>>>>> into a decidable problem.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> If H_Hat no longer does what the proof defined, then
>>>>>>>>>>>>>>>>>>>>> your
>>>>>>>>>>>>>>>>>>>>> demonstration
>>>>>>>>>>>>>>>>>>>>> is no longer applicable to the proof.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> If the halt decider is to report whether or not its
>>>>>>>>>>>>>>>>>>>> input
>>>>>>>>>>>>>>>>>>>> halts
>>>>>>>>>>>>>>>>>>>> another
>>>>>>>>>>>>>>>>>>>> program can be constructed on the the basis of this 
>>>>>>>>>>>>>>>>>>>> halt
>>>>>>>>>>>>>>>>>>>> decider
>>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>> does the opposite of whatever the halt decider decides.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> This is how H() and H_Hat() are defined in the Linz
>>>>>>>>>>>>>>>>>>>> proof.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> If the halt decider is to report whether or not it
>>>>>>>>>>>>>>>>>>>> aborted its
>>>>>>>>>>>>>>>>>>>> input
>>>>>>>>>>>>>>>>>>>> program because its input program would otherwise cause
>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>> halt
>>>>>>>>>>>>>>>>>>>> decider
>>>>>>>>>>>>>>>>>>>> to get stuck in infinite execution then this other
>>>>>>>>>>>>>>>>>>>> program
>>>>>>>>>>>>>>>>>>>> can no
>>>>>>>>>>>>>>>>>>>> longer
>>>>>>>>>>>>>>>>>>>> fool its halt decider and do the opposite of 
>>>>>>>>>>>>>>>>>>>> whatever it
>>>>>>>>>>>>>>>>>>>> decides.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> If H() aborts the execution of H_Hat() then H_Hat()
>>>>>>>>>>>>>>>>>>>> cannot
>>>>>>>>>>>>>>>>>>>> continue to
>>>>>>>>>>>>>>>>>>>> execute because H() has complete control over H_Hat.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> The end result of this slight change is that the 
>>>>>>>>>>>>>>>>>>>> halting
>>>>>>>>>>>>>>>>>>>> problem
>>>>>>>>>>>>>>>>>>>> can no
>>>>>>>>>>>>>>>>>>>> longer be shown to be undecidable.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> It is suspicious that in none of this have you ever
>>>>>>>>>>>>>>>>>>> stated
>>>>>>>>>>>>>>>>>>> what is
>>>>>>>>>>>>>>>>>>> actually wrong in the Linz proof.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> When the halting problem is defined as:
>>>>>>>>>>>>>>>>>> bool Does_It_Halt(u32 P, u32 I)
>>>>>>>>>>>>>>>>>> another program can be constructed on the basis of
>>>>>>>>>>>>>>>>>> Does_It_Halt()
>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>> does the opposite of whatever Does_It_Halt() decides.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Yes, regardless of the internal details of Does_It_Halt().
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> When the halting problem is defined as:
>>>>>>>>>>>>>>>>>> bool Was_Its_Execution_Aborted(u32 P, u32 I)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> another program CANNOT be constructed on the basis of
>>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() that does the opposite of
>>>>>>>>>>>>>>>>>> whatever
>>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() decides.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Sure, if you interpret your question literally as asking
>>>>>>>>>>>>>>>>> whether P
>>>>>>>>>>>>>>>>> would actually be aborted if it executes under the UTM
>>>>>>>>>>>>>>>>> within
>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted()!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> However, another program CAN be constructed on the 
>>>>>>>>>>>>>>>>> basis of
>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() that:
>>>>>>>>>>>>>>>>> -   halts if Was_Its_Execution_Aborted() decides "aborted"
>>>>>>>>>>>>>>>>> -   loops if Was_Its_Execution_Aborted() decides "halted"
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> (right?)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Wrong.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> No, right.  To avoid a silly pantomine argument, here is an
>>>>>>>>>>>>>>> example of
>>>>>>>>>>>>>>> such a function:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> int H_Hat(u32 M)
>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>     if (Was_Its_Execution_Aborted(M, M))
>>>>>>>>>>>>>>>     {
>>>>>>>>>>>>>>>       // Was_Its_Execution_Aborted says that M(M) was 
>>>>>>>>>>>>>>> aborted
>>>>>>>>>>>>>>>       HALT;       // so we halt
>>>>>>>>>>>>>>>     }
>>>>>>>>>>>>>>>     else
>>>>>>>>>>>>>>>     {
>>>>>>>>>>>>>>>       // Was_Its_Execution_Aborted says that M(M) halted
>>>>>>>>>>>>>>>       HERE: goto HERE;   // so we loop
>>>>>>>>>>>>>>>     }
>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> and for completeness, here is the function being invoked 
>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>> main():
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>     u32 M = (u32)H_Hat;
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>     H_Hat(M);       // run H_Hat with input H_Hat
>>>>>>>>>>>>>>>     HALT;
>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> You see, H_Hat /is/ constructed so that if
>>>>>>>>>>>>>>> Was_Its_Execution_Aborted(M, M) returns "aborted" (nonzero),
>>>>>>>>>>>>>>> H_Hat
>>>>>>>>>>>>>>> will halt, and if Was_Its_Execution_Aborted(M, M) returns
>>>>>>>>>>>>>>> "halted"
>>>>>>>>>>>>>>> (zero), H_Hat will loop.  Just like I said.  Thre is no
>>>>>>>>>>>>>>> subtle
>>>>>>>>>>>>>>> philosophical point here, just beginner knowledge of the C
>>>>>>>>>>>>>>> programming
>>>>>>>>>>>>>>> language.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> (To save you making a silly response, yes IF we were to
>>>>>>>>>>>>>>> run the
>>>>>>>>>>>>>>> program under a debugger or emulator of some kind, and we
>>>>>>>>>>>>>>> aborted the
>>>>>>>>>>>>>>> run at the "if (Abort)" statement or earlier, then of
>>>>>>>>>>>>>>> course we
>>>>>>>>>>>>>>> would
>>>>>>>>>>>>>>> not get to see what it actually does next.  (Duh.)  That's
>>>>>>>>>>>>>>> irrelevent
>>>>>>>>>>>>>>> because regardless of this, H_Hat as constructed meets the
>>>>>>>>>>>>>>> conditions
>>>>>>>>>>>>>>> just as I described.)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>  > There is no way to make the revised halting question
>>>>>>>>>>>>>>> contradictory.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> DebugTrace() either reports that it has aborted the
>>>>>>>>>>>>>>>> execution
>>>>>>>>>>>>>>>> of its
>>>>>>>>>>>>>>>> input or it reports that its input has not been aborted
>>>>>>>>>>>>>>>> after
>>>>>>>>>>>>>>>> its
>>>>>>>>>>>>>>>> input
>>>>>>>>>>>>>>>> has terminated.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>  > [A quick observation: you've flipped to talking about
>>>>>>>>>>>>>>> DebugTrace()
>>>>>>>>>>>>>>> rather than Was_Its_Execution_Aborted() which we were
>>>>>>>>>>>>>>> discussing.
>>>>>>>>>>>>>>> I'll just take it they're the same thing, and continue 
>>>>>>>>>>>>>>> saying
>>>>>>>>>>>>>>> Was_Its_Execution_Aborted().]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> OK good. I like that. Make the function say what it really
>>>>>>>>>>>>>> means.
>>>>>>>>>>>>>> That is good software engineering.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I never said otherwise.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> BUT bear in mind that H (as opposed to
>>>>>>>>>>>>>>> Was_Its_Execution_Aborted())
>>>>>>>>>>>>>>> plays the role in all this of a Linz *Halt Decider*, and
>>>>>>>>>>>>>>> so is
>>>>>>>>>>>>>>> required to deliver its HD decision *HALT* or *NOT_HALT*.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> No, not at all. Not in the least little bit.
>>>>>>>>>>>>>> This takes my solution of removing the pathological
>>>>>>>>>>>>>> self-reference
>>>>>>>>>>>>>> from
>>>>>>>>>>>>>> the halting decision and tosses this solution in the trash.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Maybe, and that would be the right thing to do if your
>>>>>>>>>>>>> solution is
>>>>>>>>>>>>> wrong.  In any case, if you can't refute the Linz proof 
>>>>>>>>>>>>> without
>>>>>>>>>>>>> changing the meaning of "Halt Decider", then your solution is
>>>>>>>>>>>>> wrong.
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I am refuting that the Linz proof proves that the halting
>>>>>>>>>>>> problem is
>>>>>>>>>>>> undecidable by finding another way to define the halt decider
>>>>>>>>>>>> that
>>>>>>>>>>>> cannot be contradicted.
>>>>>>>>>>>
>>>>>>>>>>> The Linz halt decider corresponds to the correct (HP) definition
>>>>>>>>>>> of a
>>>>>>>>>>> halt decider.  If you change this definition you are not
>>>>>>>>>>> discussing HP.
>>>>>>>>>>
>>>>>>>>>> As long as a halt decider cannot be shown to make this decision
>>>>>>>>>> incorrectly for any of its inputs then the halting problem
>>>>>>>>>> cannot be
>>>>>>>>>> shown to be undecidable:
>>>>>>>>>>
>>>>>>>>>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
>>>>>>>>>
>>>>>>>>> The Linz proof shows HP to be undecidable.  Your refuting code
>>>>>>>>> conforms with the Linz conclusion, and does not refute anything.
>>>>>>>>
>>>>>>>> Unless you can concretely show how this function would get the 
>>>>>>>> wrong
>>>>>>>> answer all of your rebuttal is ultimately totally vacuous:
>>>>>>>>
>>>>>>>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
>>>>>>>>
>>>>>>>
>>>>>>> In your code, the function answers "non halting behaviour detected"
>>>>>>> for input which actually halts, and so by any reasonable
>>>>>>> definition of
>>>>>>> the words, it has decided incorrectly.
>>>>>>
>>>>>> Bullshit. The actual question that it always correctly answers is:
>>>>>> Does the input have to be aborted to prevent infinite execution?
>>>>>
>>>>> I provided the traces which back up what I said, so it's not bullshit.
>>>>> You have snipped them because you don't want to look stupid, so I'm
>>>>> going to restore them:
>>>>>
>>>>> H_Hat machine trace
>>>>> -------------------
>>>>>
>>>>> H_Hat starts (main() calls H_Hat(H_Hat))
>>>>>     H_Hat calls Was_Its_Execution_Aborted(H_Hat,H_Hat)
>>>>>       Was_Its_Execution_Aborted emulates H_Hat(H_Hat)
>>>>>       Was_Its_Execution_Aborted decides the emulated program ..
>>>>>                  .. will never terminate if not aborted
>>>>>       Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>>>>     H_Hat *halts*
>>>>>
>>>>> OK, so the H_Hat calculation halts...
>>>>
>>>> In this case we have an outer instance of H_Hat() an inner instance of
>>>> H_Hat(). The outer instance of H_Hat() is executed in the master UTM
>>>> process context of x86utm.
>>>>
>>>> This outer instance of H_Hat() invokes
>>>> Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) which
>>>> creates the inner instance of H_Hat() in its own process context and
>>>> executes it. It then returns true to the outer instance of H_Hat() 
>>>> after
>>>> aborting the inner instance.
>>>
>>> ..*and then terminates*
>>>
>>> The calculation H_Hat(H_Hat) halts.  So if
>>> Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) says there
>>> was "non-halting behaviour" it was wrong.
>>>
>>> No point in saying this over and over....
>>>
>>>
>>>>
>>>>> H machine trace
>>>>>
>>>>> ---------------
>>>>> H starts (main() calls H(H_Hat,H_Hat))
>>>>>     H calls Was_Its_Execution_Aborted(H_Hat,H_Hat)
>>>>>       Was_Its_Execution_Aborted emulates H_Hat(H_Hat)
>>>>>       Was_Its_Execution_Aborted decides the emulated program ..
>>>>>                  .. will never terminate if not aborted
>>>>>       Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>>>>     H halts, with EAX=0 [= *NOT_HALT* decision]
>>>>>
>>>>
>>>> In this case we have an instance of H() and an instance of H_Hat(). The
>>>>  instance of H() is executed in the master UTM process context of
>>>> x86utm.
>>>>
>>>> H() invokes Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
>>>> which creates the instance of H_Hat() and executes it. It then returns
>>>> true to H() after aborting the instance of _H_Hat().
>>>
>>> Again, returning true to H is supposed to say it detected non-halting
>>> behaviour, but the calculation it is examining actually halts.
>>>
>>> There, I said it again! :)  (last time, really...)
>> Apparently this whole inner invocation of H_Hat() and outer invocation
>> of H_Hat() is against your religion.
> 
> Why do you say that?  I understand perfectly about outer and inner 
> invocations of H_Hat().  I understand it better than you, because I lack 
> your confusions on what's going on.
> 
> Incidentally, I believe I've realised where you are going wrong in your 
> thinking!  (If I'm right, it will come out in your answer to the 
> question below...)
> 
>> None-the-less an actual execution
>> trace would show that the outer invocation does abort the inner
>> invocation thus allowing the outer invocation to terminate normally.
> 
> That's fine.
> 
> If the outer invocation aborts the inner invocation, that implies that 
> the H_Hat(H_Hat) calculation halts.  

None of the invocations of H_Hat() would ever halt unless they are 
aborted. That is why this is the correct halt decider question:
bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)

When the return value of true is provided for the (M, N) input this 
return value is correct. Every other return value from
bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)
does not occur because every other
bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)
has had its execution terminated before it ever returns any value.

Therefore we can conclude that
bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)
Is a halt decider function that cannot be shown to be incorrect.

> [When I say a calculation halts, I 
> mean that there is a number n such that after n steps the calculation 
> reaches a halt state.  It is nothing to do with anything being emulated, 
> or run on some physical computer.]
> 
> Do you agree with this?
> 
> Mike.


No. I pointed out the false assumptions.
The one time that
bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)
returns its decision value this decision value is correct.
There are no other times that it reteuns its decsion value.


-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24479 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction

Fromolcott <NoOne@NoWhere.com>
Date2020-10-26 13:14 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction
Message-ID<qu-dnWnPetCUjwrCnZ2dnUU7-KFQAAAA@giganews.com>
In reply to#24476
On 10/26/2020 1:03 PM, olcott wrote:
> On 10/26/2020 11:29 AM, Mike Terry wrote:
>> On 24/10/2020 23:08, olcott wrote:
>>> On 10/24/2020 3:57 PM, Mike Terry wrote:
>>>> On 24/10/2020 21:41, olcott wrote:
>>>>> On 10/24/2020 2:44 PM, Mike Terry wrote:
>>>>>> On 24/10/2020 20:05, olcott wrote:
>>>>>>> On 10/24/2020 2:00 PM, Mike Terry wrote:
>>>>>>>> On 24/10/2020 19:42, olcott wrote:
>>>>>>>>> On 10/24/2020 1:32 PM, Mike Terry wrote:
>>>>>>>>>> On 24/10/2020 18:49, olcott wrote:
>>>>>>>>>>> On 10/24/2020 11:37 AM, Mike Terry wrote:
>>>>>>>>>>>> On 24/10/2020 16:36, olcott wrote:
>>>>>>>>>>>>> On 10/24/2020 9:38 AM, Mike Terry wrote:
>>>>>>>>>>>>>> On 24/10/2020 07:03, olcott wrote:
>>>>>>>>>>>>>>> On 10/23/2020 5:51 PM, Mike Terry wrote:
>>>>>>>>>>>>>>>> On 23/10/2020 00:05, olcott wrote:
>>>>>>>>>>>>>>>>> On 10/22/2020 5:14 PM, Mike Terry wrote:
>>>>>>>>>>>>>>>>>> On 22/10/2020 17:38, olcott wrote:
>>>>>>>>>>>>>>>>>>> On 10/22/2020 10:25 AM, Mike Terry wrote:
>>>>>>>>>>>>>>>>>>>> On 22/10/2020 15:36, olcott wrote:
>>>>>>>>>>>>>>>>>>>>> On 10/22/2020 7:00 AM, Richard Damon wrote:
>>>>>>>>>>>>>>>>>>>>>> On 10/22/20 12:33 AM, olcott wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> The difference is that it is no longer possible for
>>>>>>>>>>>>>>>>>>>>>>> H_Hat()
>>>>>>>>>>>>>>>>>>>>>>> to do
>>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>>> opposite of what H() decides. This transforms an
>>>>>>>>>>>>>>>>>>>>>>> undecidable
>>>>>>>>>>>>>>>>>>>>>>> problem
>>>>>>>>>>>>>>>>>>>>>>> into a decidable problem.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> If H_Hat no longer does what the proof defined, then
>>>>>>>>>>>>>>>>>>>>>> your
>>>>>>>>>>>>>>>>>>>>>> demonstration
>>>>>>>>>>>>>>>>>>>>>> is no longer applicable to the proof.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> If the halt decider is to report whether or not its
>>>>>>>>>>>>>>>>>>>>> input
>>>>>>>>>>>>>>>>>>>>> halts
>>>>>>>>>>>>>>>>>>>>> another
>>>>>>>>>>>>>>>>>>>>> program can be constructed on the the basis of this 
>>>>>>>>>>>>>>>>>>>>> halt
>>>>>>>>>>>>>>>>>>>>> decider
>>>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>>> does the opposite of whatever the halt decider 
>>>>>>>>>>>>>>>>>>>>> decides.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> This is how H() and H_Hat() are defined in the Linz
>>>>>>>>>>>>>>>>>>>>> proof.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> If the halt decider is to report whether or not it
>>>>>>>>>>>>>>>>>>>>> aborted its
>>>>>>>>>>>>>>>>>>>>> input
>>>>>>>>>>>>>>>>>>>>> program because its input program would otherwise 
>>>>>>>>>>>>>>>>>>>>> cause
>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>> halt
>>>>>>>>>>>>>>>>>>>>> decider
>>>>>>>>>>>>>>>>>>>>> to get stuck in infinite execution then this other
>>>>>>>>>>>>>>>>>>>>> program
>>>>>>>>>>>>>>>>>>>>> can no
>>>>>>>>>>>>>>>>>>>>> longer
>>>>>>>>>>>>>>>>>>>>> fool its halt decider and do the opposite of 
>>>>>>>>>>>>>>>>>>>>> whatever it
>>>>>>>>>>>>>>>>>>>>> decides.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> If H() aborts the execution of H_Hat() then H_Hat()
>>>>>>>>>>>>>>>>>>>>> cannot
>>>>>>>>>>>>>>>>>>>>> continue to
>>>>>>>>>>>>>>>>>>>>> execute because H() has complete control over H_Hat.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> The end result of this slight change is that the 
>>>>>>>>>>>>>>>>>>>>> halting
>>>>>>>>>>>>>>>>>>>>> problem
>>>>>>>>>>>>>>>>>>>>> can no
>>>>>>>>>>>>>>>>>>>>> longer be shown to be undecidable.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> It is suspicious that in none of this have you ever
>>>>>>>>>>>>>>>>>>>> stated
>>>>>>>>>>>>>>>>>>>> what is
>>>>>>>>>>>>>>>>>>>> actually wrong in the Linz proof.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> When the halting problem is defined as:
>>>>>>>>>>>>>>>>>>> bool Does_It_Halt(u32 P, u32 I)
>>>>>>>>>>>>>>>>>>> another program can be constructed on the basis of
>>>>>>>>>>>>>>>>>>> Does_It_Halt()
>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>> does the opposite of whatever Does_It_Halt() decides.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Yes, regardless of the internal details of 
>>>>>>>>>>>>>>>>>> Does_It_Halt().
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> When the halting problem is defined as:
>>>>>>>>>>>>>>>>>>> bool Was_Its_Execution_Aborted(u32 P, u32 I)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> another program CANNOT be constructed on the basis of
>>>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() that does the opposite of
>>>>>>>>>>>>>>>>>>> whatever
>>>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() decides.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Sure, if you interpret your question literally as asking
>>>>>>>>>>>>>>>>>> whether P
>>>>>>>>>>>>>>>>>> would actually be aborted if it executes under the UTM
>>>>>>>>>>>>>>>>>> within
>>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted()!
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> However, another program CAN be constructed on the 
>>>>>>>>>>>>>>>>>> basis of
>>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() that:
>>>>>>>>>>>>>>>>>> -   halts if Was_Its_Execution_Aborted() decides 
>>>>>>>>>>>>>>>>>> "aborted"
>>>>>>>>>>>>>>>>>> -   loops if Was_Its_Execution_Aborted() decides "halted"
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> (right?)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Wrong.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> No, right.  To avoid a silly pantomine argument, here is an
>>>>>>>>>>>>>>>> example of
>>>>>>>>>>>>>>>> such a function:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> int H_Hat(u32 M)
>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>     if (Was_Its_Execution_Aborted(M, M))
>>>>>>>>>>>>>>>>     {
>>>>>>>>>>>>>>>>       // Was_Its_Execution_Aborted says that M(M) was 
>>>>>>>>>>>>>>>> aborted
>>>>>>>>>>>>>>>>       HALT;       // so we halt
>>>>>>>>>>>>>>>>     }
>>>>>>>>>>>>>>>>     else
>>>>>>>>>>>>>>>>     {
>>>>>>>>>>>>>>>>       // Was_Its_Execution_Aborted says that M(M) halted
>>>>>>>>>>>>>>>>       HERE: goto HERE;   // so we loop
>>>>>>>>>>>>>>>>     }
>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> and for completeness, here is the function being invoked 
>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>> main():
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>     u32 M = (u32)H_Hat;
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>     H_Hat(M);       // run H_Hat with input H_Hat
>>>>>>>>>>>>>>>>     HALT;
>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> You see, H_Hat /is/ constructed so that if
>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted(M, M) returns "aborted" 
>>>>>>>>>>>>>>>> (nonzero),
>>>>>>>>>>>>>>>> H_Hat
>>>>>>>>>>>>>>>> will halt, and if Was_Its_Execution_Aborted(M, M) returns
>>>>>>>>>>>>>>>> "halted"
>>>>>>>>>>>>>>>> (zero), H_Hat will loop.  Just like I said.  Thre is no
>>>>>>>>>>>>>>>> subtle
>>>>>>>>>>>>>>>> philosophical point here, just beginner knowledge of the C
>>>>>>>>>>>>>>>> programming
>>>>>>>>>>>>>>>> language.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> (To save you making a silly response, yes IF we were to
>>>>>>>>>>>>>>>> run the
>>>>>>>>>>>>>>>> program under a debugger or emulator of some kind, and we
>>>>>>>>>>>>>>>> aborted the
>>>>>>>>>>>>>>>> run at the "if (Abort)" statement or earlier, then of
>>>>>>>>>>>>>>>> course we
>>>>>>>>>>>>>>>> would
>>>>>>>>>>>>>>>> not get to see what it actually does next.  (Duh.)  That's
>>>>>>>>>>>>>>>> irrelevent
>>>>>>>>>>>>>>>> because regardless of this, H_Hat as constructed meets the
>>>>>>>>>>>>>>>> conditions
>>>>>>>>>>>>>>>> just as I described.)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>  > There is no way to make the revised halting question
>>>>>>>>>>>>>>>> contradictory.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> DebugTrace() either reports that it has aborted the
>>>>>>>>>>>>>>>>> execution
>>>>>>>>>>>>>>>>> of its
>>>>>>>>>>>>>>>>> input or it reports that its input has not been aborted
>>>>>>>>>>>>>>>>> after
>>>>>>>>>>>>>>>>> its
>>>>>>>>>>>>>>>>> input
>>>>>>>>>>>>>>>>> has terminated.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>  > [A quick observation: you've flipped to talking about
>>>>>>>>>>>>>>>> DebugTrace()
>>>>>>>>>>>>>>>> rather than Was_Its_Execution_Aborted() which we were
>>>>>>>>>>>>>>>> discussing.
>>>>>>>>>>>>>>>> I'll just take it they're the same thing, and continue 
>>>>>>>>>>>>>>>> saying
>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted().]
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> OK good. I like that. Make the function say what it really
>>>>>>>>>>>>>>> means.
>>>>>>>>>>>>>>> That is good software engineering.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I never said otherwise.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> BUT bear in mind that H (as opposed to
>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted())
>>>>>>>>>>>>>>>> plays the role in all this of a Linz *Halt Decider*, and
>>>>>>>>>>>>>>>> so is
>>>>>>>>>>>>>>>> required to deliver its HD decision *HALT* or *NOT_HALT*.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> No, not at all. Not in the least little bit.
>>>>>>>>>>>>>>> This takes my solution of removing the pathological
>>>>>>>>>>>>>>> self-reference
>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>> the halting decision and tosses this solution in the trash.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Maybe, and that would be the right thing to do if your
>>>>>>>>>>>>>> solution is
>>>>>>>>>>>>>> wrong.  In any case, if you can't refute the Linz proof 
>>>>>>>>>>>>>> without
>>>>>>>>>>>>>> changing the meaning of "Halt Decider", then your solution is
>>>>>>>>>>>>>> wrong.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I am refuting that the Linz proof proves that the halting
>>>>>>>>>>>>> problem is
>>>>>>>>>>>>> undecidable by finding another way to define the halt decider
>>>>>>>>>>>>> that
>>>>>>>>>>>>> cannot be contradicted.
>>>>>>>>>>>>
>>>>>>>>>>>> The Linz halt decider corresponds to the correct (HP) 
>>>>>>>>>>>> definition
>>>>>>>>>>>> of a
>>>>>>>>>>>> halt decider.  If you change this definition you are not
>>>>>>>>>>>> discussing HP.
>>>>>>>>>>>
>>>>>>>>>>> As long as a halt decider cannot be shown to make this decision
>>>>>>>>>>> incorrectly for any of its inputs then the halting problem
>>>>>>>>>>> cannot be
>>>>>>>>>>> shown to be undecidable:
>>>>>>>>>>>
>>>>>>>>>>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
>>>>>>>>>>
>>>>>>>>>> The Linz proof shows HP to be undecidable.  Your refuting code
>>>>>>>>>> conforms with the Linz conclusion, and does not refute anything.
>>>>>>>>>
>>>>>>>>> Unless you can concretely show how this function would get the 
>>>>>>>>> wrong
>>>>>>>>> answer all of your rebuttal is ultimately totally vacuous:
>>>>>>>>>
>>>>>>>>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
>>>>>>>>>
>>>>>>>>
>>>>>>>> In your code, the function answers "non halting behaviour detected"
>>>>>>>> for input which actually halts, and so by any reasonable
>>>>>>>> definition of
>>>>>>>> the words, it has decided incorrectly.
>>>>>>>
>>>>>>> Bullshit. The actual question that it always correctly answers is:
>>>>>>> Does the input have to be aborted to prevent infinite execution?
>>>>>>
>>>>>> I provided the traces which back up what I said, so it's not 
>>>>>> bullshit.
>>>>>> You have snipped them because you don't want to look stupid, so I'm
>>>>>> going to restore them:
>>>>>>
>>>>>> H_Hat machine trace
>>>>>> -------------------
>>>>>>
>>>>>> H_Hat starts (main() calls H_Hat(H_Hat))
>>>>>>     H_Hat calls Was_Its_Execution_Aborted(H_Hat,H_Hat)
>>>>>>       Was_Its_Execution_Aborted emulates H_Hat(H_Hat)
>>>>>>       Was_Its_Execution_Aborted decides the emulated program ..
>>>>>>                  .. will never terminate if not aborted
>>>>>>       Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>>>>>     H_Hat *halts*
>>>>>>
>>>>>> OK, so the H_Hat calculation halts...
>>>>>
>>>>> In this case we have an outer instance of H_Hat() an inner instance of
>>>>> H_Hat(). The outer instance of H_Hat() is executed in the master UTM
>>>>> process context of x86utm.
>>>>>
>>>>> This outer instance of H_Hat() invokes
>>>>> Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) which
>>>>> creates the inner instance of H_Hat() in its own process context and
>>>>> executes it. It then returns true to the outer instance of H_Hat() 
>>>>> after
>>>>> aborting the inner instance.
>>>>
>>>> ..*and then terminates*
>>>>
>>>> The calculation H_Hat(H_Hat) halts.  So if
>>>> Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) says there
>>>> was "non-halting behaviour" it was wrong.
>>>>
>>>> No point in saying this over and over....
>>>>
>>>>
>>>>>
>>>>>> H machine trace
>>>>>>
>>>>>> ---------------
>>>>>> H starts (main() calls H(H_Hat,H_Hat))
>>>>>>     H calls Was_Its_Execution_Aborted(H_Hat,H_Hat)
>>>>>>       Was_Its_Execution_Aborted emulates H_Hat(H_Hat)
>>>>>>       Was_Its_Execution_Aborted decides the emulated program ..
>>>>>>                  .. will never terminate if not aborted
>>>>>>       Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>>>>>     H halts, with EAX=0 [= *NOT_HALT* decision]
>>>>>>
>>>>>
>>>>> In this case we have an instance of H() and an instance of H_Hat(). 
>>>>> The
>>>>>  instance of H() is executed in the master UTM process context of
>>>>> x86utm.
>>>>>
>>>>> H() invokes Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, 
>>>>> H_Hat)
>>>>> which creates the instance of H_Hat() and executes it. It then returns
>>>>> true to H() after aborting the instance of _H_Hat().
>>>>
>>>> Again, returning true to H is supposed to say it detected non-halting
>>>> behaviour, but the calculation it is examining actually halts.
>>>>
>>>> There, I said it again! :)  (last time, really...)
>>> Apparently this whole inner invocation of H_Hat() and outer invocation
>>> of H_Hat() is against your religion.
>>
>> Why do you say that?  I understand perfectly about outer and inner 
>> invocations of H_Hat().  I understand it better than you, because I 
>> lack your confusions on what's going on.
>>
>> Incidentally, I believe I've realised where you are going wrong in 
>> your thinking!  (If I'm right, it will come out in your answer to the 
>> question below...)
>>
>>> None-the-less an actual execution
>>> trace would show that the outer invocation does abort the inner
>>> invocation thus allowing the outer invocation to terminate normally.
>>
>> That's fine.
>>
>> If the outer invocation aborts the inner invocation, that implies that 
>> the H_Hat(H_Hat) calculation halts. 
> 

CORRECTION
> None of the invocations of H_Hat() would ever halt unless they are 
> aborted. 

In both cases the input H_Hat would not halt unless it has been aborted:
H_Hat(H_Hat)
H(H_Hat, H_Hat)


> That is why this is the correct halt decider question:
> bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)
> 
> When the return value of true is provided for the (M, N) input this 
> return value is correct. Every other return value from
> bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)
> does not occur because every other
> bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)
> has had its execution terminated before it ever returns any value.
> 
> Therefore we can conclude that
> bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)
> Is a halt decider function that cannot be shown to be incorrect.
> 
>> [When I say a calculation halts, I mean that there is a number n such 
>> that after n steps the calculation reaches a halt state.  It is 
>> nothing to do with anything being emulated, or run on some physical 
>> computer.]
>>
>> Do you agree with this?
>>
>> Mike.
> 
> 
> No. I pointed out the false assumptions.
> The one time that
> bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)
> returns its decision value this decision value is correct.
> There are no other times that it reteuns its decsion value.
> 
> 


-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24498 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction

FromMike Terry <news.dead.person.stones@darjeeling.plus.com>
Date2020-10-27 00:06 +0000
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction
Message-ID<Ke2dnaoWbqkW-QrCnZ2dnUU78bXNnZ2d@brightview.co.uk>
In reply to#24479
On 26/10/2020 18:14, olcott wrote:
> On 10/26/2020 1:03 PM, olcott wrote:
>> On 10/26/2020 11:29 AM, Mike Terry wrote:
>>> On 24/10/2020 23:08, olcott wrote:
>>>> On 10/24/2020 3:57 PM, Mike Terry wrote:
>>>>> On 24/10/2020 21:41, olcott wrote:
>>>>>> On 10/24/2020 2:44 PM, Mike Terry wrote:
>>>>>>> On 24/10/2020 20:05, olcott wrote:
>>>>>>>> On 10/24/2020 2:00 PM, Mike Terry wrote:
>>>>>>>>> On 24/10/2020 19:42, olcott wrote:
>>>>>>>>>> On 10/24/2020 1:32 PM, Mike Terry wrote:
>>>>>>>>>>> On 24/10/2020 18:49, olcott wrote:
>>>>>>>>>>>> On 10/24/2020 11:37 AM, Mike Terry wrote:
>>>>>>>>>>>>> On 24/10/2020 16:36, olcott wrote:
>>>>>>>>>>>>>> On 10/24/2020 9:38 AM, Mike Terry wrote:
>>>>>>>>>>>>>>> On 24/10/2020 07:03, olcott wrote:
>>>>>>>>>>>>>>>> On 10/23/2020 5:51 PM, Mike Terry wrote:
>>>>>>>>>>>>>>>>> On 23/10/2020 00:05, olcott wrote:
>>>>>>>>>>>>>>>>>> On 10/22/2020 5:14 PM, Mike Terry wrote:
>>>>>>>>>>>>>>>>>>> On 22/10/2020 17:38, olcott wrote:
>>>>>>>>>>>>>>>>>>>> On 10/22/2020 10:25 AM, Mike Terry wrote:
>>>>>>>>>>>>>>>>>>>>> On 22/10/2020 15:36, olcott wrote:
>>>>>>>>>>>>>>>>>>>>>> On 10/22/2020 7:00 AM, Richard Damon wrote:
>>>>>>>>>>>>>>>>>>>>>>> On 10/22/20 12:33 AM, olcott wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> The difference is that it is no longer possible for
>>>>>>>>>>>>>>>>>>>>>>>> H_Hat()
>>>>>>>>>>>>>>>>>>>>>>>> to do
>>>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>>>> opposite of what H() decides. This transforms an
>>>>>>>>>>>>>>>>>>>>>>>> undecidable
>>>>>>>>>>>>>>>>>>>>>>>> problem
>>>>>>>>>>>>>>>>>>>>>>>> into a decidable problem.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> If H_Hat no longer does what the proof defined, then
>>>>>>>>>>>>>>>>>>>>>>> your
>>>>>>>>>>>>>>>>>>>>>>> demonstration
>>>>>>>>>>>>>>>>>>>>>>> is no longer applicable to the proof.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> If the halt decider is to report whether or not its
>>>>>>>>>>>>>>>>>>>>>> input
>>>>>>>>>>>>>>>>>>>>>> halts
>>>>>>>>>>>>>>>>>>>>>> another
>>>>>>>>>>>>>>>>>>>>>> program can be constructed on the the basis of
>>>>>>>>>>>>>>>>>>>>>> this halt
>>>>>>>>>>>>>>>>>>>>>> decider
>>>>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>>>> does the opposite of whatever the halt decider
>>>>>>>>>>>>>>>>>>>>>> decides.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> This is how H() and H_Hat() are defined in the Linz
>>>>>>>>>>>>>>>>>>>>>> proof.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> If the halt decider is to report whether or not it
>>>>>>>>>>>>>>>>>>>>>> aborted its
>>>>>>>>>>>>>>>>>>>>>> input
>>>>>>>>>>>>>>>>>>>>>> program because its input program would otherwise
>>>>>>>>>>>>>>>>>>>>>> cause
>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>> halt
>>>>>>>>>>>>>>>>>>>>>> decider
>>>>>>>>>>>>>>>>>>>>>> to get stuck in infinite execution then this other
>>>>>>>>>>>>>>>>>>>>>> program
>>>>>>>>>>>>>>>>>>>>>> can no
>>>>>>>>>>>>>>>>>>>>>> longer
>>>>>>>>>>>>>>>>>>>>>> fool its halt decider and do the opposite of
>>>>>>>>>>>>>>>>>>>>>> whatever it
>>>>>>>>>>>>>>>>>>>>>> decides.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> If H() aborts the execution of H_Hat() then H_Hat()
>>>>>>>>>>>>>>>>>>>>>> cannot
>>>>>>>>>>>>>>>>>>>>>> continue to
>>>>>>>>>>>>>>>>>>>>>> execute because H() has complete control over H_Hat.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> The end result of this slight change is that the
>>>>>>>>>>>>>>>>>>>>>> halting
>>>>>>>>>>>>>>>>>>>>>> problem
>>>>>>>>>>>>>>>>>>>>>> can no
>>>>>>>>>>>>>>>>>>>>>> longer be shown to be undecidable.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> It is suspicious that in none of this have you ever
>>>>>>>>>>>>>>>>>>>>> stated
>>>>>>>>>>>>>>>>>>>>> what is
>>>>>>>>>>>>>>>>>>>>> actually wrong in the Linz proof.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> When the halting problem is defined as:
>>>>>>>>>>>>>>>>>>>> bool Does_It_Halt(u32 P, u32 I)
>>>>>>>>>>>>>>>>>>>> another program can be constructed on the basis of
>>>>>>>>>>>>>>>>>>>> Does_It_Halt()
>>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>> does the opposite of whatever Does_It_Halt() decides.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Yes, regardless of the internal details of
>>>>>>>>>>>>>>>>>>> Does_It_Halt().
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> When the halting problem is defined as:
>>>>>>>>>>>>>>>>>>>> bool Was_Its_Execution_Aborted(u32 P, u32 I)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> another program CANNOT be constructed on the basis of
>>>>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() that does the opposite of
>>>>>>>>>>>>>>>>>>>> whatever
>>>>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() decides.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Sure, if you interpret your question literally as asking
>>>>>>>>>>>>>>>>>>> whether P
>>>>>>>>>>>>>>>>>>> would actually be aborted if it executes under the UTM
>>>>>>>>>>>>>>>>>>> within
>>>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted()!
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> However, another program CAN be constructed on the
>>>>>>>>>>>>>>>>>>> basis of
>>>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted() that:
>>>>>>>>>>>>>>>>>>> -   halts if Was_Its_Execution_Aborted() decides
>>>>>>>>>>>>>>>>>>> "aborted"
>>>>>>>>>>>>>>>>>>> -   loops if Was_Its_Execution_Aborted() decides
>>>>>>>>>>>>>>>>>>> "halted"
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> (right?)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Wrong.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> No, right.  To avoid a silly pantomine argument, here
>>>>>>>>>>>>>>>>> is an
>>>>>>>>>>>>>>>>> example of
>>>>>>>>>>>>>>>>> such a function:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> int H_Hat(u32 M)
>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>     if (Was_Its_Execution_Aborted(M, M))
>>>>>>>>>>>>>>>>>     {
>>>>>>>>>>>>>>>>>       // Was_Its_Execution_Aborted says that M(M) was
>>>>>>>>>>>>>>>>> aborted
>>>>>>>>>>>>>>>>>       HALT;       // so we halt
>>>>>>>>>>>>>>>>>     }
>>>>>>>>>>>>>>>>>     else
>>>>>>>>>>>>>>>>>     {
>>>>>>>>>>>>>>>>>       // Was_Its_Execution_Aborted says that M(M) halted
>>>>>>>>>>>>>>>>>       HERE: goto HERE;   // so we loop
>>>>>>>>>>>>>>>>>     }
>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> and for completeness, here is the function being
>>>>>>>>>>>>>>>>> invoked from
>>>>>>>>>>>>>>>>> main():
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>     u32 M = (u32)H_Hat;
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>     H_Hat(M);       // run H_Hat with input H_Hat
>>>>>>>>>>>>>>>>>     HALT;
>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> You see, H_Hat /is/ constructed so that if
>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted(M, M) returns "aborted"
>>>>>>>>>>>>>>>>> (nonzero),
>>>>>>>>>>>>>>>>> H_Hat
>>>>>>>>>>>>>>>>> will halt, and if Was_Its_Execution_Aborted(M, M) returns
>>>>>>>>>>>>>>>>> "halted"
>>>>>>>>>>>>>>>>> (zero), H_Hat will loop.  Just like I said.  Thre is no
>>>>>>>>>>>>>>>>> subtle
>>>>>>>>>>>>>>>>> philosophical point here, just beginner knowledge of the C
>>>>>>>>>>>>>>>>> programming
>>>>>>>>>>>>>>>>> language.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> (To save you making a silly response, yes IF we were to
>>>>>>>>>>>>>>>>> run the
>>>>>>>>>>>>>>>>> program under a debugger or emulator of some kind, and we
>>>>>>>>>>>>>>>>> aborted the
>>>>>>>>>>>>>>>>> run at the "if (Abort)" statement or earlier, then of
>>>>>>>>>>>>>>>>> course we
>>>>>>>>>>>>>>>>> would
>>>>>>>>>>>>>>>>> not get to see what it actually does next.  (Duh.)  That's
>>>>>>>>>>>>>>>>> irrelevent
>>>>>>>>>>>>>>>>> because regardless of this, H_Hat as constructed meets the
>>>>>>>>>>>>>>>>> conditions
>>>>>>>>>>>>>>>>> just as I described.)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>  > There is no way to make the revised halting question
>>>>>>>>>>>>>>>>> contradictory.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> DebugTrace() either reports that it has aborted the
>>>>>>>>>>>>>>>>>> execution
>>>>>>>>>>>>>>>>>> of its
>>>>>>>>>>>>>>>>>> input or it reports that its input has not been aborted
>>>>>>>>>>>>>>>>>> after
>>>>>>>>>>>>>>>>>> its
>>>>>>>>>>>>>>>>>> input
>>>>>>>>>>>>>>>>>> has terminated.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>  > [A quick observation: you've flipped to talking about
>>>>>>>>>>>>>>>>> DebugTrace()
>>>>>>>>>>>>>>>>> rather than Was_Its_Execution_Aborted() which we were
>>>>>>>>>>>>>>>>> discussing.
>>>>>>>>>>>>>>>>> I'll just take it they're the same thing, and continue
>>>>>>>>>>>>>>>>> saying
>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted().]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> OK good. I like that. Make the function say what it really
>>>>>>>>>>>>>>>> means.
>>>>>>>>>>>>>>>> That is good software engineering.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I never said otherwise.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> BUT bear in mind that H (as opposed to
>>>>>>>>>>>>>>>>> Was_Its_Execution_Aborted())
>>>>>>>>>>>>>>>>> plays the role in all this of a Linz *Halt Decider*, and
>>>>>>>>>>>>>>>>> so is
>>>>>>>>>>>>>>>>> required to deliver its HD decision *HALT* or *NOT_HALT*.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> No, not at all. Not in the least little bit.
>>>>>>>>>>>>>>>> This takes my solution of removing the pathological
>>>>>>>>>>>>>>>> self-reference
>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>> the halting decision and tosses this solution in the trash.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Maybe, and that would be the right thing to do if your
>>>>>>>>>>>>>>> solution is
>>>>>>>>>>>>>>> wrong.  In any case, if you can't refute the Linz proof
>>>>>>>>>>>>>>> without
>>>>>>>>>>>>>>> changing the meaning of "Halt Decider", then your
>>>>>>>>>>>>>>> solution is
>>>>>>>>>>>>>>> wrong.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I am refuting that the Linz proof proves that the halting
>>>>>>>>>>>>>> problem is
>>>>>>>>>>>>>> undecidable by finding another way to define the halt decider
>>>>>>>>>>>>>> that
>>>>>>>>>>>>>> cannot be contradicted.
>>>>>>>>>>>>>
>>>>>>>>>>>>> The Linz halt decider corresponds to the correct (HP)
>>>>>>>>>>>>> definition
>>>>>>>>>>>>> of a
>>>>>>>>>>>>> halt decider.  If you change this definition you are not
>>>>>>>>>>>>> discussing HP.
>>>>>>>>>>>>
>>>>>>>>>>>> As long as a halt decider cannot be shown to make this decision
>>>>>>>>>>>> incorrectly for any of its inputs then the halting problem
>>>>>>>>>>>> cannot be
>>>>>>>>>>>> shown to be undecidable:
>>>>>>>>>>>>
>>>>>>>>>>>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P,
>>>>>>>>>>>> u32 I)
>>>>>>>>>>>
>>>>>>>>>>> The Linz proof shows HP to be undecidable.  Your refuting code
>>>>>>>>>>> conforms with the Linz conclusion, and does not refute anything.
>>>>>>>>>>
>>>>>>>>>> Unless you can concretely show how this function would get the
>>>>>>>>>> wrong
>>>>>>>>>> answer all of your rebuttal is ultimately totally vacuous:
>>>>>>>>>>
>>>>>>>>>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> In your code, the function answers "non halting behaviour
>>>>>>>>> detected"
>>>>>>>>> for input which actually halts, and so by any reasonable
>>>>>>>>> definition of
>>>>>>>>> the words, it has decided incorrectly.
>>>>>>>>
>>>>>>>> Bullshit. The actual question that it always correctly answers is:
>>>>>>>> Does the input have to be aborted to prevent infinite execution?
>>>>>>>
>>>>>>> I provided the traces which back up what I said, so it's not
>>>>>>> bullshit.
>>>>>>> You have snipped them because you don't want to look stupid, so I'm
>>>>>>> going to restore them:
>>>>>>>
>>>>>>> H_Hat machine trace
>>>>>>> -------------------
>>>>>>>
>>>>>>> H_Hat starts (main() calls H_Hat(H_Hat))
>>>>>>>     H_Hat calls Was_Its_Execution_Aborted(H_Hat,H_Hat)
>>>>>>>       Was_Its_Execution_Aborted emulates H_Hat(H_Hat)
>>>>>>>       Was_Its_Execution_Aborted decides the emulated program ..
>>>>>>>                  .. will never terminate if not aborted
>>>>>>>       Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>>>>>>     H_Hat *halts*
>>>>>>>
>>>>>>> OK, so the H_Hat calculation halts...
>>>>>>
>>>>>> In this case we have an outer instance of H_Hat() an inner
>>>>>> instance of
>>>>>> H_Hat(). The outer instance of H_Hat() is executed in the master UTM
>>>>>> process context of x86utm.
>>>>>>
>>>>>> This outer instance of H_Hat() invokes
>>>>>> Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) which
>>>>>> creates the inner instance of H_Hat() in its own process context and
>>>>>> executes it. It then returns true to the outer instance of H_Hat()
>>>>>> after
>>>>>> aborting the inner instance.
>>>>>
>>>>> ..*and then terminates*
>>>>>
>>>>> The calculation H_Hat(H_Hat) halts.  So if
>>>>> Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) says there
>>>>> was "non-halting behaviour" it was wrong.
>>>>>
>>>>> No point in saying this over and over....
>>>>>
>>>>>
>>>>>>
>>>>>>> H machine trace
>>>>>>>
>>>>>>> ---------------
>>>>>>> H starts (main() calls H(H_Hat,H_Hat))
>>>>>>>     H calls Was_Its_Execution_Aborted(H_Hat,H_Hat)
>>>>>>>       Was_Its_Execution_Aborted emulates H_Hat(H_Hat)
>>>>>>>       Was_Its_Execution_Aborted decides the emulated program ..
>>>>>>>                  .. will never terminate if not aborted
>>>>>>>       Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>>>>>>     H halts, with EAX=0 [= *NOT_HALT* decision]
>>>>>>>
>>>>>>
>>>>>> In this case we have an instance of H() and an instance of
>>>>>> H_Hat(). The
>>>>>>  instance of H() is executed in the master UTM process context of
>>>>>> x86utm.
>>>>>>
>>>>>> H() invokes Aborted_Because_Non_Halting_Behavior_Detected(H_Hat,
>>>>>> H_Hat)
>>>>>> which creates the instance of H_Hat() and executes it. It then
>>>>>> returns
>>>>>> true to H() after aborting the instance of _H_Hat().
>>>>>
>>>>> Again, returning true to H is supposed to say it detected non-halting
>>>>> behaviour, but the calculation it is examining actually halts.
>>>>>
>>>>> There, I said it again! :)  (last time, really...)
>>>> Apparently this whole inner invocation of H_Hat() and outer invocation
>>>> of H_Hat() is against your religion.
>>>
>>> Why do you say that?  I understand perfectly about outer and inner
>>> invocations of H_Hat().  I understand it better than you, because I
>>> lack your confusions on what's going on.
>>>
>>> Incidentally, I believe I've realised where you are going wrong in
>>> your thinking!  (If I'm right, it will come out in your answer to the
>>> question below...)
>>>
>>>> None-the-less an actual execution
>>>> trace would show that the outer invocation does abort the inner
>>>> invocation thus allowing the outer invocation to terminate normally.
>>>
>>> That's fine.
>>>
>>> If the outer invocation aborts the inner invocation, that implies
>>> that the H_Hat(H_Hat) calculation halts.
>>
>
> CORRECTION
>> None of the invocations of H_Hat() would ever halt unless they are
>> aborted.
>
> In both cases the input H_Hat would not halt unless it has been aborted:
> H_Hat(H_Hat)
> H(H_Hat, H_Hat)
>

Talking about what /would/ happen if xxxxx is confusing the discussion, 
I think.

By now you must know for your ACTUAL FINAL coded H and H_Hat:  Does the 
calculation H_Hat(H_Hat) halt?

I'm not talking about what its internal 
Aborted_Because_Non_Halting_Behavior_Detected(M, N) routine does, or 
what happens in any internal emulations of anything.

>
>> That is why this is the correct halt decider question:
>> bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)

It is only the correct halt decider question if it actually relates to 
the halting of calculation (M,N).  Otherwise it is not a halt decider, 
it's a "Internal routine aborted something" decider.

Mike.

>>
>> When the return value of true is provided for the (M, N) input this
>> return value is correct. Every other return value from
>> bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)
>> does not occur because every other
>> bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)
>> has had its execution terminated before it ever returns any value.
>>
>> Therefore we can conclude that
>> bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)
>> Is a halt decider function that cannot be shown to be incorrect.
>>
>>> [When I say a calculation halts, I mean that there is a number n such
>>> that after n steps the calculation reaches a halt state.  It is
>>> nothing to do with anything being emulated, or run on some physical
>>> computer.]
>>>
>>> Do you agree with this?
>>>
>>> Mike.
>>
>>
>> No. I pointed out the false assumptions.
>> The one time that
>> bool Aborted_Because_Non_Halting_Behavior_Detected(M, N)
>> returns its decision value this decision value is correct.
>> There are no other times that it reteuns its decsion value.
>>
>>
>
>

[toc] | [prev] | [next] | [standalone]


#24499 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2020-10-26 17:16 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction
Message-ID<878sbsv7zo.fsf@nosuchdomain.example.com>
In reply to#24498
Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes:
[SNIP]

Mike, and everyone else, please drop the comp.lang.* newsgroups when
you post a followup to one of olcott's articles.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips Healthcare
void Void(void) { Void(); } /* The recursive call of the void */

[toc] | [prev] | [next] | [standalone]


#24501 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction

FromMike Terry <news.dead.person.stones@darjeeling.plus.com>
Date2020-10-27 00:46 +0000
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction
Message-ID<KdadnckAyf948ArCnZ2dnUU78eudnZ2d@brightview.co.uk>
In reply to#24499
On 27/10/2020 00:16, Keith Thompson wrote:
> Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes:
> [SNIP]
>
> Mike, and everyone else, please drop the comp.lang.* newsgroups when
> you post a followup to one of olcott's articles.
>

I try to do that, and mostly I think I succeed, but of course sometimes 
I just forget.

[toc] | [prev] | [next] | [standalone]


Page 20 of 25 — ← Prev page 1 … 18 19 [20] 21 22 … 25  Next page →

Back to top | Article view | comp.theory


csiph-web