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


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

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-25 13:55 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<bd965614-b7fd-45fb-88a8-cc4e0d323faen@googlegroups.com>
In reply to#24403
On Sunday, 25 October 2020 at 17:26:16 UTC, Mike Terry wrote:
> 
> Correct, but for Malcolm's benefit, the halt decider itself continues 
> running. It has not smashed its own machine. :) 
> 
Yes, you have to smash your own machine for the rebuttal of Linz
to work. Otherwise there is no way out. :-(

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-25 15:56 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<1KKdnYpTLv0NewjCnZ2dnUU7-K2dnZ2d@giganews.com>
In reply to#24420
On 10/25/2020 3:55 PM, Malcolm McLean wrote:
> On Sunday, 25 October 2020 at 17:26:16 UTC, Mike Terry wrote:
>>
>> Correct, but for Malcolm's benefit, the halt decider itself continues
>> running. It has not smashed its own machine. :)
>>
> Yes, you have to smash your own machine for the rebuttal of Linz
> to work. Otherwise there is no way out. :-(
> 

This does (as has always been my stated goal) refute all of the 
conventional self-referential halting problem proofs. None of these 
proofs show that halting is undecidable they only show that one 
definition of a halt decider does not work.

bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)

Every syntactically correct machine description can be divided into
(a) HAS_INFINITE_EXECUTION
(b) DOES_NOT_HAVE_INFINITE_EXECUTION

I have as I have claimed correctly refuted the conventional 
self-referential halting problem proofs.


-- 
Copyright 2020 Pete Olcott

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


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

FromRichard Damon <Richard@Damon-Family.org>
Date2020-10-25 17:35 -0400
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<hcmlH.359441$575.310705@fx38.iad>
In reply to#24420
On 10/25/20 4:55 PM, Malcolm McLean wrote:
> On Sunday, 25 October 2020 at 17:26:16 UTC, Mike Terry wrote:
>>
>> Correct, but for Malcolm's benefit, the halt decider itself continues 
>> running. It has not smashed its own machine. :) 
>>
> Yes, you have to smash your own machine for the rebuttal of Linz
> to work. Otherwise there is no way out. :-(
> 

except then you don't have the required halt decider because it never
answered the question,

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


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

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-25 14:43 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<d9f37a8d-e895-465e-8868-80bf87630ad0n@googlegroups.com>
In reply to#24428
On Sunday, 25 October 2020 at 21:35:13 UTC, Richard Damon wrote:
> On 10/25/20 4:55 PM, Malcolm McLean wrote: 
> > On Sunday, 25 October 2020 at 17:26:16 UTC, Mike Terry wrote: 
> >> 
> >> Correct, but for Malcolm's benefit, the halt decider itself continues 
> >> running. It has not smashed its own machine. :) 
> >> 
> > Yes, you have to smash your own machine for the rebuttal of Linz 
> > to work. Otherwise there is no way out. :-( 
> >
> except then you don't have the required halt decider because it never 
> answered the question,
>
It's a Turing machine*, not a subroutine. It can write a 0 / 1 to a previously
agreed location on the tape, then smash the machine.

*OK, it's not. 

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-25 16:55 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<IuSdneGQPe-paQjCnZ2dnUU7-d2dnZ2d@giganews.com>
In reply to#24428
On 10/25/2020 4:35 PM, Richard Damon wrote:
> On 10/25/20 4:55 PM, Malcolm McLean wrote:
>> On Sunday, 25 October 2020 at 17:26:16 UTC, Mike Terry wrote:
>>>
>>> Correct, but for Malcolm's benefit, the halt decider itself continues
>>> running. It has not smashed its own machine. :)
>>>
>> Yes, you have to smash your own machine for the rebuttal of Linz
>> to work. Otherwise there is no way out. :-(
>>
> 
> except then you don't have the required halt decider because it never
> answered the question,
> 

bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
Cannot be fooled by pathological self reference.


-- 
Copyright 2020 Pete Olcott

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


#24384 — 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 14:43 +0000
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<87lffu74e8.fsf@bsb.me.uk>
In reply to#24377
Malcolm McLean <malcolm.arthur.mclean@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.

> To make that obvious, I say abort means "smash the machine".

That does not make it obvious.  It suggests you are talking about
hardware, not mathematics.

-- 
Ben.

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


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

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-25 08:36 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<7969da2b-02c2-4b5a-a067-014b5ede89fbn@googlegroups.com>
In reply to#24384
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.

Remember PO was very clear that he had changed the question from "does it
halt / not halt?" to "was it aborted?".

By talking about smashing the machine, the stratagem becomes obvious.
Anyone can now see that H_Hat doesn't halt, it was aborted. But of course you
have to abort the instance of H_Hat you are running, not the one you are 
emulating. That point has caused difficulty.

However the price of saying that the machine is smashed is that it now becomes 
more obvious that something somewhere isn't a Turing machine. In PO's original 
example, that's H_Hat, the act of writing 0 to eax is the step that is disallowed. In 
my modified example, it's H. H destroys itself. So H can't be a Turing machine.
However it still returns "halts" if H_Hat halts and destroys itself if H_Hat 
destroys itself, so we've got rid of the inconsistency, which was the goal.
  
Just to be a bit cheeky about it, remember that the function while(1); is unlikely
to run forever. It will terminate when the machine is aborted.

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-25 12:23 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<dZKdncZVf6gBKQjCnZ2dnUU7-LfNnZ2d@giganews.com>
In reply to#24391
On 10/25/2020 10:36 AM, Malcolm McLean wrote:
> 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.
> 
> Remember PO was very clear that he had changed the question from "does it
> halt / not halt?" to "was it aborted?".
> 
> By talking about smashing the machine, the stratagem becomes obvious.
> Anyone can now see that H_Hat doesn't halt, it was aborted. But of course you
> have to abort the instance of H_Hat you are running, not the one you are
> emulating. That point has caused difficulty.
> 
> However the price of saying that the machine is smashed is that it now becomes
> more obvious that something somewhere isn't a Turing machine. In PO's original

If we assume that that H_Hat() machine physically exists and is 
physically destroyed by smashing it with a sledge hammer then this 
indicates that the machine is not exactly and precisely a Turing machine 
in every single way.

If we understand that:
(a) All of the executable code is implemented as von Neumann 
architecture virtual machines.

(b) An operating system function u32* Allocate(u32 size) is provided.

(c) The execution of these virtual machines never require more memory 
than Allocate(u32 size) can allocate.

then we can know that the computations of these virtual machines are 
equivalent to the computations of universal Turing Machines.
https://en.wikipedia.org/wiki/Random-access_stored-program_machine

> example, that's H_Hat, the act of writing 0 to eax is the step that is disallowed. In

Not all all. It is equivalent to the Linz machine transitioning to 
((qn)) non-halting behavior detected, would not terminate unless aborted.

The outermost H_Hat(H_Hat) that is invoked in the x86utm process context 
calls DebugTrace(H_Hat, H_Hat) AKA
Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
that is also executed in the x86utm process context.

This causes DebugTrace(H_Hat, H_Hat) to create a whole new process 
context to executes its first parameter (the inner H_Hat) in DebugStep() 
mode.

This causes the inner H_Hat to execute an inner
DebugTrace(H_Hat, H_Hat) in its own subordinate process context.

This inner DebugTrace(H_Hat, H_Hat) creates another whole new process to
that executes its first parameter (an inner inner H_Hat) in DebugStep() 
mode.

------------------------------------------------------

The same sequence can be implemented a Universal Turing Machines instead 
of von Neumann architecture virtual machines.

The master UTM owns the whole tape and allocates portions of this tape 
to its subordinate UTMs when they are first executed or on request.

The master UTM executes the H_Hat() UTM and allocates a portion of its 
tape to H_Hat().

The H_Hat() UTM executes the DebugTrace() (causing the master UTM to 
allocate a portion of its master tape to DebugTrace)

DebugTrace() executes another instance of H_Hat() is allocated its own 
separate portion of the master UTM tape.

All of the instances of DebugTrace() execute their subordinate UTMs one 
state transition at a time.

As soon as the outermost DebugTrace() detects that its subordinate UTM 
would not terminate it stops executing it, thus stopping the whole 
execution tree of UTMs.


> my modified example, it's H. H destroys itself. So H can't be a Turing machine.
> However it still returns "halts" if H_Hat halts and destroys itself if H_Hat
> destroys itself, so we've got rid of the inconsistency, which was the goal.
>    
> Just to be a bit cheeky about it, remember that the function while(1); is unlikely
> to run forever. It will terminate when the machine is aborted.
> 


-- 
Copyright 2020 Pete Olcott

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


#24435 — 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 22:54 +0000
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<87a6w97w7w.fsf@bsb.me.uk>
In reply to#24391
Malcolm McLean <malcolm.arthur.mclean@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?

The meaning of the return from H (and it must return) has to be
halts/does not halt.  H need not be always right (indeed it allowed to
be wrong in every case but one) but to call its result "correct", it must
indicate halting or not halting and it must indicate the right one of
these for H(H_Hat, H_Hat).

By talking about aborted/not aborted it is clear he's no longer saying
anything interesting -- unless they happen map to halting/not-halting the
key case.  Bit then I'd have to have said they do and I don't recall
that either.

I suppose, since we don't care about any other cases, we could allow the
meaning of the return to be "aborted" or "played the Marseillaise" for
all or some of those other cases, but it seems simpler to fix a single
meaning, and it does not constrain H since H can be wrong about
everything else.

> By talking about smashing the machine, the stratagem becomes obvious.

Not to me.  I don't know what stratagem you are talking about is even
now, and since I think of these questions as mathematical ones (which is
what they are), smashing things is a completely unhelpful metaphor.

In the TM model, a computation is the recursive application of a
function that maps a TMs configuration another configurations.  Halting
is the property that the sequence of such configurations is finite.  I
think about program in quite a similar way.  while(1); has a meaning
detached from registers, memory, CPUs, machine instructions and so on.
It describes a non-terminating sequence of configurations.

> Anyone can now see that H_Hat doesn't halt, it was aborted. But of course you
> have to abort the instance of H_Hat you are running, not the one you are 
> emulating. That point has caused difficulty.

I am not surprised.  "You have to abort", "you are running".  This is
the sort of language that makes me tear my hair out.  "It was aborted"
is the same.  Programs follow control paths, some of which get fancy
names like that, but they are just jumps.  If they can occur at any time
(like an interrupt) then ideally the program text would reflect this but
it usually can't.  (I once worked on a microcoded architecture where the
points at which interrupts could be taken, and the effect they would
have, was explicit in the code for every instruction.)

> However the price of saying that the machine is smashed is that it now becomes 
> more obvious that something somewhere isn't a Turing machine.

How could it be more obvious?  He's banged on about x86 code for months.
The term "Turing machine" is not some vague term meaning "abstract
program", it specifies a mathematical object.  The smashing metaphor
just stops me seeing any connection to the halting problem.

> Just to be a bit cheeky about it, remember that the function while(1); is unlikely
> to run forever. It will terminate when the machine is aborted.

I don't see how this is cheeky.  I know you have this sort of
operational view of what a program means.  Presumably while(1); is also
at the mercy of buggy hardware, cosmic rays and power cuts.  Its meaning
will vary from run to run and from place to place.  Its meaning is not
in the text, but in what happens on this hardware at this time right
now.

I can't see anything useful coming out of that view in relation to
formal claims like the halting theorem.

-- 
Ben.

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


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

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-25 16:19 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<0a47a060-1ac7-4feb-ac00-619b62f3dad3n@googlegroups.com>
In reply to#24435
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? 

Unfortunately PO hasn't been consistent. For example he accepted an amended
H_Hat from you which destroyed his whole system. 

Of course it's no longer the original problem.  The question has changed and the
requirement that H and H_Hat be Turing machines has been relaxed. I think
I've been clear on that.
 

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-25 18:35 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<9PidnWWl4PxXlgvCnZ2dnUU7-X3NnZ2d@giganews.com>
In reply to#24437
On 10/25/2020 6:19 PM, Malcolm McLean wrote:
> 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?
> 
> Unfortunately PO hasn't been consistent. For example he accepted an amended
> H_Hat from you which destroyed his whole system.
> 
> Of course it's no longer the original problem.  The question has changed and the
> requirement that H and H_Hat be Turing machines has been relaxed. I think
> I've been clear on that.

We have no need to drop the idea that this applies to Turing Machines
x86 language ≡ von Neumann architecture ≡ UTM

Does the UTM halt decider have to stop executing its subordinate UTM to 
prevent its own infinite execution?

The UTM halt decider executes its subordinate UTM one state transition 
at a time until it decides that it must stop the execution of its 
subordinate UTM or its subordinate UTM has terminated normally.


-- 
Copyright 2020 Pete Olcott

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-25 18:40 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<q8mdnbtLy8aXkAvCnZ2dnUU7-XudnZ2d@giganews.com>
In reply to#24439
On 10/25/2020 6:35 PM, olcott wrote:
> On 10/25/2020 6:19 PM, Malcolm McLean wrote:
>> 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?
>>
>> Unfortunately PO hasn't been consistent. For example he accepted an 
>> amended
>> H_Hat from you which destroyed his whole system.
>>
>> Of course it's no longer the original problem.  The question has 
>> changed and the
>> requirement that H and H_Hat be Turing machines has been relaxed. I think
>> I've been clear on that.
> 
> We have no need to drop the idea that this applies to Turing Machines
> x86 language ≡ von Neumann architecture ≡ UTM
> 
> Does the UTM halt decider have to stop executing its subordinate UTM to 
> prevent its own infinite execution?
> 
> The UTM halt decider executes its subordinate UTM one state transition 
> at a time until it decides that it must stop the execution of its 
> subordinate UTM or its subordinate UTM has terminated normally.

In either case it transitions into one of two final states ((qn)) or 
((qy)) indicating its decision.


-- 
Copyright 2020 Pete Olcott

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


#24443 — 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 01:17 +0000
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<87imax4wgm.fsf@bsb.me.uk>
In reply to#24437
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.

-- 
Ben.

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


#24446 — 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 02:49 +0000
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<7-udnW7WoOzWpAvCnZ2dnUU78RXNnZ2d@brightview.co.uk>
In reply to#24443
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.

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.

Then came the "changing the question", and along with it a string of 
renames for DebugTrace() and its return codes to ever longer names, 
while continuing to sometimes post about DebugTrace, and on other 
occasions various longer names, sometimes all in the same post!  (Well, 
the renaming of DebugTrace() is just Very Irritating, not the key issue.)

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?

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.

E.g. he gives code which directly translates the new question (which 
still isn't clearly stated) to the EAX halt states for the HD, and if we 
take those states as meaning the HP/Linz halt state meanings the whole 
"new question" thing becomes moot, and his example agrees with Linz 
proof.  (And is clearly "fooled" by the cheap Linz trick :) )

So I don't know what PO is saying any more, and every question gets an 
unclear response that doesn't resolve the issues.  Then there's all the 
"aborting" smoke, and some kind of "challenge" we're supposed to respond to!

I would say the thread is just too big and confused in purpose (and 
content) to be worth continuing.  Too many posters all with different 
assumptions about what PO might mean.  So I'm basically stopping, but 
might comment in "my own" particular subthreads if they seem to be 
progressing.

(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.)

Mike.

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


#24448 — 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 03:56 +0000
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<871rhl4p37.fsf@bsb.me.uk>
In reply to#24446
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;
}

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

> 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.

> 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.

-- 
Ben.

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


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

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-26 02:37 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<30e16903-9a9a-44fa-be79-004798f89d0an@googlegroups.com>
In reply to#24448
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. 

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


#24454 — 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 12:10 +0000
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<87v9ex2noc.fsf@bsb.me.uk>
In reply to#24453
Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:

> 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.

Is it?  It appears to be hard to explain.  I have no idea what the point
is, why it matters, or what the effect of it is supposed to be.  I don't
even know if it's important.

Generally I prefer code in these cases.  An illustrative code sketch
would surely have helped and can't be hard if the point is a simple one.
PO's code sketch makes no reference to "aborting" or raising signals or
any such thing.  There is only a function with a name that contains
"abort" -- a name from someone who frequently abuses technical terms.
All the descriptions suggests the function just returns when some
slightly vague condition in a simulated computation is found.

> But it has generated a huge thread.

I think PO has entered another phase of manic posting.

-- 
Ben.

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


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

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-26 06:45 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<8e5fe431-4bd5-4110-96e5-62860a625ca4n@googlegroups.com>
In reply to#24454
On Monday, 26 October 2020 at 12:10:15 UTC, Ben Bacarisse wrote:

> Generally I prefer code in these cases. An illustrative code sketch 
> would surely have helped and can't be hard if the point is a simple one. 
>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <signal.h>

int H(const char *src, const char *input)
{
   if (strstr(src, "printf"))
   {
      printf("Function will terminate normally\n");
      return 0;
   }
   else
   {
      printf("Function will terminate when aborted\n");
      kill(0, SIGINT);
      return 1;
   }
}

void H_Hat(const char *input)
{
   if (!H(input, input))
     while(1);
}

void hello(const char *input)
{
   printf("%s\n", input);
}

void loop(const char *input)
{
   while(1);
}

const char *H_Hatsrc = 
"void H_Hat(const char *input)"
"{"
"   if (!H(input, input))"
"     while(1);"
"}";

const char *hellosrc = 
"void hello(const char *input)"
"{"
"   printf(\"%s\\n\", input);"
"}";

const char *loopsrc =
"void loop(const char *input)"
"{"
"   while(1);"
"}";

void usage(void)
{
   printf("Pass the operation you want: choose from:\n");
   printf("H(hello)\n");
   printf("H(loop)\n");
   printf("H(H_hat)\n");
   printf("hello\n");
   printf("loop\n");
   printf("H_Hat\n"); 

   exit(0);
}


void handle_abort(int x)
{
  printf("Program terminated because aborted\n");
  exit(0);
}

int main(int argc, char **argv)
{

   struct sigaction sa;
   sa.sa_handler = handle_abort;
   sa.sa_mask = SIGINT;
   sa.sa_flags = 0;
   
   sigaction(SIGINT, &sa, 0);

   if (argc != 2)
     usage();

   if (!strcmp(argv[1], "H(hello)"))
     H(hellosrc, hellosrc);
   else if (!strcmp(argv[1], "H(loop)"))
     H(loopsrc, loopsrc);
   else if (!strcmp(argv[1], "H(H_Hat)"))
     H(H_Hatsrc, H_Hatsrc);

   else if (!strcmp(argv[1], "hello"))
     hello(hellosrc);
   else if (!strcmp(argv[1], "loop"))
     loop(loopsrc);
   else if (!strcmp(argv[1], "H_Hat"))
     H_Hat(H_Hatsrc);
   else
      usage();

   printf("Terminating normally\n");

   return 0;
}

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


#24468 — 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:24 +0000
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<87eelk3nph.fsf@bsb.me.uk>
In reply to#24456
Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:

> On Monday, 26 October 2020 at 12:10:15 UTC, Ben Bacarisse wrote:
>
>> Generally I prefer code in these cases. An illustrative code sketch 
>> would surely have helped and can't be hard if the point is a simple one. 
>>
> #include <stdio.h>
> #include <stdlib.h>
> #include <string.h>
> #include <signal.h>
>
> int H(const char *src, const char *input)
> {
>    if (strstr(src, "printf"))
>    {
>       printf("Function will terminate normally\n");
>       return 0;
>    }
>    else
>    {
>       printf("Function will terminate when aborted\n");
>       kill(0, SIGINT);
>       return 1;
>    }
> }

So H(src, input) can only correct about the halting status of the
computation src(input) if strstr(src, "printf") is non-zero.  It could
be wrong in those cases, but it can't be correct any other way.  OK...

(Aside: I'd use !strstr(src, "while") as the dummy halting test, just to
hint at the sort of thing that might be expanded on in a real partial
decider.)

(Second aside: you've flipped the use of 0 an 1 from PO's code.  That's
slightly unfortunate.)

> void H_Hat(const char *input)
> {
>    if (!H(input, input))
>      while(1);
> }

Here I'm going to remove the other test cases just to keep things
simple.  And I'll put only the case in question into main...

> const char *H_Hatsrc = 
> "void H_Hat(const char *input)"
> "{"
> "   if (!H(input, input))"
> "     while(1);"
> "}";

> void handle_abort(int x)
> {
>   printf("Program terminated because aborted\n");
>   exit(0);
> }

int main(void)
{
      H(H_Hatsrc, H_Hatsrc);
      // never reached
      printf("Terminating normally\n");
}

So much clearer (to me) -- thank you.  The trouble is it that it's so
obviously not what was claimed because H(H_Hatsrc, H_Hatsrc) gives no
answer at all.  That, of course, is the point -- the trick -- but I
don't see how one can argue that H(H_Hatsrc, H_Hatsrc) is correct about
the halting of H_Hat(H_Hatsrc).

At least a game of words about it is possible, though.



A couple of technical things...

I think you improve the odds of winning the word game if you copy PO's
use of a global (eax is essentially a global variable):

int H_return;

void H(const char *src, const char *input)
{
   if (strstr(src, "printf"))
   {
      H_return = 0;
      printf("Function will terminate normally\n");
   }
   else
   {
      H_return = 1;
      printf("Function will terminate when aborted\n");
      kill(0, SIGINT);
   }
}

written like this, no one can say that H does not give (or indicate) an
answer.  OK, it still won't be seen, and it just indicates "the other
way of stopping" (so H should be indicating halting), but it does
obfuscate things a bit more.

Second, I think the sigaction mask code is wrong -- sa_mask can be a
struct.  Masking the signal being altered is the default, so you can
just omit that line.  But standard C would do, I think.

-- 
Ben.

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


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

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-26 10:38 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<0a832340-c796-49b4-bfa3-e54e5beaab1en@googlegroups.com>
In reply to#24468
On Monday, 26 October 2020 at 17:24:14 UTC, Ben Bacarisse wrote:
> Malcolm McLean <malcolm.ar...@gmail.com> writes: 
> 
> A couple of technical things... 
> 
> I think you improve the odds of winning the word game if you copy PO's 
> use of a global (eax is essentially a global variable): 
> 
> int H_return; 
> 
Yes, that's the next step. Unfortunately I don't have what PO calls a UTM, so I
can't easily make it clear that eax 0 = "abort". I do have a Unix-like system on
which there is a signal, which is an equivalent.
>
> void H(const char *src, const char *input) 
> { 
> if (strstr(src, "printf")) 
> { 
> H_return = 0;
> printf("Function will terminate normally\n"); 
> }
> else 
> { 
> H_return = 1;
> printf("Function will terminate when aborted\n"); 
> kill(0, SIGINT); 
> } 
> }
> written like this, no one can say that H does not give (or indicate) an 
> answer. OK, it still won't be seen, and it just indicates "the other 
> way of stopping" (so H should be indicating halting), but it does 
> obfuscate things a bit more. 
>
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). 
>
> Second, I think the sigaction mask code is wrong -- sa_mask can be a 
> struct. Masking the signal being altered is the default, so you can 
> just omit that line. But standard C would do, I think. 
> 
I had to look up signal handling code. It's not something I ever do in my
serious work.

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


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

Back to top | Article view | comp.theory


csiph-web