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


Groups > comp.lang.c > #155812 > 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-11-06 20:34 -0800
Articles 16 on this page of 256 — 15 participants

Back to article view | Back to comp.lang.c


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 ] "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2020-10-20 14:26 -0700
          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:41 +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 ] 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 ] 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 ] 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 ] "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2020-10-22 17:21 -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: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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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) [ 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 ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 03:28 -0700
                                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 ] 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 ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 08:07 -0700
                                      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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] olcott <NoOne@NoWhere.com> - 2020-10-22 19:09 -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-22 21: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-22 23:31 -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 20:36 -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 22:18 -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-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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 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 ] 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 ] 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 ] 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 ] 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 ] olcott <NoOne@NoWhere.com> - 2020-10-27 14:44 -0500
                                                                                  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 ] 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 ] 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 ] 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 ] 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 ] olcott <NoOne@NoWhere.com> - 2020-10-29 12:48 -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 13:57 -0600
                                            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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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-23 18:14 -0500
                                          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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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 ] olcott <NoOne@NoWhere.com> - 2020-10-25 10:33 -0500
                                                  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] olcott <NoOne@NoWhere.com> - 2020-10-25 16:07 -0500
                                                  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 ] 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 ] 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 ] 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 ] 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 ] 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-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 ] 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 ] 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 ] 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 ] 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 ] 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 ] 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-26 16:35 -0500
                                                                              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 ] 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 ] 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 ] 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 ] 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 ] 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 ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 03:18 -0700
                                              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 ] 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-24 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 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 ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-25 01:07 -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:07 -0500
                                      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 ] 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 ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 09:09 -0700
                                        Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 11: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-22 20:41 +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 ] 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 ] 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 ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:40 -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-21 22:42 +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 16:56 -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:25 +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 23:26 +0100
                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 [ 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) [ 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
    Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] audating801@gmail.com - 2020-11-06 20:34 -0800

Page 13 of 13 — ← Prev page 1 … 11 12 [13]


#155833

FromBen Bacarisse <ben.usenet@bsb.me.uk>
Date2020-10-22 00:25 +0100
Message-ID<87imb3cgbi.fsf@bsb.me.uk>
In reply to#155828
olcott <NoOne@NoWhere.com> writes:

> On 10/21/2020 4:42 PM, Ben Bacarisse wrote:
>> There's actually something topical in comp.lang.c...
>>
>> olcott <NoOne@NoWhere.com> writes:
>>
>>> As Ben has very carefully elaborated twice the invocation of a
>>> function with the same input must result in the same output. The
>>> return value from H_Hat() and the return value from H() are the same
>>> return value.
>>
>> That first sentence, attributed to me, is not true, and I hope I never
>> said it!  (If I did, post a message ID so I can post a correction,
>> please.)
>
> On 10/21/2020 8:36 AM, Ben Bacarisse wrote:
>> Yup.  But I want to nitpick...  It would be better to say that the
>> result of a Turing machine is determined solely by it's input.

Just as I thought, I never said what you claimed I did.  Whew!

-- 
Ben.

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


#155831

FromMike Terry <news.dead.person.stones@darjeeling.plus.com>
Date2020-10-21 23:26 +0100
Message-ID<95-dncsfWbgYKA3CnZ2dnUU78efNnZ2d@brightview.co.uk>
In reply to#155826
On 21/10/2020 22:42, Ben Bacarisse wrote:
> There's actually something topical in comp.lang.c...
>
> olcott <NoOne@NoWhere.com> writes:
>
>> As Ben has very carefully elaborated twice the invocation of a
>> function with the same input must result in the same output. The
>> return value from H_Hat() and the return value from H() are the same
>> return value.
>
> That first sentence, attributed to me, is not true, and I hope I never
> said it!  (If I did, post a message ID so I can post a correction,
> please.)
>
> You appear to writing C (or maybe C++), and in C, the invocation of a
> function with the same "input" does not necessarily result in the same
> "output", not unless the terms "input" and "output" are being stretched
> beyond all reason.
>

Exactly.

If we defined "input" to mean "everything that affects the behaviour of 
the function", then if two function calls have the same "input" they 
will behave exactly the same and produce the same output - it's pretty 
much a tautology (in the usual non-technical sense).  But that's NOT 
what people normally take "input" to mean.

In my case I was referring to calls to a function called with the same 
input parameters, which in itself is obviously no guarantee that they 
will give the same return code.

Mike.

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


#155835 — Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-21 21:14 -0500
SubjectRe: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ]
Message-ID<Bd6dnQgPu-h2dw3CnZ2dnUU7-bmdnZ2d@giganews.com>
In reply to#155821
On 10/21/2020 8:22 PM, Richard Damon wrote:
> On 10/21/20 12:48 PM, olcott wrote:
>> On 10/21/2020 10:28 AM, Mike Terry wrote:
>>>
>>> What DebugTrace does internally matters to you (because you are
>>> writing it), but not so much at this high level (which should turn out
>>> to be enough to see your overall claim will not succeed).
>>>
>>
>> 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?
>>
>> I have one more key element that can best be demonstrated by fully
>> functional code.
>>
> 
> Note, you do not have the 'right' to redefine the Halting Question, at
> least not if you want to be talking about the 'classical' Halt Decider
> and Linz's proof of impossibility.  The machine which he showed to be
> impossible was the machine that could be given the description of any
> Turing machine, and its input, and be able to ALWAYS tell, in finite
> time, if said machine with said input would halt, or if it would process
> forever an not halt.
> 
> Thus, the machine H, must never get stuck in an 'infinite loop' for any
> legal input.
> 
> If you have decided that as part of that implementation, that it somehow
> can detect that it has gotten itself in a loop and aborts that
> calculation, and declare that the described machine will not halt, it
> can, but that means that if someone can come up with a sufficiently
> complicated machine that triggers this condition when given to H, but if
> run by itself does eventual halt, that H wasn't the needed halt detector
> (but for Linz's proof, this isn't really needed, at the Linz H^ when it
> loops can be fairly easily detected,
> 
> Note, that your new wording seems to leave open some possibilities that
> are not allowed in the original construction:
> 
> The implementation of your function that implements the decision of H(),
> your DebugStep isn't allowed to know which program called it, but must
> return the same code to both H and H_Hat.
> 
> Your implementation of your function can't halt in and of itself, but
> MUST return the answer to its caller (The Turing machine H had just two
> terminal states, both of which were accounted for in H_Hat).
> 
> The answer that it returns needs to reflect what H_Hat actually ends up
> doing, and the program H_Hat needs to act in the manner that Linz described.
> 
> Note, that I don;'t really care how it actually gets the answer, as it
> only really needs to provide the answer for this one case, being given
> the machine/Input H_Hat/H_Hat, as far as I am concerned, Linz proof
> still holds even if the function is just a return 0;, or a return 1;
> 
> There are only a few things that are really important:
> 
> Both the calls to it in H and in H_Hat need to return the same value,
> and in finite time.
> 
> That H indicates the correct halting indication for H_Hat.
> 
> That H_Hat was constructed and executes per Linz's specification (It
> must halt if H will indicate that it looped, and it must loop if H will
> indicate it halted)
> 
> Any attempt to mark H_Hat is an 'improper program' will just prove
> Linz's statement, as if there IS an H, then the construction of H_Hat is
> clearly a legal modification, so any problems with it must have been
> contained in H, so saying H can't exist is exactly what Linz was trying
> to prove.
> 

When we make the single change that I suggest the halting problem ceases 
to be impossible to solve because this revised question is not subject 
to pathological self-reference.

All of the inputs are divided into halting and not halting and the halt 
decider cannot be fooled by a program based on itself that does the 
opposite of whatever it decides.

-- 
Copyright 2020 Pete Olcott

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-22 15:13 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<HN-dnen9u4FregzCnZ2dnUU7-QvNnZ2d@giganews.com>
In reply to#155835
On 10/22/2020 2:43 PM, André G. Isaak wrote:
> On 2020-10-22 08:41, olcott wrote:
>> On 10/22/2020 7:12 AM, Richard Damon wrote:
> 
>>> Your argument seems to basically devolve into redefining the Halt
>>> Detector definition to have a trinary output, Yes, it Halt, No it
>>> doesn't, or I can't determine because it 'cheats'. 
>>
>> No it is binary:
>> (a) Its execution was aborted because it would not otherwise halt.
>> (b) Its execution was allowed to continue until it terminated.
> 
> So how exactly does that avoid the contradiction inherent in Linz proof?
> 
> If the relation between your H and Ĥ is the same as in the Linz proof, 
> the same contradiction results despite your change of wording.
> 
> André
> 

If we keep everything in the Linz proof the same** except we change the 
name of what the halt decider decides:

(a) Decision:Not_Halting and
     Behavior:Halts (a contradiction)

(b) Decision:Aborted_Execution_Because_Not_Halting_Detected and
     Behavior:Aborted Execution (not a contradiction)

http://www.liarparadox.org/Peter_Linz_HP(Pages_315-320).pdf

** We also assume that the halt decider works on the basis of executing 
its input program in DebugStep() mode until it detects non-halting 
behavior or its input program terminates.

If the halt decider detects non halting behavior it immediately stops 
executing its input in DebugStep() mode and returns its Boolean value.

If it returns a value meaning Not_Halting then a contradiction of formed 
because its input program did halt.

If it returns a value meaning Aborted_Execution_Because_Not_Halting_Detected
then no contradiction is formed because its input program was aborted.




-- 
Copyright 2020 Pete Olcott

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


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

FromAndré G. Isaak <agisaak@gm.invalid>
Date2020-10-22 14:34 -0600
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<rmsqcj$1su$1@dont-email.me>
In reply to#155898
On 2020-10-22 14:13, olcott wrote:
> On 10/22/2020 2:43 PM, André G. Isaak wrote:
>> On 2020-10-22 08:41, olcott wrote:
>>> On 10/22/2020 7:12 AM, Richard Damon wrote:
>>
>>>> Your argument seems to basically devolve into redefining the Halt
>>>> Detector definition to have a trinary output, Yes, it Halt, No it
>>>> doesn't, or I can't determine because it 'cheats'. 
>>>
>>> No it is binary:
>>> (a) Its execution was aborted because it would not otherwise halt.
>>> (b) Its execution was allowed to continue until it terminated.
>>
>> So how exactly does that avoid the contradiction inherent in Linz proof?
>>
>> If the relation between your H and Ĥ is the same as in the Linz proof, 
>> the same contradiction results despite your change of wording.

No. If your H() returns 'terminated normally', then Ĥ(Ĥ) must have been 
forced to abort if they were really using the same halt deciding code.

And if your H() returns 'forced to abort', then Ĥ(Ĥ) must have 
terminated normally if they were really using the same halt deciding code.

The contradiction is there despite your change of wording.

André


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

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-22 16:28 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<5O-dnQAZ3MXuZAzCnZ2dnUU7-fdQAAAA@giganews.com>
In reply to#155900
On 10/22/2020 3:34 PM, André G. Isaak wrote:
> On 2020-10-22 14:13, olcott wrote:
>> On 10/22/2020 2:43 PM, André G. Isaak wrote:
>>> On 2020-10-22 08:41, olcott wrote:
>>>> On 10/22/2020 7:12 AM, Richard Damon wrote:
>>>
>>>>> Your argument seems to basically devolve into redefining the Halt
>>>>> Detector definition to have a trinary output, Yes, it Halt, No it
>>>>> doesn't, or I can't determine because it 'cheats'. 
>>>>
>>>> No it is binary:
>>>> (a) Its execution was aborted because it would not otherwise halt.
>>>> (b) Its execution was allowed to continue until it terminated.
>>>
>>> So how exactly does that avoid the contradiction inherent in Linz proof?
>>>
>>> If the relation between your H and Ĥ is the same as in the Linz 
>>> proof, the same contradiction results despite your change of wording.
> 
> No. If your H() returns 'terminated normally', then Ĥ(Ĥ) must have been 
> forced to abort if they were really using the same halt deciding code.
> 
> And if your H() returns 'forced to abort', then Ĥ(Ĥ) must have 
> terminated normally if they were really using the same halt deciding code.

bool DebugTrace() only returns forced to abort or not forced to abort.

-- 
Copyright 2020 Pete Olcott

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


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

FromAndré G. Isaak <agisaak@gm.invalid>
Date2020-10-22 15:34 -0600
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<rmstsp$qhl$1@dont-email.me>
In reply to#155901
On 2020-10-22 15:28, olcott wrote:
> On 10/22/2020 3:34 PM, André G. Isaak wrote:
>> On 2020-10-22 14:13, olcott wrote:
>>> On 10/22/2020 2:43 PM, André G. Isaak wrote:
>>>> On 2020-10-22 08:41, olcott wrote:
>>>>> On 10/22/2020 7:12 AM, Richard Damon wrote:
>>>>
>>>>>> Your argument seems to basically devolve into redefining the Halt
>>>>>> Detector definition to have a trinary output, Yes, it Halt, No it
>>>>>> doesn't, or I can't determine because it 'cheats'. 
>>>>>
>>>>> No it is binary:
>>>>> (a) Its execution was aborted because it would not otherwise halt.
>>>>> (b) Its execution was allowed to continue until it terminated.
>>>>
>>>> So how exactly does that avoid the contradiction inherent in Linz 
>>>> proof?
>>>>
>>>> If the relation between your H and Ĥ is the same as in the Linz 
>>>> proof, the same contradiction results despite your change of wording.
>>
>> No. If your H() returns 'terminated normally', then Ĥ(Ĥ) must have 
>> been forced to abort if they were really using the same halt deciding 
>> code.
>>
>> And if your H() returns 'forced to abort', then Ĥ(Ĥ) must have 
>> terminated normally if they were really using the same halt deciding 
>> code.
> 
> bool DebugTrace() only returns forced to abort or not forced to abort.

So replace 'terminated normally' with 'not forced to abort' in what I 
say above. There is still a contradiction.

André

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

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


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

Fromolcott <NoOne@NoWhere.com>
Date2020-10-22 16:47 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<YOWdnXlXy4GRYwzCnZ2dnUU7-TfNnZ2d@giganews.com>
In reply to#155902
On 10/22/2020 4:34 PM, André G. Isaak wrote:
> On 2020-10-22 15:28, olcott wrote:
>> On 10/22/2020 3:34 PM, André G. Isaak wrote:
>>> On 2020-10-22 14:13, olcott wrote:
>>>> On 10/22/2020 2:43 PM, André G. Isaak wrote:
>>>>> On 2020-10-22 08:41, olcott wrote:
>>>>>> On 10/22/2020 7:12 AM, Richard Damon wrote:
>>>>>
>>>>>>> Your argument seems to basically devolve into redefining the Halt
>>>>>>> Detector definition to have a trinary output, Yes, it Halt, No it
>>>>>>> doesn't, or I can't determine because it 'cheats'. 
>>>>>>
>>>>>> No it is binary:
>>>>>> (a) Its execution was aborted because it would not otherwise halt.
>>>>>> (b) Its execution was allowed to continue until it terminated.
>>>>>
>>>>> So how exactly does that avoid the contradiction inherent in Linz 
>>>>> proof?
>>>>>
>>>>> If the relation between your H and Ĥ is the same as in the Linz 
>>>>> proof, the same contradiction results despite your change of wording.
>>>
>>> No. If your H() returns 'terminated normally', then Ĥ(Ĥ) must have 
>>> been forced to abort if they were really using the same halt deciding 
>>> code.
>>>
>>> And if your H() returns 'forced to abort', then Ĥ(Ĥ) must have 
>>> terminated normally if they were really using the same halt deciding 
>>> code.
>>
>> bool DebugTrace() only returns forced to abort or not forced to abort.
> 
> So replace 'terminated normally' with 'not forced to abort' in what I 
> say above. There is still a contradiction.
> 
> André
> 


(1) Original self-referential halting problem counter example
    (a) Decision: ~Halting and Behavior: Halts (a contradiction)
    (b) Decision:  Halting and Behavior: Loops (a contradiction)

(2) Revised halting problem decision
    (a) Decision:  Aborted_Execution and Behavior:  Aborted Execution
    (b) Decision: ~Aborted_Execution and Behavior: ~Aborted Execution

In the first case the decision and the behavior contradict each other.
In the second case the decision and the behavior DO NOT contradict each 
other.

It is only hard if it is welded into your brain that I must be wrong.



-- 
Copyright 2020 Pete Olcott

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


#155869

FromMr Flibble <flibbleREMOVETHISBIT@i42.co.uk>
Date2020-10-22 17:54 +0100
Message-ID<4PikH.234424$rm5.2218@fx31.am4>
In reply to#155812
On 20/10/2020 17:33, olcott wrote:
> x86utm is as much as possible a Universal Turing Machine UTM that has the x86 language as its Turing Machine Description language.

Occam's Razor suggests that my assumption that Turing is correct and you, random Usenet person, are incorrect is a fair assumption so I don't have the time to read your refutation.  If your "solution" to the HP is an "oracle" then:

"A machine with an oracle for the halting problem can determine whether particular Turing machines will halt on particular inputs, but they cannot determine, in general, if machines equivalent to themselves will halt."

/Flibble

-- 
¬

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


#155871

Fromolcott <NoOne@NoWhere.com>
Date2020-10-22 11:57 -0500
Message-ID<UeSdnScn4MGRJwzCnZ2dnUU7-S2dnZ2d@giganews.com>
In reply to#155869
On 10/22/2020 11:54 AM, Mr Flibble wrote:
> On 20/10/2020 17:33, olcott wrote:
>> x86utm is as much as possible a Universal Turing Machine UTM that has 
>> the x86 language as its Turing Machine Description language.
> 
> Occam's Razor suggests that my assumption that Turing is correct and 

Perhaps you are totally unaware that Occam's Razor is merely a heuristic 
used to save time and money and no aspect what-so-ever of correct 
reasoning.

> you, random Usenet person, are incorrect is a fair assumption so I don't 
> have the time to read your refutation.  If your "solution" to the HP is 
> an "oracle" then:
> 
> "A machine with an oracle for the halting problem can determine whether 
> particular Turing machines will halt on particular inputs, but they 
> cannot determine, in general, if machines equivalent to themselves will 
> halt."
> 
> /Flibble
> 


-- 
Copyright 2020 Pete Olcott

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


#155872

FromMr Flibble <flibbleREMOVETHISBIT@i42.co.uk>
Date2020-10-22 18:05 +0100
Message-ID<OZikH.243888$B8s1.193758@fx15.am4>
In reply to#155871
On 22/10/2020 17:57, olcott wrote:
> On 10/22/2020 11:54 AM, Mr Flibble wrote:
>> On 20/10/2020 17:33, olcott wrote:
>>> x86utm is as much as possible a Universal Turing Machine UTM that has the x86 language as its Turing Machine Description language.
>>
>> Occam's Razor suggests that my assumption that Turing is correct and 
> 
> Perhaps you are totally unaware that Occam's Razor is merely a heuristic used to save time and money and no aspect what-so-ever of correct reasoning.

Yes I am aware that it a heuristic which I can use to decide on what I spend my time doing or thinking about. Life is fucking finite and time is fucking precious, mate, and there is no fucking afterlife. Stop wasting our time.

/Flibble

-- 
¬

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


#155894

FromJoe Pfeiffer <pfeiffer@cs.nmsu.edu>
Date2020-10-22 12:55 -0600
Message-ID<1bd01adra3.fsf@pfeifferfamily.net>
In reply to#155872
Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> writes:

> On 22/10/2020 17:57, olcott wrote:
>> On 10/22/2020 11:54 AM, Mr Flibble wrote:
>>> On 20/10/2020 17:33, olcott wrote:
>>>> x86utm is as much as possible a Universal Turing Machine UTM that
>>>> has the x86 language as its Turing Machine Description language.
>>>
>>> Occam's Razor suggests that my assumption that Turing is correct
>>> and 
>>
>> Perhaps you are totally unaware that Occam's Razor is merely a
>> heuristic used to save time and money and no aspect what-so-ever of
>> correct reasoning.
>
> Yes I am aware that it a heuristic which I can use to decide on what I
> spend my time doing or thinking about. Life is fucking finite and time
> is fucking precious, mate, and there is no fucking afterlife. Stop
> wasting our time.

Crackpots will always be among us.  There is no one to blame for
engaging this one but yourself.  You've established he's not worth your
time; let those who wish to try to teach the unteachable spend their
time as they wish.  Killfile him and move on.

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


#155895

FromMr Flibble <flibbleREMOVETHISBIT@i42.co.uk>
Date2020-10-22 19:59 +0100
Message-ID<3EkkH.11913$W14.26@fx03.am4>
In reply to#155894
On 22/10/2020 19:55, Joe Pfeiffer wrote:
> Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> writes:
> 
>> On 22/10/2020 17:57, olcott wrote:
>>> On 10/22/2020 11:54 AM, Mr Flibble wrote:
>>>> On 20/10/2020 17:33, olcott wrote:
>>>>> x86utm is as much as possible a Universal Turing Machine UTM that
>>>>> has the x86 language as its Turing Machine Description language.
>>>>
>>>> Occam's Razor suggests that my assumption that Turing is correct
>>>> and
>>>
>>> Perhaps you are totally unaware that Occam's Razor is merely a
>>> heuristic used to save time and money and no aspect what-so-ever of
>>> correct reasoning.
>>
>> Yes I am aware that it a heuristic which I can use to decide on what I
>> spend my time doing or thinking about. Life is fucking finite and time
>> is fucking precious, mate, and there is no fucking afterlife. Stop
>> wasting our time.
> 
> Crackpots will always be among us.  There is no one to blame for
> engaging this one but yourself.  You've established he's not worth your
> time; let those who wish to try to teach the unteachable spend their
> time as they wish.  Killfile him and move on.

You are right: I have wasted enough time on this troll (assuming he is a troll and not simply batshit crazy like you suggest).

/Flibble

-- 
¬

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


#155896

FromLew Pitcher <lew.pitcher@digitalfreehold.ca>
Date2020-10-22 19:13 +0000
Message-ID<rmslk2$9bb$1@dont-email.me>
In reply to#155895
On Thu, 22 Oct 2020 19:59:17 +0100, Mr Flibble wrote:

> On 22/10/2020 19:55, Joe Pfeiffer wrote:
[snip]
>> Crackpots will always be among us.  There is no one to blame for
>> engaging this one but yourself.  You've established he's not worth your
>> time; let those who wish to try to teach the unteachable spend their
>> time as they wish.  Killfile him and move on.
> 
> You are right: I have wasted enough time on this troll (assuming he is a
> troll and not simply batshit crazy like you suggest).

In this case, there doesn't seem to be much of a difference. He passed 
the "duck test" ("If it looks like a duck, and quacks like a duck, then 
we can call it a duck."), anyway.

-- 
Lew Pitcher
"In Skills, We Trust"

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


#156246 — Stop crossposting you imbecil spammer (Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ])

FromMostowski Collapse <janburse@fastmail.fm>
Date2020-10-29 14:01 +0100
SubjectStop crossposting you imbecil spammer (Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ])
Message-ID<rneefd$d0j$3@solani.org>
In reply to#155812
For gods sacke stop cross posting on 4 newsgroups.

Especially comp.lang.prolog doesn't make much sense.

RAM/RASP is probably best housed on comp.theory.

olcott schrieb:
 > I am a complete imbecial spammer

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


#156530

Fromaudating801@gmail.com
Date2020-11-06 20:34 -0800
Message-ID<6a29d679-fcdf-4e0c-aa41-45473a8a639fo@googlegroups.com>
In reply to#155812
On Tuesday, October 20, 2020 at 10:03:42 PM UTC+5:30, olcott wrote:
> x86utm is as much as possible a Universal Turing Machine UTM that has 
> the x86 language as its Turing Machine Description language.
> 
> It is common knowledge that the RASP architecture is equivalent to a 
> universal Turing machine. It is self-evident that the x86 language is a 
> finite implementation of the Random Access Stored Program (RASP) model.
> 
> x86 UTM has these four key operating system functions providing the 
> functionality to transform an x86 emulator into a finite Universal 
> Turing Machine: (Source code will be provided)
> 
> u32* Allocate(u32 size); // Allocate bytes of memory
> void SaveState(Registers* state);
> void LoadState(Registers* state);
> u32  DebugStep(Registers* master_state, Registers* slave_state);
> 
> To make x86utm easy to use it directly executes the COFF object file 
> output of the Microsoft C compiler. The entire x86UTM system works on 
> both Windows and Linux. It will also directly execute the output of the 
> GCC compiler when this output has been converted to the COFF format. An 
> open source utility is provided for this purpose.
> 
> x86utm is based on a very superb x86 emulator. The only change the 
> needed to be made to the emulator was to very slightly adapt it to 
> compile under windows and add the feature of disassembling an object 
> file. All of the adaptations to transform this emulator into a master 
> UTM are contained in a single C++ source file.
> 
> Here is how x86UTM is applied to the Peter Linz H() and H_Hat() to 
> correctly decide halting of H_Hat()
> 
> H() continues to DebugStep() though H_Hat() until H_Hat() terminates or
> H() decides that H_Hat() would not otherwise terminate. In this case H()
> would stop executing H_Hat() and report Not_Halting behavior.
> 
> H() executes H_Hat() as if H() was a UTM. H() and H_Hat() are separate 
> processes having their own: {Memory, registers and stack}
> To make things simple the halt deciding aspect of H() and H_Hat() is the 
> same function. (see below)
> 
> #define HALT __asm hlt
> // N and M have address of H_Hat()
> int H(u32 M, u32 N)
> {
>    int Abort = DebugTrace(M, N);
>    if (Abort)
>    {
>      MOV_EAX_0
>      HALT
>    }
>    else
>    {
>      MOV_EAX_1
>      HALT
>    }
> }
> 
> 
> int main()
> {
>    u32 M = (u32)H_Hat;
>    H(M, M);
>    HALT;
> }
> 
> 
> -- 
> Copyright 2020 Pete Olcott

[toc] | [prev] | [standalone]


Page 13 of 13 — ← Prev page 1 … 11 12 [13]

Back to top | Article view | comp.lang.c


csiph-web