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 18 of 25 — ← Prev page 1 … 16 17 [18] 19 20 … 25  Next page →


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

FromBen Bacarisse <ben.usenet@bsb.me.uk>
Date2020-10-27 00:51 +0000
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<87imaw1ofe.fsf@bsb.me.uk>
In reply to#24471
Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:

> What PO has actually done is put the set eax 0 into H_Hat. Then he's accepted
> an amended H_Hat with this line removed. Of course that blows up the entire 
> scheme. But we can now wait for H_Hat to return (at the machine level) and
> say "eax = 0 so it was aborted" (at the logical level).

I don't think that's what PO was doing, but to be frank, I don't care.
This side discussion on how to make something fundamentally wrong
slightly more deceptive is sapping my will to live.

-- 
Ben.

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-26 11:16 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<4_6dnUS5eqfYawvCnZ2dnUU7-YvNnZ2d@giganews.com>
In reply to#24453
On 10/26/2020 4:37 AM, Malcolm McLean wrote:
> On Monday, 26 October 2020 at 03:56:48 UTC, Ben Bacarisse wrote:
>> Mike Terry <news.dead.p...@darjeeling.plus.com> writes:
>>
> 
>>> Then he abstracted the common decider logic out of H(), calling it
>>> DebugTrace() so that it could be called from his H() and H_Hat() which
>>> also mostly makes sense, and his code for H() and H_Hat() also made
>>> sense. It is obvious that this code actually conforms with what LINZ
>>> proof suggests.
>> That's fine, but there no reason not to be more explicit about the Linz
>> correspondence, and he could get rid of the ghastly setting eax
>> nonsense. At first, I thought that would be the back door he would use
>> to cheat on the separation of H and H_Hat, but no. It's just a clunky
>> interface.
>>
> He's not been consistent. In the original post, eax 0 means "aborted", and
> you ran H and eax was 0, so "aborted", and you ran H_Hat and eax was 0, so
> "aborted", and we change the question from "did it halt?" to "was it aborted?"
> 
> But later on, that seems to have changed. I suspect because of confusion
> about whether you abort yourself or not.
> 
> It's a root a very simple point. But it has generated a huge thread.
> 
Here is how my code has been augmented based on feedback from
10/26/2020 9:44 AM, Melzzzzz:


void H_Hat(u32 M)
{
   if (Aborted_Because_Non_Halting_Behavior_Detected(M, M))
     Output("The function at this machine address has been aborted:", M);
   else
   {
     Output("The function at this machine address has terminated:", M);
     HERE: goto HERE;
   }
   HALT
}


void H(u32 M, u32 N)
{
   if (Aborted_Because_Non_Halting_Behavior_Detected(M, M))
     Output("The function at this machine address has been aborted:", M);
   else
     Output("The function at this machine address has terminated:", M);
   HALT
}


int main()
{
   u32 M = (u32)H_Hat;
   H_Hat(M);
   HALT
}


I recap everything here:

This thread starts with a simple overview of exactly how the redefined 
the halt decider so that it cannot be fooled by the conventional halting 
problem trick.

On 10/25/2020 8:33 PM, olcott wrote:
Making the Halting Problem Decidable
[ Includes deciding the Peter Linz proof counter-example ]

It goes on to explain all of the details of exactly how halting is 
decided for the the Peter Linz H_Hat() counter example.


-- 
Copyright 2020 Pete Olcott

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


#24460 — 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 15:41 +0000
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<p8CdnUVZtYCgcwvCnZ2dnUU78c_NnZ2d@brightview.co.uk>
In reply to#24448
On 26/10/2020 03:56, Ben Bacarisse wrote:
> Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes:
>
>> On 26/10/2020 01:17, Ben Bacarisse wrote:
>>> Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:
>>>
>>>> On Sunday, 25 October 2020 at 22:54:30 UTC, Ben Bacarisse wrote:
>>>>> Malcolm McLean <malcolm.ar...@gmail.com> writes:
>>>>>
>>>>>> On Sunday, 25 October 2020 at 14:43:14 UTC, Ben Bacarisse wrote:
>>>>>>> Malcolm McLean <malcolm.ar...@gmail.com> writes:
>>>>>>>
>>>>>>>> On Sunday, 25 October 2020 at 03:33:13 UTC, Ben Bacarisse wrote:
>>>>>>>>> Malcolm McLean <malcolm.ar...@gmail.com> writes:
>>>>>>>>
>>>>>>>>>> "Abort is" exactly equivlalent to smashing the computer.
>>>>>>>>> OK. So you want to limit your (and PO's) arguments to physical things
>>>>>>>>> that can be smashed? If that not literal, how much of the smashing
>>>>>>>>> metaphor is needed for the things you want limit the discussion to?
>>>>>>>>>
>>>>>>>> The mistake you are making is that if H aborts, you can somehow capture that
>>>>>>>> and suppress or invert it. Then its not an abort.
>>>>>>> I'm not missing that, but if H aborts it does not decide anything. The
>>>>>>> mistake I was making was to assume you meant something less obviously
>>>>>>> wrong -- maybe even something related to what PO was saying. In PO's
>>>>>>> writing, when the call to DebugTrace in H aborts the simulation, it
>>>>>>> still returns a value to H. If it "smashed the machine" it couldn't do
>>>>>>> that.
>>>>>>>
>>>>>> Yes, in PO's original example, H and DebugTrace (as it was then) are decoupled.
>>>>>> H_Hat doesn't call / incorporate H, it calls DebugTrace. However then H_Hat
>>>>>> writes 0 to eax. This means "non-halting behaviour detected, program aborted".
>>>>>> It doesn't matter that H_Hat then physically continues execution and halts.
>>>>>> Caller (main) picks up eax 0 and knows there's been an abortion somewhere
>>>>>> down the chain.
>>>>> I can't make this out.
>>>>>> Remember PO was very clear that he had changed the question from "does it
>>>>>> halt / not halt?" to "was it aborted?".
>>>>> I missed that. Did you tell him he had scuppered his own claim by doing
>>>>> that?
>>>>>
>>>> olcott (from a while back)
>>>> Yes I believe that is true.
>>>> The key to this is noticing that the halting question has been changed:
>>>> (a) Does H_Hat() halt on its input?
>>>>
>>>> (b) Does the execution of H_Hat() have to be aborted to prevent the halt
>>>> decider from getting stuck in infinite execution?
>>>
>>> Sorry, I must duck out of this.  I can't follow what you are saying.
>>>
>>
>> For me, the whole thread has become impossible to follow.
>
> Yes.  And the cross posting has brought in people who have not seen any
> history so he's having to restate everytihng.
>>
>> PO started (I thought) by talking of his original claim of refuting HP
>> proof by providing his specific H, H^ which followed the requirements
>> of a halt decider [must terminate in one of two states, e.g. HALT,
>> NONHALT] with the property that H correctly decides halting for the
>> case of H^ running with input H^.  (No claim of H correctly deciding
>> anything else, but I know you know all about that.)
>>
>> Then he abstracted the common decider logic out of H(), calling it
>> DebugTrace() so that it could be called from his H() and H_Hat() which
>> also mostly makes sense, and his code for H() and H_Hat() also made
>> sense.  It is obvious that this code actually conforms with what LINZ
>> proof suggests.
>
> That's fine, but there no reason not to be more explicit about the Linz
> correspondence, and he could get rid of the ghastly setting eax
> nonsense.  At first, I thought that would be the back door he would use
> to cheat on the separation of H and H_Hat, but no.  It's just a clunky
> interface.
>
> It could be more explicit and cleaner:
>
> typedef uintptr_t data;
> typedef uintptr_t function;
>
> bool H(function p, data i)
> {
>      return decide_something_like_halting(p, i);
> }
>
> void H_Hat(function p)
> {
>      if (H(p, (data)p))
>           while (1);
> }
>
> int main(void)
> {
>      return H((function)H_Hat, (data)H_Hat) ? EXIT_SUCCESS : EXIT_FAILURE;
> }

Yes, I would also have gone for a variation of "all decisions are 
returned as return codes from functions.  PO's code is slightly messy 
because of his x86utm design decisions.  I think the main thing is the 
main function, hehe.  His x86utm does not cater for returning from 
main(), so he needs the HALT instruction, but then he needs a rather 
clunky convention for returning different results.

>
> But maybe this makes the impossibility of the claim too obvious?

I don't think so.  I could say that nothing is too obvious for PO, but 
that would be a little rude!  A better way of saying it is that his own 
code makes the impossibility only very slightly less obvious than your 
code, so this isn't PO's problem.  It's not that he doesn't see that the 
structure makes the "actually halts" decision impossible - his problem 
is that he thinks that doesn't matter due to some incoherent argument 
regarding his "change the question" proposal.  That proposal (whatever 
it means) wouldn't affected by switching to cleaner code.

>
>> It's never been clear to me what he actually means by changing the
>> question, or exactly what his new "question" actually is, or its
>> role. E.g. is it just that the meaning of the RC from DebugTrace() has
>> changed, or is it the meaning of the halt states of the halt decider,
>> or both?
>
> I tried to ask about when the new "question" differs from "halts?" but
> answering that would give too much away I think.
>

Yes I noticed that.  I've decided to try to get this clarified by 
responding to his "challenge", in my Mon, 26 Oct 2020 03:57:18 +0000 
post.  I will just keep asking until either the meaning of his new 
question is clear, or it becomes clear there really is no meaning that 
PO can explain.

>> Just about everybody (including you now, I see) has pointed out that
>> changing the meaning of the halt decider states means he is not
>> actually talking about HP/Linz halt deciders any more, and so there
>> would no longer be any relevence to the HP proof any more.  Also, when
>> I suggested an example with a DebugTrace() correctly answering his new
>> question, but which wasn't answering the question about whether its
>> input /actually/ halted or ran forever, he dismissed it sarcastically,
>> saying "An example which isn't actually a halt decider refutes
>> nothing". So that suggests he is not changing the meaning of the HD
>> halt states, ... except loads of other things make me think he is
>> changing that.
>
> There's a lot of equivocating going on.
>
>> (What's clear is that none of this has actually refuted anything, and
>> in fact I'm rather disappointed that his code fails so unsubtly - I
>> expected at least his H halt state /would/ match with /his own/
>> H_Hat's halt/non-halting property, with the actual problem being
>> elsewhere.)
>
> Yes, I am a little disappointed too.  I thought there'd be some attempt
> at foul play at least.  The eax nonsense seemed like a plausible
> backdoor, but that was when I thought we'd be presented with thousands
> of lines of code and just a trace showing "correct" behaviour.  It would
> not be hard to hide some linkage in a huge program, but there is nothing
> sneaky going on in these dozen lines.  He's just wrong.
>

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


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

FromBen Bacarisse <ben.usenet@bsb.me.uk>
Date2020-10-26 17:28 +0000
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<875z6w3nhn.fsf@bsb.me.uk>
In reply to#24460
Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes:

> On 26/10/2020 03:56, Ben Bacarisse wrote:
>> Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes:
<cut>
>>> It's never been clear to me what he actually means by changing the
>>> question, or exactly what his new "question" actually is, or its
>>> role. E.g. is it just that the meaning of the RC from DebugTrace() has
>>> changed, or is it the meaning of the halt states of the halt decider,
>>> or both?
>>
>> I tried to ask about when the new "question" differs from "halts?" but
>> answering that would give too much away I think.
>>
>
> Yes I noticed that.  I've decided to try to get this clarified by
> responding to his "challenge", in my Mon, 26 Oct 2020 03:57:18 +0000
> post.  I will just keep asking until either the meaning of his new
> question is clear, or it becomes clear there really is no meaning that
> PO can explain.

I think plugging away at one question is the way to go.  After about a
dozen evasions, he sometimes feels he has to reply.  Good luck with
that.

-- 
Ben.

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-23 19:52 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<L7idneYS_dAv5w7CnZ2dnUU7-IHNnZ2d@giganews.com>
In reply to#24281
On 10/23/2020 7:24 PM, Malcolm McLean wrote:
> On Saturday, 24 October 2020 at 01:14:01 UTC+1, olcott wrote:
>> On 10/23/2020 6:58 PM, Malcolm McLean wrote:
>>>
>>> But the when H_Hat is called directly, the outermost H_Hat terminates normally?
>>> Or is it aborted?
>>>
>> The outermost H_Hat() terminates normally because the inner one was
>> aborted.
>>
> OK, that's crucial. If H_Hat terminates normally when invoked directly, then
> H() has to return "Not aborted". But that's impossible. There's an infinite
> recursion of DebugTraces.

The key thing that everyone has disavowed that really does make a huge 
difference is the placement order in the process tree. The difference 
now is that I have a whole operating system to back me up.

> So you've got a choice. You can keep H_Hat as a Turing machine, and say
> Linz hasn;t been refuted. Or you can make a tiny change to H_Hat so that
> it is no longer a Turing machine.  Then H() and H_Hat() will give consistent
> results.

Not, not at all, not in the least little bit. My whole x86utm operating 
system was designed to model UTM's executing other UTM's. The outermost 
DebugTrace() can see the infinite recursion of H_Hat() sooner that the 
next inner DebugTrace() can see this because it has already seen more 
execution steps / state transitions.

The outer DebugTrace() has identical code to the Inner DebugTrace() but 
because it has more data the decision that it makes with this additional 
data is not the same decision that its inner process would make with 
less data.

>>
>> // M has address of H_Hat()
>> void H_Hat(u32 M)
>> {
>> if (DebugTrace(M, M)) // M(M) Aborted?
>> MOV_EAX_0 // Execution of M(N) has been aborted
>>
> So what is this doing if H_Hat hasn't aborted?
>>
>> else
>> {
>> MOV_EAX_1 // M(N) has halted
>> HERE: goto HERE;
>> }
>> HALT
>> }
>>


-- 
Copyright 2020 Pete Olcott

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


#24280 — 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-24 01:21 +0100
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<HtCdndtmeNzj7g7CnZ2dnUU78KmdnZ2d@brightview.co.uk>
In reply to#24272
On 24/10/2020 00:54, olcott wrote:
> On 10/23/2020 6:39 PM, Malcolm McLean wrote:
>> On Saturday, 24 October 2020 at 00:32:07 UTC+1, olcott wrote:
>>> On 10/23/2020 6:17 PM, Mike Terry wrote:
>>>> On 24/10/2020 00:03, Malcolm McLean wrote:
>>>>> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
>>>>>>
>>>>>> 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))
>>>>>> {
>>>>> // Machine no longer exists. Control flow can't get to this point.
>>>>>> // Was_Its_Execution_Aborted says that M(M) was aborted
>>>>>> HALT; // so we halt
>>>>>> }
>>>>>
>>>>> That's the step you are missing. At least this is what I
>>>>> understand. PO
>>>>> sems to be changing his argument slightly and I don't want to speak
>>>>> for
>>>>> him.
>>>>>
>>>>
>>>> No, this is you not undertanding the whole emulation thing that's going
>>>> on. If you'd read on you'd have seen a quite thorough explanation of
>>>> the flow of control that's involved.
>>>>
>>>> If you read the rest of my post and are still unclear, post back and
>>>> I'll try to explain better - but really it's all in my earlier post.
>>>> Check out the "stack trace" (sort-of) of the two machines H and H_Hat
>>>> running.
>>>>
>>>> Mike.
>>> The outermost H_Hat() has its process terminated before:
>>> if (Was_Its_Execution_Aborted(M, M)) returns a value to H_Hat().
>>>
>>> This is because the DebugTrace() that H() invoked that created the
>>> process that H_Hat() resides in is a few steps ahead of what the inner
>>> DebugStep() invoked by H_Hat() can see.
>>>
>> You're going to have to clarify.
>> If H is called, DebugTrace emulates the outer instance of H_Hat, and can
>> abort the emulation without aborting itself.
>
> As soon as DebugTrace() returns a value all of its local stack memory is
> freed and the process that it created only existed in this local stack
> memory.
>
>> If H_Hat is called directly, and not through H, does the outer
>> instance of
>> H_Hat abort, or does it terminate normally?
>
> Whether or not H() or H_Hat() is the outermost process that invokes the
> outermost DebugTrace() in either case this outermost DebugTrace() aborts
> the inner H_Hat() before the inner DebugTrace() returns a value to it.

Malcolm didn't ask what happens to the /inner/ (emulated) H_Hat.  That 
obviously goes away.  He asks what happens to the /outer/ H_Hat that 
first called DebugTrace().

Mike.

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


#24275 — 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-24 01:06 +0100
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<L9CdnaNsrdpk8g7CnZ2dnUU78Y3NnZ2d@brightview.co.uk>
In reply to#24263
On 24/10/2020 00:31, olcott wrote:
> On 10/23/2020 6:17 PM, Mike Terry wrote:
>> On 24/10/2020 00:03, Malcolm McLean wrote:
>>> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
>>>>
>>>> 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))
>>>> {
>>> // Machine no longer exists. Control flow can't get to this point.
>>>> // Was_Its_Execution_Aborted says that M(M) was aborted
>>>> HALT; // so we halt
>>>> }
>>>
>>> That's the step you are missing. At least this is what I understand. PO
>>> sems to be changing his argument slightly and I don't want to speak for
>>> him.
>>>
>>
>> No, this is you not undertanding the whole emulation thing that's
>> going on.  If you'd read on you'd have seen a quite thorough
>> explanation of the flow of control that's involved.
>>
>> If you read the rest of my post and are still unclear, post back and
>> I'll try to explain better - but really it's all in my earlier post.
>> Check out the "stack trace" (sort-of) of the two machines H and H_Hat
>> running.
>>
>> Mike.
>
> The outermost H_Hat() has its process terminated before:
> if (Was_Its_Execution_Aborted(M, M)) returns a value to H_Hat().
>
> This is because the DebugTrace() that H() invoked that created the
> process that H_Hat() resides in is a few steps ahead of what the inner
> DebugStep() invoked by H_Hat() can see.
>

OK I can see you're not even going to read the rest of my post, so I'll 
cut and paste the stack traces of what the two machines H, H_Hat do when 
they run, adjusting a bit to remove my intermediate DeciderLogic() 
routine.  At least if you disagree with something you can point out 
where we are diverging!

The most relevent one for discussing what H_Hat does is the trace for 
H_Hat machine:

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 emulation is looping!!!
     Was_Its_Execution_Aborted stops emulating and returns ABORTED
   H_Hat does the opposite of HALT/NOT_HALT

So... which of these lines are correct/incorrect?


And for comparison here is what H does:

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 emulation is looping!!!
     Was_Its_Execution_Aborted stops emulating and returns ABORTED
   H_Hat halts indicating HALT/NOT_HALT decision based on rc..
               ..from Was_Its_Execution_Aborted()

While we're at it you might as well say which of these lines are 
correct/incorrect too.  :)

Regards,
Mike.

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-23 19:39 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<hvSdnU9OmoJf6g7CnZ2dnUU7-UXNnZ2d@giganews.com>
In reply to#24275
On 10/23/2020 7:06 PM, Mike Terry wrote:
> On 24/10/2020 00:31, olcott wrote:
>> On 10/23/2020 6:17 PM, Mike Terry wrote:
>>> On 24/10/2020 00:03, Malcolm McLean wrote:
>>>> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
>>>>>
>>>>> 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))
>>>>> {
>>>> // Machine no longer exists. Control flow can't get to this point.
>>>>> // Was_Its_Execution_Aborted says that M(M) was aborted
>>>>> HALT; // so we halt
>>>>> }
>>>>
>>>> That's the step you are missing. At least this is what I understand. PO
>>>> sems to be changing his argument slightly and I don't want to speak for
>>>> him.
>>>>
>>>
>>> No, this is you not undertanding the whole emulation thing that's
>>> going on.  If you'd read on you'd have seen a quite thorough
>>> explanation of the flow of control that's involved.
>>>
>>> If you read the rest of my post and are still unclear, post back and
>>> I'll try to explain better - but really it's all in my earlier post.
>>> Check out the "stack trace" (sort-of) of the two machines H and H_Hat
>>> running.
>>>
>>> Mike.
>>
>> The outermost H_Hat() has its process terminated before:
>> if (Was_Its_Execution_Aborted(M, M)) returns a value to H_Hat().
>>
>> This is because the DebugTrace() that H() invoked that created the
>> process that H_Hat() resides in is a few steps ahead of what the inner
>> DebugStep() invoked by H_Hat() can see.
>>
> 
> OK I can see you're not even going to read the rest of my post, so I'll 
> cut and paste the stack traces of what the two machines H, H_Hat do when 
> they run, 


First of all all of these ideas equally apply to a UTM that executes 
another UTM in one state transition at-a-time mode, that executes other 
UTM's in an execution hierarchy.

The material is presented in C because presenting it using an adaptation 
of an existing Turing Machine Description language would be tedious 
beyond belief.  http://www.lns.mit.edu/~dsw/turing/turing.html
Who want to mow five acres of grass using only finger nail clippers?

main() H() and the first DebugTrace() run in a process with its own stack.

The first H_Hat() runs in a separate process with its own separate stack 
space. It invokes another different DebugTrace() that runs in its 
process with a separate stack space.

This second DebugTrace() created another separate process with its own 
separate stack space and executes a second instance of H_Hat().

Bottom line here is that when the outermost DebugTrace() terminates the 
outermost H_Hat() there is no stack unwinding that allows this outermost 
H_hat() to receive any return value from DebugTrace().

It is like the outermost H_Hat() executed exit(0);


> adjusting a bit to remove my intermediate DeciderLogic() 
> routine.  At least if you disagree with something you can point out 
> where we are diverging!
> 
> The most relevent one for discussing what H_Hat does is the trace for 
> H_Hat machine:
> 
> 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 emulation is looping!!!
>      Was_Its_Execution_Aborted stops emulating and returns ABORTED
>    H_Hat does the opposite of HALT/NOT_HALT
> 
> So... which of these lines are correct/incorrect?
> 
> 
> And for comparison here is what H does:
> 
> 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 emulation is looping!!!
>      Was_Its_Execution_Aborted stops emulating and returns ABORTED
>    H_Hat halts indicating HALT/NOT_HALT decision based on rc..
>                ..from Was_Its_Execution_Aborted()
> 
> While we're at it you might as well say which of these lines are 
> correct/incorrect too.  :)
> 
> Regards,
> Mike.
> 

You got the above wrong because you did not even bother to get the 
execution order correctly:

main() calls H() which calls DebugTrace() which creates a whole new 
process and invokes H_Hat() in this process


-- 
Copyright 2020 Pete Olcott

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


#24300 — 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-24 04:27 +0100
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<m8adnfzIYIewAg7CnZ2dnUU78d3NnZ2d@brightview.co.uk>
In reply to#24283
On 24/10/2020 01:39, olcott wrote:
> On 10/23/2020 7:06 PM, Mike Terry wrote:
>> On 24/10/2020 00:31, olcott wrote:
>>> On 10/23/2020 6:17 PM, Mike Terry wrote:
>>>> On 24/10/2020 00:03, Malcolm McLean wrote:
>>>>> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
>>>>>>
>>>>>> 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))
>>>>>> {
>>>>> // Machine no longer exists. Control flow can't get to this point.
>>>>>> // Was_Its_Execution_Aborted says that M(M) was aborted
>>>>>> HALT; // so we halt
>>>>>> }
>>>>>
>>>>> That's the step you are missing. At least this is what I
>>>>> understand. PO
>>>>> sems to be changing his argument slightly and I don't want to speak
>>>>> for
>>>>> him.
>>>>>
>>>>
>>>> No, this is you not undertanding the whole emulation thing that's
>>>> going on.  If you'd read on you'd have seen a quite thorough
>>>> explanation of the flow of control that's involved.
>>>>
>>>> If you read the rest of my post and are still unclear, post back and
>>>> I'll try to explain better - but really it's all in my earlier post.
>>>> Check out the "stack trace" (sort-of) of the two machines H and H_Hat
>>>> running.
>>>>
>>>> Mike.
>>>
>>> The outermost H_Hat() has its process terminated before:
>>> if (Was_Its_Execution_Aborted(M, M)) returns a value to H_Hat().
>>>
>>> This is because the DebugTrace() that H() invoked that created the
>>> process that H_Hat() resides in is a few steps ahead of what the inner
>>> DebugStep() invoked by H_Hat() can see.
>>>
>>
>> OK I can see you're not even going to read the rest of my post, so
>> I'll cut and paste the stack traces of what the two machines H, H_Hat
>> do when they run,
>
>
> First of all all of these ideas equally apply to a UTM that executes
> another UTM in one state transition at-a-time mode, that executes other
> UTM's in an execution hierarchy.
>
> The material is presented in C because presenting it using an adaptation
> of an existing Turing Machine Description language would be tedious
> beyond belief.  http://www.lns.mit.edu/~dsw/turing/turing.html
> Who want to mow five acres of grass using only finger nail clippers?
>
> main() H() and the first DebugTrace() run in a process with its own stack.
>
> The first H_Hat() runs in a separate process with its own separate stack
> space. It invokes another different DebugTrace() that runs in its
> process with a separate stack space.
>
> This second DebugTrace() created another separate process with its own
> separate stack space and executes a second instance of H_Hat().
>
> Bottom line here is that when the outermost DebugTrace() terminates the
> outermost H_Hat() there is no stack unwinding that allows this outermost
> H_hat() to receive any return value from DebugTrace().
>
> It is like the outermost H_Hat() executed exit(0);
>
>

What you are describing is what I have called the H run, or "what H 
does" below.  (The second of the traces.)

The first of the traces is for the "H_Hat machine", i.e. H_Hat is called 
directly from main().

I totally get that when DebugTrace() emulates the running of H_Hat, it 
will emulate a new "process" for that run of H_Hat.

>> adjusting a bit to remove my intermediate DeciderLogic() routine.  At
>> least if you disagree with something you can point out where we are
>> diverging!
>>
>> The most relevent one for discussing what H_Hat does is the trace for
>> H_Hat machine:
>>
>> 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 emulation is looping!!!
>>      Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>    H_Hat does the opposite of HALT/NOT_HALT
>>
>> So... which of these lines are correct/incorrect?
>>
>>
>> And for comparison here is what H does:
>>
>> 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 emulation is looping!!!
>>      Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>    H_Hat halts indicating HALT/NOT_HALT decision based on rc..
>>                ..from Was_Its_Execution_Aborted()
>>
>> While we're at it you might as well say which of these lines are
>> correct/incorrect too.  :)
>>
>> Regards,
>> Mike.
>>
>
> You got the above wrong because you did not even bother to get the
> execution order correctly:
>
> main() calls H() which calls DebugTrace() which creates a whole new
> process and invokes H_Hat() in this process
>

Yeah, you're describing the second "what H does" trace.  You're not even 
bothering to make an effort to properly examine what I wrote, so I don't 
see why I should be motivated to spend my time on any of this, but I'll 
have one more go at explaining what should have been perfectly obvious 
to you:

You said:

    main() calls H() ...

and I said:

    H starts (main() calls H(H_Hat,H_Hat))

Do you see how I /am/ in fact "getting the order right" so far?

Then you continued:

    ... which calls DebugTrace() ...

and my next line was:

    H calls Was_Its_Execution_Aborted(H_Hat,H_Hat)

ok, you say DebugTrace, I say Was_Its_Execution_Aborted() which is THE 
SAME THING.  It was *YOU* who suggested we should rename DebugTrace to 
Was_Its_Execution_Aborted() upthread somewhere, as part of "changing the 
question".  I thought it was all a bit dumb, but went along with it for 
you.  Do you want me to post my traces again, but saying DebugTrace 
instead of Was_Its_Execution_Aborted()?  My point would be that YOU 
SHOULD RECOGNISE THIS EQUIVALENCE WITHOUT ME NEEDING TO EXPLAIN IT TO 
YOU, AS YOU INVENTED THE DIFFERENT NAMES.

Assuming you can translate your own name change, do you see that I am 
/still/ getting the order right so far?

Then you continued:

    ... which creates a whole new process and invokes H_Hat() in this 
process ...

and my next line was:

    Was_Its_Execution_Aborted emulates H_Hat(H_Hat)

Well common sense should tell you this is saying the same as you. 
Emulating H_Hat(H_Hat) in your UTM architecture involves creating a new 
"virtual process" (or maybe a real OS one, it doesn't matter) and 
running H_Hat in that process.  In fact emulating in any architecture 
would be the same (new virtual process and so on.)

Do you see that I am /still/ getting the order right so far?

Um, that's everything you picked up on, and I /in fact/ got every one of 
those in the right order!

Note:

1)  I only trace what happens in the "native" machine level.  I know 
full well that the emulated H_Hat() in it's virtual process will do 
stuff that could be traced, but I am simply not concerned with that 
level of trace.  Pretend that I have set TRACELEVEL = OUTER, LOL.

With that in mind you might go back to my SECOND trace and see if it 
matches your understanding, and if not where it diverges.  (With the 
understanding that my Was_Its_Execution_Aborted() is the same as your 
DebugTrace(), etc.)

2)  As well as the second trace for H running natively, I also provided 
the first trace, which in similar fashion shows H_Hat running "natively".

You could take a look at that one and comment too.

And IF your position is that H_Hat never is run natively, you should say 
that rather than claiming my order is wrong because you are too lazy to 
look at the right trace.

Or if you just want me to go away, post another bunch of crap without 
bothering to actually try to achieve any mutual understanding - that's 
OK too.

Regards,
Mike.

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-23 22:40 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<c6ydndRlidvcPw7CnZ2dnUU7-X3NnZ2d@giganews.com>
In reply to#24300
On 10/23/2020 10:27 PM, Mike Terry wrote:
 > On 24/10/2020 01:39, olcott wrote:
 >> On 10/23/2020 7:06 PM, Mike Terry wrote:
 >>> On 24/10/2020 00:31, olcott wrote:
 >>>> On 10/23/2020 6:17 PM, Mike Terry wrote:
 >>>>> On 24/10/2020 00:03, Malcolm McLean wrote:
 >>>>>> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
 >>>>>>>
 >>>>>>> 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))
 >>>>>>> {
 >>>>>> // Machine no longer exists. Control flow can't get to this point.
 >>>>>>> // Was_Its_Execution_Aborted says that M(M) was aborted
 >>>>>>> HALT; // so we halt
 >>>>>>> }
 >>>>>>
 >>>>>> That's the step you are missing. At least this is what I
 >>>>>> understand. PO
 >>>>>> sems to be changing his argument slightly and I don't want to speak
 >>>>>> for
 >>>>>> him.
 >>>>>>
 >>>>>
 >>>>> No, this is you not undertanding the whole emulation thing that's
 >>>>> going on.  If you'd read on you'd have seen a quite thorough
 >>>>> explanation of the flow of control that's involved.
 >>>>>
 >>>>> If you read the rest of my post and are still unclear, post back and
 >>>>> I'll try to explain better - but really it's all in my earlier post.
 >>>>> Check out the "stack trace" (sort-of) of the two machines H and H_Hat
 >>>>> running.
 >>>>>
 >>>>> Mike.
 >>>>
 >>>> The outermost H_Hat() has its process terminated before:
 >>>> if (Was_Its_Execution_Aborted(M, M)) returns a value to H_Hat().
 >>>>
 >>>> This is because the DebugTrace() that H() invoked that created the
 >>>> process that H_Hat() resides in is a few steps ahead of what the inner
 >>>> DebugStep() invoked by H_Hat() can see.
 >>>>
 >>>
 >>> OK I can see you're not even going to read the rest of my post, so
 >>> I'll cut and paste the stack traces of what the two machines H, H_Hat
 >>> do when they run,
 >>
 >>
 >> First of all all of these ideas equally apply to a UTM that executes
 >> another UTM in one state transition at-a-time mode, that executes other
 >> UTM's in an execution hierarchy.
 >>
 >> The material is presented in C because presenting it using an adaptation
 >> of an existing Turing Machine Description language would be tedious
 >> beyond belief.  http://www.lns.mit.edu/~dsw/turing/turing.html
 >> Who want to mow five acres of grass using only finger nail clippers?
 >>
 >> main() H() and the first DebugTrace() run in a process with its own
 >> stack.
 >>
 >> The first H_Hat() runs in a separate process with its own separate stack
 >> space. It invokes another different DebugTrace() that runs in its
 >> process with a separate stack space.
 >>
 >> This second DebugTrace() created another separate process with its own
 >> separate stack space and executes a second instance of H_Hat().
 >>
 >> Bottom line here is that when the outermost DebugTrace() terminates the
 >> outermost H_Hat() there is no stack unwinding that allows this outermost
 >> H_hat() to receive any return value from DebugTrace().
 >>
 >> It is like the outermost H_Hat() executed exit(0);
 >>
 >>
 >
 > What you are describing is what I have called the H run, or "what H
 > does" below.  (The second of the traces.)
 >
 > The first of the traces is for the "H_Hat machine", i.e. H_Hat is called
 > directly from main().
 >
 > I totally get that when DebugTrace() emulates the running of H_Hat, it
 > will emulate a new "process" for that run of H_Hat.

When H_Hat(H_Hat) or H(H_Hat, H_Hat) is invoked they both invoke 
DebugTrace(H_Hat, H_Hat) which returns the same value because it has the 
same input.

 >>> adjusting a bit to remove my intermediate DeciderLogic() routine.  At
 >>> least if you disagree with something you can point out where we are
 >>> diverging!
 >>>
 >>> The most relevent one for discussing what H_Hat does is the trace for
 >>> H_Hat machine:
 >>>
 >>> 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 emulation is looping!!!
 >>>      Was_Its_Execution_Aborted stops emulating and returns ABORTED
 >>>    H_Hat does the opposite of HALT/NOT_HALT
 >>>
 >>> So... which of these lines are correct/incorrect?
 >>>
 >>>
 >>> And for comparison here is what H does:
 >>>
 >>> 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 emulation is looping!!!
 >>>      Was_Its_Execution_Aborted stops emulating and returns ABORTED
 >>>    H_Hat halts indicating HALT/NOT_HALT decision based on rc..
 >>>                ..from Was_Its_Execution_Aborted()
 >>>
 >>> While we're at it you might as well say which of these lines are
 >>> correct/incorrect too.  :)
 >>>
 >>> Regards,
 >>> Mike.
 >>>
 >>
 >> You got the above wrong because you did not even bother to get the
 >> execution order correctly:
 >>
 >> main() calls H() which calls DebugTrace() which creates a whole new
 >> process and invokes H_Hat() in this process
 >>
 >
 > Yeah, you're describing the second "what H does" trace.  You're not even
 > bothering to make an effort to properly examine what I wrote, so I don't
 > see why I should be motivated to spend my time on any of this, but I'll
 > have one more go at explaining what should have been perfectly obvious
 > to you:
 >
 > You said:
 >
 >     main() calls H() ...
 >
 > and I said:
 >
 >     H starts (main() calls H(H_Hat,H_Hat))
 >
 > Do you see how I /am/ in fact "getting the order right" so far?
Yes. I was mistaken about this earlier.

 >
 > Then you continued:
 >
 >     ... which calls DebugTrace() ...
 >
 > and my next line was:
 >
 >     H calls Was_Its_Execution_Aborted(H_Hat,H_Hat)
 >
Yes.

 > ok, you say DebugTrace, I say Was_Its_Execution_Aborted() which is THE
 > SAME THING.  It was *YOU* who suggested we should rename DebugTrace to
 > Was_Its_Execution_Aborted() upthread somewhere, as part of "changing the
 > question".  I thought it was all a bit dumb, but went along with it for
 > you.  Do you want me to post my traces again, but saying DebugTrace
 > instead of Was_Its_Execution_Aborted()?  My point would be that YOU
 > SHOULD RECOGNISE THIS EQUIVALENCE WITHOUT ME NEEDING TO EXPLAIN IT TO
 > YOU, AS YOU INVENTED THE DIFFERENT NAMES.
 >
Yes agreed.

 > Assuming you can translate your own name change, do you see that I am
 > /still/ getting the order right so far?
 >
Yes.

 > Then you continued:
 >
 >     ... which creates a whole new process and invokes H_Hat() in this
 > process ...
 >
Yes.

 > and my next line was:
 >
 >     Was_Its_Execution_Aborted emulates H_Hat(H_Hat)
 >
No. It always takes two params.

 > Well common sense should tell you this is saying the same as you.
 > Emulating H_Hat(H_Hat) in your UTM architecture involves creating a new
 > "virtual process" (or maybe a real OS one, it doesn't matter) and
 > running H_Hat in that process.  In fact emulating in any architecture
 > would be the same (new virtual process and so on.)
 >
Yes

 > Do you see that I am /still/ getting the order right so far?
 >
Yes. You have always been one of my best reviewers.

 > Um, that's everything you picked up on, and I /in fact/ got every one of
 > those in the right order!
 >
Yes except the two versus one param thing.

 > Note:
 >
 > 1)  I only trace what happens in the "native" machine level.  I know
 > full well that the emulated H_Hat() in it's virtual process will do
 > stuff that could be traced, but I am simply not concerned with that
 > level of trace.  Pretend that I have set TRACELEVEL = OUTER, LOL.
 >
 > With that in mind you might go back to my SECOND trace and see if it
 > matches your understanding, and if not where it diverges.  (With the
 > understanding that my Was_Its_Execution_Aborted() is the same as your
 > DebugTrace(), etc.)

Two params versus one and CRUCIALLY the second invocation of
Was_Its_Execution_Aborted() is terminated before it ever gets any chance 
to return a value. As soon as the invocation of H_Hat() by the outermost
Was_Its_Execution_Aborted() is terminated the whole process tree is 
terminated.

 > 2)  As well as the second trace for H running natively, I also provided
 > the first trace, which in similar fashion shows H_Hat running "natively".
 >
 > You could take a look at that one and comment too.
 >
 > And IF your position is that H_Hat never is run natively, you should say
 > that rather than claiming my order is wrong because you are too lazy to
 > look at the right trace.
 >
 > Or if you just want me to go away, post another bunch of crap without
 > bothering to actually try to achieve any mutual understanding - that's
 > OK too.
 >
 > Regards,
 > Mike.
 >

-- 
Copyright 2020 Pete Olcott

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-23 23:02 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<CZednRZSyfj0Og7CnZ2dnUU7-a3NnZ2d@giganews.com>
In reply to#24275
On 10/23/2020 7:06 PM, Mike Terry wrote:
> On 24/10/2020 00:31, olcott wrote:
>> On 10/23/2020 6:17 PM, Mike Terry wrote:
>>> On 24/10/2020 00:03, Malcolm McLean wrote:
>>>> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
>>>>>
>>>>> 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))
>>>>> {
>>>> // Machine no longer exists. Control flow can't get to this point.
>>>>> // Was_Its_Execution_Aborted says that M(M) was aborted
>>>>> HALT; // so we halt
>>>>> }
>>>>
>>>> That's the step you are missing. At least this is what I understand. PO
>>>> sems to be changing his argument slightly and I don't want to speak for
>>>> him.
>>>>
>>>
>>> No, this is you not undertanding the whole emulation thing that's
>>> going on.  If you'd read on you'd have seen a quite thorough
>>> explanation of the flow of control that's involved.
>>>
>>> If you read the rest of my post and are still unclear, post back and
>>> I'll try to explain better - but really it's all in my earlier post.
>>> Check out the "stack trace" (sort-of) of the two machines H and H_Hat
>>> running.
>>>
>>> Mike.
>>
>> The outermost H_Hat() has its process terminated before:
>> if (Was_Its_Execution_Aborted(M, M)) returns a value to H_Hat().
>>
>> This is because the DebugTrace() that H() invoked that created the
>> process that H_Hat() resides in is a few steps ahead of what the inner
>> DebugStep() invoked by H_Hat() can see.
>>
> 
> OK I can see you're not even going to read the rest of my post, so I'll 
> cut and paste the stack traces of what the two machines H, H_Hat do when 
> they run, adjusting a bit to remove my intermediate DeciderLogic() 
> routine.  At least if you disagree with something you can point out 
> where we are diverging!
> 
> The most relevent one for discussing what H_Hat does is the trace for 
> H_Hat machine:
> 
> 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 emulation is looping!!!

Infinitely recursive.

>      Was_Its_Execution_Aborted stops emulating and returns ABORTED
>    H_Hat does the opposite of HALT/NOT_HALT


No this step is incorrect as you can see by the following code.
In this case ABORTED = true causing the outermost H_Hat() to halt.

// M has address of H_Hat()
void H_Hat(u32 M)
{
   if (DebugTrace(M, M)) // M(M) Aborted?
     MOV_EAX_0  // Execution of M(N) has been aborted
   else
   {
     MOV_EAX_1  // M(N) has halted
     HERE: goto HERE;
   }
   HALT
}

It seems really really weird that H_Hat() decides that its input of 
H_Hat() will not halt and then it goes ahead and halts itself.

The reason for this is that the outermost halt decider has more 
information than the inner halt decider (more traced steps) so we are 
not getting two different results from the same function for the same 
input. The inputs are different.

Also the key discovery that I made in 2016 is the all of the 
conventional self-referential halting problem proof counter-examples are 
infinitely recursive so that none of them ever reach the undecidable 
state transitions.

This key insight necessitates that any halt decider based on a 
DebugStep() of its input must terminate this input or get stuck in 
infinite execution.

Although it may be possible for it to wait a fixed number of steps to 
see what its input does before terminating its input it cannot simply 
wait to see what its input would do. This results in infinite execution.

it is best that it terminates its input as soon as it definitely decides 
that its input must be terminated. This keeps things simple.

> So... which of these lines are correct/incorrect?
> 
> 
> And for comparison here is what H does:
> 
> 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 emulation is looping!!!

Infinitely recursive

>      Was_Its_Execution_Aborted stops emulating and returns ABORTED
>    H_Hat halts indicating HALT/NOT_HALT decision based on rc..
>                ..from Was_Its_Execution_Aborted()
> 
> While we're at it you might as well say which of these lines are 
> correct/incorrect too.  :)
> 
> Regards,
> Mike.
> 

These look like they are correct.

-- 
Copyright 2020 Pete Olcott

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


#24318 — 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-24 16:58 +0100
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<dLGdnXX1DY2y0gnCnZ2dnUU78QXNnZ2d@brightview.co.uk>
In reply to#24303
On 24/10/2020 05:02, olcott wrote:
> On 10/23/2020 7:06 PM, Mike Terry wrote:
>> On 24/10/2020 00:31, olcott wrote:
>>> On 10/23/2020 6:17 PM, Mike Terry wrote:
>>>> On 24/10/2020 00:03, Malcolm McLean wrote:
>>>>> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
>>>>>>
>>>>>> 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))
>>>>>> {
>>>>> // Machine no longer exists. Control flow can't get to this point.
>>>>>> // Was_Its_Execution_Aborted says that M(M) was aborted
>>>>>> HALT; // so we halt
>>>>>> }
>>>>>
>>>>> That's the step you are missing. At least this is what I
>>>>> understand. PO
>>>>> sems to be changing his argument slightly and I don't want to speak
>>>>> for
>>>>> him.
>>>>>
>>>>
>>>> No, this is you not undertanding the whole emulation thing that's
>>>> going on.  If you'd read on you'd have seen a quite thorough
>>>> explanation of the flow of control that's involved.
>>>>
>>>> If you read the rest of my post and are still unclear, post back and
>>>> I'll try to explain better - but really it's all in my earlier post.
>>>> Check out the "stack trace" (sort-of) of the two machines H and H_Hat
>>>> running.
>>>>
>>>> Mike.
>>>
>>> The outermost H_Hat() has its process terminated before:
>>> if (Was_Its_Execution_Aborted(M, M)) returns a value to H_Hat().
>>>
>>> This is because the DebugTrace() that H() invoked that created the
>>> process that H_Hat() resides in is a few steps ahead of what the inner
>>> DebugStep() invoked by H_Hat() can see.
>>>
>>
>> OK I can see you're not even going to read the rest of my post, so
>> I'll cut and paste the stack traces of what the two machines H, H_Hat
>> do when they run, adjusting a bit to remove my intermediate
>> DeciderLogic() routine.  At least if you disagree with something you
>> can point out where we are diverging!
>>
>> The most relevent one for discussing what H_Hat does is the trace for
>> H_Hat machine:
>>
>> 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 emulation is looping!!!
>
> Infinitely recursive.

What do you mean by that?  Are you agreeing or disagreeing with the 
line?  How should the line be corrected?

Does Was_Its_Execution_Aborted() decide the emulated H_Hat(H_Hat) is 
exhibiting infinite recursion)?  That is a form of "not halting", so we 
could make the line 100% correct by rewording it

I think maybe you just mean that Was_Its_Execution_Aborted() identifies 
the onset of infinited recursion in the program its emulating, and so 
decides it is going to abort the emulation - so your remark is just a 
comment.  Or at least we can get rid of this comment if I change my 
wording to

       Was_Its_Execution_Aborted decides the emulated program ..
                 .. will never terminate if not aborted

I.e. the problem(?) is just my use of the word "loop" rather than the 
more general "never terminate".

>
>>      Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>    H_Hat does the opposite of HALT/NOT_HALT
>
>
> No this step is incorrect as you can see by the following code.
> In this case ABORTED = true causing the outermost H_Hat() to halt.

Ok, this is all down to me copy-and-pasting from my earlier post which 
included my DeciderLogic() intermediate routine.  I tried to remove 
references to that after the copying, but the HALT/NOT_HALT is a carry 
over.  (DeciderLogic() translated ABORTED into the HALT/NOT_HALT 
decision that H makes.)

So this is easily corrected - we just have to know how ABORTED is to be 
translated into H's HALT/NOT_HALT decision.  (I.e. whether H sets EAX to 
0 or 1 when ABORTED is true...)

>
> // M has address of H_Hat()
> void H_Hat(u32 M)
> {
>   if (DebugTrace(M, M)) // M(M) Aborted?
>     MOV_EAX_0  // Execution of M(N) has been aborted
>   else
>   {
>     MOV_EAX_1  // M(N) has halted
>     HERE: goto HERE;
>   }
>   HALT
> }

Given this implementation it's clear Was_Its_Execution_Aborted() 
returning ABORTED results in H_Hat halting.  Which is what you said, so 
good.

So we can correct my trace by amending my line from
 >>    H_Hat does the opposite of HALT/NOT_HALT
to
 >>    H_Hat halts

>
> It seems really really weird that H_Hat() decides that its input of
> H_Hat() will not halt and then it goes ahead and halts itself.

Not really, H_Hat is not a decider.  It is only you who sees weirdness, 
because you /tried/ to design H/H^ to work in a particular way, and in 
the end they do not.  :)

>
> The reason for this is that the outermost halt decider has more
> information than the inner halt decider (more traced steps) so we are
> not getting two different results from the same function for the same
> input. The inputs are different.

I am only interested (for this machine trace) in whether H_Hat(H_Hat) 
halts or does not halt for the specific case of your final code delivery 
(which you've yet to make).  You can give your own explanations for 
/why/ your code does what it does, but I don't need to understand that. 
(Also, the trace is only for the outer level process, and you are trying 
to explain something about the inner levels, which is OK but not 
relevant to this level of trace.)

>
> Also the key discovery that I made in 2016 is the all of the
> conventional self-referential halting problem proof counter-examples are
> infinitely recursive so that none of them ever reach the undecidable
> state transitions.
>
> This key insight necessitates that any halt decider based on a
> DebugStep() of its input must terminate this input or get stuck in
> infinite execution.
>
> Although it may be possible for it to wait a fixed number of steps to
> see what its input does before terminating its input it cannot simply
> wait to see what its input would do. This results in infinite execution.
>
> it is best that it terminates its input as soon as it definitely decides
> that its input must be terminated. This keeps things simple.
>
>> So... which of these lines are correct/incorrect?

Thanks for responding above.

So... Based on your comments, here is a corrected version of my 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

Great!


>>
>>
>> And for comparison here is what H does:
>>
>> 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 emulation is looping!!!
>
> Infinitely recursive
>
>>      Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>    H_Hat halts indicating HALT/NOT_HALT decision based on rc..
>>                ..from Was_Its_Execution_Aborted()
>>
>> While we're at it you might as well say which of these lines are
>> correct/incorrect too.  :)
>>

And also, based on your comments, here is a corrected version of my 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]

Great!

Except that now the H_Hat and H machine traces are in conflict for the 
expected reason.

You may explain /why/ your code has behaved like this by talking about 
outer levels of code having more information than inner levels, and why 
you believe there is nothing contradictory about this, but in the end 
that simply doesn't matter.  The fact is that FOR YOUR FINAL DELIVERY OF 
H, H_Hat, it is the case that:

1)  H_Hat run with input (H_Hat) halts
2)  H run with input (H_Hat, H_Hat) transitions to the NOT_HALT state.

This is exactly what Linz says.  Your refutation has failed.

Mike.

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-24 13:38 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<G6ydnc74LP4z6QnCnZ2dnUU7-cfNnZ2d@giganews.com>
In reply to#24318
On 10/24/2020 10:58 AM, Mike Terry wrote:
> On 24/10/2020 05:02, olcott wrote:
>> On 10/23/2020 7:06 PM, Mike Terry wrote:
>>> On 24/10/2020 00:31, olcott wrote:
>>>> On 10/23/2020 6:17 PM, Mike Terry wrote:
>>>>> On 24/10/2020 00:03, Malcolm McLean wrote:
>>>>>> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
>>>>>>>
>>>>>>> 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))
>>>>>>> {
>>>>>> // Machine no longer exists. Control flow can't get to this point.
>>>>>>> // Was_Its_Execution_Aborted says that M(M) was aborted
>>>>>>> HALT; // so we halt
>>>>>>> }
>>>>>>
>>>>>> That's the step you are missing. At least this is what I
>>>>>> understand. PO
>>>>>> sems to be changing his argument slightly and I don't want to speak
>>>>>> for
>>>>>> him.
>>>>>>
>>>>>
>>>>> No, this is you not undertanding the whole emulation thing that's
>>>>> going on.  If you'd read on you'd have seen a quite thorough
>>>>> explanation of the flow of control that's involved.
>>>>>
>>>>> If you read the rest of my post and are still unclear, post back and
>>>>> I'll try to explain better - but really it's all in my earlier post.
>>>>> Check out the "stack trace" (sort-of) of the two machines H and H_Hat
>>>>> running.
>>>>>
>>>>> Mike.
>>>>
>>>> The outermost H_Hat() has its process terminated before:
>>>> if (Was_Its_Execution_Aborted(M, M)) returns a value to H_Hat().
>>>>
>>>> This is because the DebugTrace() that H() invoked that created the
>>>> process that H_Hat() resides in is a few steps ahead of what the inner
>>>> DebugStep() invoked by H_Hat() can see.
>>>>
>>>
>>> OK I can see you're not even going to read the rest of my post, so
>>> I'll cut and paste the stack traces of what the two machines H, H_Hat
>>> do when they run, adjusting a bit to remove my intermediate
>>> DeciderLogic() routine.  At least if you disagree with something you
>>> can point out where we are diverging!
>>>
>>> The most relevent one for discussing what H_Hat does is the trace for
>>> H_Hat machine:
>>>
>>> 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 emulation is looping!!!
>>
>> Infinitely recursive.
> 
> What do you mean by that?  Are you agreeing or disagreeing with the 
> line?  How should the line be corrected?
>

I mean that H_Hat() does not loop. H_Hat() executes infinite recursion 
and thus never reaches its undecidable states.

> Does Was_Its_Execution_Aborted() decide the emulated H_Hat(H_Hat) is 
> exhibiting infinite recursion)?  That is a form of "not halting", so we 
> could make the line 100% correct by rewording it

Yes you got it.

> I think maybe you just mean that Was_Its_Execution_Aborted() identifies 
> the onset of infinited recursion in the program its emulating, and so 
> decides it is going to abort the emulation - so your remark is just a 
> comment.  Or at least we can get rid of this comment if I change my 
> wording to
> 
>        Was_Its_Execution_Aborted decides the emulated program ..
>                  .. will never terminate if not aborted

Perfect !!!

> I.e. the problem(?) is just my use of the word "loop" rather than the 
> more general "never terminate".

Exactly !!!

>>>      Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>>    H_Hat does the opposite of HALT/NOT_HALT
>>
>>
>> No this step is incorrect as you can see by the following code.
>> In this case ABORTED = true causing the outermost H_Hat() to halt.
> 
> Ok, this is all down to me copy-and-pasting from my earlier post which 
> included my DeciderLogic() intermediate routine.  I tried to remove 
> references to that after the copying, but the HALT/NOT_HALT is a carry 
> over.  (DeciderLogic() translated ABORTED into the HALT/NOT_HALT 
> decision that H makes.)
> 
> So this is easily corrected - we just have to know how ABORTED is to be 
> translated into H's HALT/NOT_HALT decision.  (I.e. whether H sets EAX to 
> 0 or 1 when ABORTED is true...)


(a) Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) == true
means that an error was detected and the program's execution was aborted.

(b) Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) == false
means that NO ERROR WAS DETECTED and the program's execution WAS NOT 
ABORTED.

Although (b) is an example of HALTED (a) is not an example of NOT_HALTED


>> // M has address of H_Hat()
>> void H_Hat(u32 M)
>> {
>>   if (DebugTrace(M, M)) // M(M) Aborted?
>>     MOV_EAX_0  // Execution of M(N) has been aborted
>>   else
>>   {
>>     MOV_EAX_1  // M(N) has halted
>>     HERE: goto HERE;
>>   }
>>   HALT
>> }
> 
> Given this implementation it's clear Was_Its_Execution_Aborted() 
> returning ABORTED results in H_Hat halting.  Which is what you said, so 
> good.
> 
> So we can correct my trace by amending my line from
>  >>    H_Hat does the opposite of HALT/NOT_HALT
> to
>  >>    H_Hat halts

Yes. When either H(H_Hat, H_Hat) or H_Hat(H_Hat) is called from the 
x86utm execution context they both call
Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
from this context and they both receive a return value of TRUE.

Both of these execution contexts create another execution context where 
another Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) is 
executed that get aborted before it ever returns any value.

>> It seems really really weird that H_Hat() decides that its input of
>> H_Hat() will not halt and then it goes ahead and halts itself.
> 
> Not really, H_Hat is not a decider.  It is only you who sees weirdness, 
> because you /tried/ to design H/H^ to work in a particular way, and in 
> the end they do not.  :)
> 

What I mean by really weird is only that other people besides myself may 
have very great difficulty in understanding how the same function
Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
does not return the same result from what superficially seems to be the 
same input.

They may even have great difficulty in understanding that an outer 
instance of Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
can possibly exist.

If they can't understand that an outer instance can possibly exist then 
they can't understand that this outer instance has seen a longer 
sequence of execution steps than the inner instance.

Ben would probably respond as he has responded in the past and simply 
dogmatically assert that there cannot possibly be any inner or outer 
instance there can only be a single instance.

The key difference this time is that I have a fully operational x86utm 
operating system to empirically prove otherwise.

He would then go on to say that this same sort of thing has nothing to 
do with Turing machines as if it was impossible for a UTM to execute 
another UTM that executes yet another UTM. At this point he would go 
back to his dogmatic assertions and simply ignore everything that I say.

>> The reason for this is that the outermost halt decider has more
>> information than the inner halt decider (more traced steps) so we are
>> not getting two different results from the same function for the same
>> input. The inputs are different.
> 
> I am only interested (for this machine trace) in whether H_Hat(H_Hat) 
> halts or does not halt for the specific case of your final code delivery 
> (which you've yet to make).  You can give your own explanations for 
> /why/ your code does what it does, but I don't need to understand that. 
> (Also, the trace is only for the outer level process, and you are trying 
> to explain something about the inner levels, which is OK but not 
> relevant to this level of trace.)

The outermost instance of
bool Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
that is executed in the x86utm execution context simply traces the 
execution of H_Hat(H_Hat) until it decides that this execution is 
infinitely recursive then its stops tracing this execution trace and 
reports true.

When executed in the outermost execution context of x86utm both
H(H_Hat, H_Hat) and H_Hat(H_Hat) call
bool Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
thus they both get the same return value of true.


>> Also the key discovery that I made in 2016 is the all of the
>> conventional self-referential halting problem proof counter-examples are
>> infinitely recursive so that none of them ever reach the undecidable
>> state transitions.
>>
>> This key insight necessitates that any halt decider based on a
>> DebugStep() of its input must terminate this input or get stuck in
>> infinite execution.
>>
>> Although it may be possible for it to wait a fixed number of steps to
>> see what its input does before terminating its input it cannot simply
>> wait to see what its input would do. This results in infinite execution.
>>
>> it is best that it terminates its input as soon as it definitely decides
>> that its input must be terminated. This keeps things simple.
>>
>>> So... which of these lines are correct/incorrect?
> 
> Thanks for responding above.
> 
> So... Based on your comments, here is a corrected version of my 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

It only halts because it was aborted thus it was decided to be incorrect.

If (as in the olden days before there were user interface infinite 
loops) a program that never halted was always incorrect then
bool Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
always divides programs into correct / incorrect.


> Great!
> 
> 
>>>
>>>
>>> And for comparison here is what H does:
>>>
>>> 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 emulation is looping!!!
>>
>> Infinitely recursive
>>
>>>      Was_Its_Execution_Aborted stops emulating and returns ABORTED
>>>    H_Hat halts indicating HALT/NOT_HALT decision based on rc..
>>>                ..from Was_Its_Execution_Aborted()
>>>
>>> While we're at it you might as well say which of these lines are
>>> correct/incorrect too.  :)
>>>
> 
> And also, based on your comments, here is a corrected version of my 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]
> 
> Great!
> 
> Except that now the H_Hat and H machine traces are in conflict for the 
> expected reason.

In every single case
Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
divides programs into correct / incorrect

There are no undecidable case.

Either a program had to be terminated because it would not otherwise 
halt or it need not be terminated because it has halted.

Either a program had to be terminated because it would not otherwise 
halt or it need not be terminated because it has halted.

Either a program had to be terminated because it would not otherwise 
halt or it need not be terminated because it has halted.

Either a program had to be terminated because it would not otherwise 
halt or it need not be terminated because it has halted.

Either a program had to be terminated because it would not otherwise 
halt or it need not be terminated because it has halted.

> You may explain /why/ your code has behaved like this by talking about 
> outer levels of code having more information than inner levels, and why 
> you believe there is nothing contradictory about this, but in the end 
> that simply doesn't matter.  The fact is that FOR YOUR FINAL DELIVERY OF 
> H, H_Hat, it is the case that:
> 
> 1)  H_Hat run with input (H_Hat) halts
> 2)  H run with input (H_Hat, H_Hat) transitions to the NOT_HALT state.
> 
> This is exactly what Linz says.  Your refutation has failed.
> 
> Mike.
> 


-- 
Copyright 2020 Pete Olcott

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


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

FromBen Bacarisse <ben.usenet@bsb.me.uk>
Date2020-10-25 01:17 +0100
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<87sga3xip7.fsf@bsb.me.uk>
In reply to#24329
olcott <NoOne@NoWhere.com> writes:

> Ben would probably respond as he has responded in the past and simply
> dogmatically assert that there cannot possibly be any inner or outer
> instance there can only be a single instance.

Never said that.  I said (correctly) that you've suckered people into
this debate about inner and outer whatevers, aborts vs returns and so on
when all that is needed to show that H(H_Hat, H_Hat) is wrong is to know
the value of DebugTrace(H_Hat, H_Hat) and what that means (because H set
eax based on that alone).  How that value is arrived at makes no
difference.

> The key difference this time is that I have a fully operational x86utm
> operating system to empirically prove otherwise.

Before (when you told the Big Lie) you said you had H and H^ exactly and
precisely as in Linz fully encode as actual Turing machines.  No guff
about inner or outer anything.  No redefining the problem.  Just
something clear an simple (and impossible).

> He would then go on to say that this same sort of thing has nothing to
> do with Turing machines as if it was impossible for a UTM to execute
> another UTM that executes yet another UTM. At this point he would go
> back to his dogmatic assertions and simply ignore everything that I
> say.

Best if you don't try to paraphrase people you don't understand.
(Remember when you called me mad because you didn't know what a function
was?)  It certainly can't advance your case to argue against straw men.
To make progress you need to clear the decks and restate your claim
clearly.  You appear to have abandoned the idea that you will
demonstrate an H and H^ pair where H(H^, H^) is correct.  But what you
now claim is getting more and more lost in a mess of
Names_With_Underscores_For_Code_You_Wont_Show.

-- 
Ben.

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-23 18:06 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<Us2dnbWHxsd-_A7CnZ2dnUU7-XnNnZ2d@giganews.com>
In reply to#24257
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
>     }
> }
> 
The key difference is that if (Was_Its_Execution_Aborted(M, M))
is true, then its execution has already been aborted so it never reaches 
this if statement.

-- 
Copyright 2020 Pete Olcott

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


#24267 — 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-24 00:38 +0100
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<ws6dnaq6IL7H9A7CnZ2dnUU78RnNnZ2d@brightview.co.uk>
In reply to#24259
On 24/10/2020 00:06, 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
>>     }
>> }
>>
> The key difference is that if (Was_Its_Execution_Aborted(M, M))
> is true, then its execution has already been aborted so it never reaches
> this if statement.
>

No, that's obviously wrong as I explained.  All that has been aborted is 
the /emulation/ of H_Hat that occurs within Was_Its_Execution_Aborted(M, 
M).

Do you really not see the difference between H_Hat running at outer 
level, and some inner "emulation" of H_Hat that occurs within 
Was_Its_Execution_Aborted()?  Was_Its_Execution_Aborted() can only 
"abort" the inner emulation [i.e. just decide to stop emulating at some 
point], not its own running instance!

Are you trying to claim that the code for Was_Its_Execution_Aborted() 
contains a HALT instruction?  That's not simply not allowed - 
Was_Its_Execution_Aborted() MUST actually report back its 
TERMINATED/ABORTED decision, because it's part of a Halt Decider and the 
only way a Halt Decider is allowed to terminate is in one of the two 
decider states.  In our template it has been arranged (for good reason!) 
to occur /only/ in the two alternate HALT instructions in H().  The role 
of Was_Its_Execution_Aborted() is to enable H and H_Hat to make their 
correct choices.


Mike.

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-23 18:46 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<ZYudnb8yQ8z19g7CnZ2dnUU7-LXNnZ2d@giganews.com>
In reply to#24267
On 10/23/2020 6:38 PM, Mike Terry wrote:
> On 24/10/2020 00:06, 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
>>>     }
>>> }
>>>
>> The key difference is that if (Was_Its_Execution_Aborted(M, M))
>> is true, then its execution has already been aborted so it never reaches
>> this if statement.
>>
> 
> No, that's obviously wrong as I explained.  All that has been aborted is 
> the /emulation/ of H_Hat that occurs within Was_Its_Execution_Aborted(M, 
> M).
> 
> Do you really not see the difference between H_Hat running at outer 
> level, and some inner "emulation" of H_Hat that occurs within 
> Was_Its_Execution_Aborted()?  Was_Its_Execution_Aborted() can only 
> "abort" the inner emulation [i.e. just decide to stop emulating at some 
> point], not its own running instance!

I made a process map to verify this answer:

The outermost H_Hat() has its process terminated before:
if (Was_Its_Execution_Aborted(M, M)) returns a value to this outermost 
H_Hat().

This is because the DebugTrace() that H() invoked that created the 
process that H_Hat() resides in is a few steps ahead of what the inner 
DebugStep() invoked by H_Hat() can see.

When the outermost DebugTrace() aborts the outermost H_Hat() the entire 
process tree created by this outermost H_hat() is terminated.

> Are you trying to claim that the code for Was_Its_Execution_Aborted() 
> contains a HALT instruction?  That's not simply not allowed - 
> Was_Its_Execution_Aborted() MUST actually report back its 
> TERMINATED/ABORTED decision, because it's part of a Halt Decider and the 
> only way a Halt Decider is allowed to terminate is in one of the two 
> decider states.  In our template it has been arranged (for good reason!) 
> to occur /only/ in the two alternate HALT instructions in H().  The role 
> of Was_Its_Execution_Aborted() is to enable H and H_Hat to make their 
> correct choices.
> 
> 
> Mike.
> 


-- 
Copyright 2020 Pete Olcott

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-24 01:03 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<c6CdnZhmmtBeXg7CnZ2dnUU7-VfNnZ2d@giganews.com>
In reply to#24257
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.

If Was_Its_Execution_Aborted() means H_Hat() [did not halt], then when 
it is aborted and it halts we have the wrong answer.

It must mean: Aborted_Because_Non_Halting_Behavior_Detected.
This is the exact same cases, except now we have the right answer.

 > any decision on whether some internal routine made some particular
 > decision and ceased emulating something or other - all that is beside
 > the point from the Linz proof perspective.)

No. Not at all. Not in the least little bit.
To remove the pathological self-reference and make the halting problem 
decidable we must ask a question that cannot be thwarted.

 > If you want to change the interpretation of the return code from
 > Was_Its_Execution_Aborted() to mean something other than
 > HALT/NOT_HALT,
 > then you will now have to provide extra logic in H, and hence also in
 > H_Hat, to convert that return code into its final HALT/NOT_HALT
 > decision.  (Regardless of your new question, H must still deliver the
 > Halting Decider required output.)

No. Not at all. Not in the least little bit.
Aborted_Because_Non_Halting_Behavior_Detected means that the input would 
not halt yet it says it in such a way that it cannot be contradicted.

 > There's really nothing to be gained from choosing to do this.
 > Originally the reason for extracting the Halt Decider logic into
 > a separate routine outside of H() was that exactly the same
 > logic needed to be employed in both H() and H_Hat().

bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
is the same function invoked by both H() and H_Hat().
This function cannot be contradicted.

 > The role of H in the Linz proof is to make the
 > Halt Decider decision of either HALT or NOT_HALT, and so if we extract

Yet we must be careful to frame the question so that it cannot be 
contradicted.

 > the logic into an external routine, it's pointless for that routine to
 > return anything other than HALT/NOT_HALT.  Given that your
 > Was_Its_Execution_Aborted() does not return HALT/NOT_HALT then the
 > thing to do is call it from within the halt decider logic routine.

No, not at all. Not in the least. As soon as we redefine the halt 
decider so that its return value cannot possisbly be contradicted then 
the halting problem ceases to be undecidable.

Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) == true
means that the input has infinite execution.

Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) == false
means that the input DOES NOT HAVE infinite execution.


-- 
Copyright 2020 Pete Olcott

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


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

FromAndré G. Isaak <agisaak@gm.invalid>
Date2020-10-24 08:04 -0600
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<rn1c9d$75b$1@dont-email.me>
In reply to#24306
On 2020-10-24 00:03, olcott wrote:

> If Was_Its_Execution_Aborted() means H_Hat() [did not halt], then when 
> it is aborted and it halts we have the wrong answer.
> 
> It must mean: Aborted_Because_Non_Halting_Behavior_Detected.
> This is the exact same cases, except now we have the right answer.

I'm starting to think your confusion about Linz proof is even deeper 
than I'd originally thought.

 From the above you seem to think that there is a contradiction if you 
claim a program doesn't halt when it has to be aborted inside 
DebugTrace() because aborting it causes it to halt. That isn't a 
contradiction, because presumably if you ran the program on its own it 
would not halt. And that's the only behaviour that H is concerned with.

And if you are under the impression that *that* is the contradiction 
inherent in the Linz Proof, then you have completely misunderstood the 
proof (not that there was any doubt of that).

The question which H is designed to answer is 'does the input TM halt'?

It isn't asking about what happens when run inside your DebugTrace() 
routine. It's asking about what happens when the machine is run on its own.

There's nothing in the definition of H which requires H to run the input 
program at all. Merely to determine if it would halt, which is one 
reason, among many, why you need to stop talking about UTMs. A UTM is a 
TM which executes another arbitrary TM. Neither H nor Ĥ do that. They 
answer a *question* regarding another TM.

André

-- 
To email remove 'invalid' & replace 'gm' with well known Google mail 
service.

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-24 11:25 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<96KdnfDmjNgfyAnCnZ2dnUU7-KHNnZ2d@giganews.com>
In reply to#24312
On 10/24/2020 9:04 AM, André G. Isaak wrote:
> On 2020-10-24 00:03, olcott wrote:
> 
>> If Was_Its_Execution_Aborted() means H_Hat() [did not halt], then when 
>> it is aborted and it halts we have the wrong answer.
>>
>> It must mean: Aborted_Because_Non_Halting_Behavior_Detected.
>> This is the exact same cases, except now we have the right answer.
> 
> I'm starting to think your confusion about Linz proof is even deeper 
> than I'd originally thought.
> 
>  From the above you seem to think that there is a contradiction if you 
> claim a program doesn't halt when it has to be aborted inside 
> DebugTrace() because aborting it causes it to halt. That isn't a 
> contradiction, because presumably if you ran the program on its own it 
> would not halt. And that's the only behaviour that H is concerned with.

H_Hat(H_Hat) calls
Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) which aborts 
the inner H_Hat() and returns true to the outer H_Hat() which then 
terminates normally.

> And if you are under the impression that *that* is the contradiction 
> inherent in the Linz Proof, then you have completely misunderstood the 
> proof (not that there was any doubt of that).
> 
> The question which H is designed to answer is 'does the input TM halt'?
> 

Yes and this question can be phrased such that it is subject to 
pathological self-reference and it can be phrased such that is is not 
subject to patholegical self-reference.

> It isn't asking about what happens when run inside your DebugTrace() 
> routine. It's asking about what happens when the machine is run on its own.

Previously when I talking about inner H_Hat() and outer _H_Hat() people 
flatly denied that there could be any such thing. Now I have a complete 
x86utm operating system to empirically prove my point.

People were saying the every instance of a halt decider having the same 
input must always return that same result without realizing that the 
outer instance of a halt decider has a longer execution trace than the 
inner instance of this halt decider sop the input is not the same.

> There's nothing in the definition of H which requires H to run the input 
> program at all. Merely to determine if it would halt, which is one 
> reason, among many, why you need to stop talking about UTMs. A UTM is a 
> TM which executes another arbitrary TM. Neither H nor Ĥ do that. They 
> answer a *question* regarding another TM.
> 
> André
> 

The simplest and most direct way to define any halt decider is to simply 
execute its program under test (PUT) one (step / state transition) at a 
time and examine its actual behavior.

-- 
Copyright 2020 Pete Olcott

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


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

Back to top | Article view | comp.theory


csiph-web