Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch > #111650 > unrolled thread
| Started by | quadibloc <quadibloc@gmail.com> |
|---|---|
| First post | 2025-05-19 19:15 +0000 |
| Last post | 2025-06-19 01:03 +0000 |
| Articles |
20 on this page of 1000+
— 49 participants
Thread has 1028 articles; only the first 1000 are indexed. |
Back to article view | Back to comp.arch | Browse in flat view
Thread has 1028 articles; showing the first 1000 in depth-first order. Use the flat group view to see the rest.
Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-05-19 19:15 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-05-19 21:26 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-05-21 15:07 +0000
Re: Why I've Dropped In David Chmelik <dchmelik@gmail.com> - 2025-05-22 06:51 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-05-22 17:42 +0000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-05-22 18:03 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-05-23 12:37 +0000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-05-23 13:24 +0000
Re: Why I've Dropped In John Savard <quadibloc@invalid.invalid> - 2025-07-26 05:57 +0000
Re: Why I've Dropped In John Savard <quadibloc@invalid.invalid> - 2025-07-26 06:14 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-10 21:45 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-10 22:45 -0500
Re: Why I've Dropped In John Savard <quadibloc@invalid.invalid> - 2025-08-01 04:42 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-08-01 05:03 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-08-01 18:07 -0500
Re: Why I've Dropped In MitchAlsup <user5857@newsgrouper.org.invalid> - 2025-08-27 01:01 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-11 17:19 +0000
Re: Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-11 12:16 -0700
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-12 02:11 +0000
Re: Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-12 11:48 -0700
Re: Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-15 17:26 -0700
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-12 08:00 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-10 22:53 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-11 05:56 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-11 04:42 -0500
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-11 16:37 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-11 14:47 -0500
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-12 19:13 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-12 16:30 -0500
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-13 00:00 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-15 13:21 -0500
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-15 18:42 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-15 16:42 -0500
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-11 16:51 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-11 19:08 +0000
Re: Why I've Dropped In EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-11 18:00 -0400
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-11 23:01 +0000
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-12 08:38 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-12 18:44 +0000
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-20 05:56 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-12 19:55 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-11 16:28 -0500
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-12 07:05 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-12 15:27 -0500
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-20 15:30 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-20 15:59 +0000
Re: Why I've Dropped In moi <findlaybill@blueyonder.co.uk> - 2025-06-20 17:12 +0100
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-20 19:46 +0000
Re: Why I've Dropped In John Savard <quadibloc@invalid.invalid> - 2025-07-23 16:03 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-11 14:12 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-11 16:49 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-11 17:34 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-11 19:16 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-14 14:22 -0500
Re: Why I've Dropped In Stefan Monnier <monnier@iro.umontreal.ca> - 2025-06-16 12:17 -0400
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-17 01:07 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-16 18:26 -0700
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-17 17:45 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-17 11:09 -0700
Re: Why I've Dropped In Stefan Monnier <monnier@iro.umontreal.ca> - 2025-06-17 16:43 -0400
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-17 21:18 +0000
Re: Why I've Dropped In Stefan Monnier <monnier@iro.umontreal.ca> - 2025-06-17 18:14 -0400
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-18 07:31 +0000
Re: Why I've Dropped In Stefan Monnier <monnier@iro.umontreal.ca> - 2025-06-18 11:50 -0400
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-19 08:56 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-18 15:37 -0500
Re: Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-18 00:47 -0700
Re: Why I've Dropped In Stefan Monnier <monnier@iro.umontreal.ca> - 2025-06-18 11:22 -0400
Re: Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-19 21:45 -0700
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-11 17:05 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-12 15:00 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-12 08:44 -0700
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-13 03:09 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-12 20:36 -0700
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-13 06:03 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-13 11:14 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-13 08:23 -0700
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-13 17:40 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-13 10:57 -0700
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-13 18:11 +0000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-13 18:18 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-13 18:42 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-14 20:31 -0700
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-15 15:55 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-13 11:55 -0700
Re: base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-15 17:15 +0000
Re: base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-15 12:17 -0700
Re: base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-15 19:44 +0000
Re: base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-15 20:09 +0000
Re: base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-15 21:02 -0700
Re: base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-16 14:37 +0000
Re: base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-16 07:55 -0700
Re: base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-16 17:42 +0000
Re: base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-16 10:56 -0700
Re: base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-16 21:52 +0000
Re: base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-16 15:04 -0700
Re: base and bounds, Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-16 18:11 +0000
Re: base and bounds, Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-16 14:25 +0000
Re: base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-16 14:45 +0000
Re: base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-15 14:39 -0700
Re: base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-16 02:33 +0000
Re: base and bounds, Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-16 14:22 +0000
Re: big pages, base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-16 16:42 +0000
Re: big pages, base and bounds, Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-16 16:52 +0000
Re: Why I've Dropped In Lars Poulsen <lars@cleo.beagle-ears.com> - 2025-06-13 19:49 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-13 18:37 +0000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-13 21:09 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-13 20:27 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-14 10:48 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-14 09:45 -0700
Re: Why I've Dropped In EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-14 13:56 -0400
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-14 12:23 -0700
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-14 21:26 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-14 14:37 -0700
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-14 21:49 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-14 20:34 -0700
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-15 03:52 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-15 04:04 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-15 04:09 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-15 04:38 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-15 07:37 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-15 07:00 -0700
Re: swapping pain, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-15 17:39 +0000
Re: swapping pain, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-15 12:23 -0700
Re: base hackery, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-15 17:22 +0000
Re: Why I've Dropped In EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-15 09:48 -0400
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-14 18:51 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-14 12:33 -0700
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-14 20:06 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-15 19:29 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-18 09:55 -0700
Re: more addressing, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-18 18:19 +0000
Re: more addressing, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-18 12:07 -0700
Re: more addressing, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-19 06:13 +0000
Re: more addressing, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-18 23:39 -0700
Re: more addressing, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-19 07:46 +0000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-13 13:14 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-13 11:52 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-13 08:15 -0700
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-13 19:50 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-13 13:50 -0700
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-13 22:01 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-13 23:10 -0700
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-14 09:26 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-14 10:44 +0000
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-14 15:40 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-14 09:24 -0700
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-14 16:49 +0000
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-14 16:39 +0000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-15 01:07 +0000
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-15 07:10 +0000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-15 16:01 +0000
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-15 16:53 +0000
Re: static linked libraries, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-15 17:54 +0000
Re: Why I've Dropped In Robert Swindells <rjs@fdy2.co.uk> - 2025-06-15 19:24 +0000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-16 14:15 +0000
Re: static libraries, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-15 17:00 +0000
Re: Why I've Dropped In John Savard <quadibloc@invalid.invalid> - 2025-07-24 10:47 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-14 16:56 +0000
Re: Why I've Dropped In Lars Poulsen <lars@cleo.beagle-ears.com> - 2025-06-14 12:42 +0000
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-14 15:53 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-14 17:02 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-14 21:19 +0000
Re: fitting programs in Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-14 22:12 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-14 20:51 -0700
Re: base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-15 18:08 +0000
Re: base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-15 12:38 -0700
Re: old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-15 20:20 +0000
Re: old and slow base and bounds, Why I've Dropped In Al Kossow <aek@bitsavers.org> - 2025-06-15 18:48 -0700
Re: old and slow base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-18 10:35 -0700
Re: old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-18 19:51 +0000
Re: old and slow base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-18 15:30 -0700
Re: old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-19 01:23 +0000
Re: old and slow base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-18 19:41 -0700
Re: old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-19 05:36 +0000
Re: old and slow base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-18 23:10 -0700
Re: old and slow base and bounds, Why I've Dropped In EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-19 09:35 -0400
Re: old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-19 15:11 +0000
Re: Fortran, old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-19 18:03 +0000
Re: old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-19 18:53 +0000
Re: old and slow base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-19 23:18 +0000
Re: old and slow base and bounds, Why I've Dropped In EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-20 15:13 -0400
Re: old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-20 20:35 +0000
Re: old and slow base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-20 21:27 +0000
Re: old and slow base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-20 21:09 +0000
Re: old and slow base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-20 21:48 +0000
Re: old and slow base and bounds, Why I've Dropped In EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-21 14:57 -0400
Re: old and slow base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-19 23:36 +0000
Re: old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-20 01:32 +0000
Re: old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-20 13:45 +0000
Re: old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-20 17:19 +0000
Re: old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-20 18:06 +0000
Re: old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-20 18:31 +0000
Re: old and slow base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-20 12:27 -0700
Re: emulation, old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-20 20:16 +0000
Re: emulation, old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-20 20:47 +0000
Re: old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-20 21:26 +0000
Re: old and slow base and bounds, Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-21 14:33 +0000
Re: old and slow base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-20 21:34 +0000
Re: old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-20 23:57 +0000
Re: old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-21 00:06 +0000
Re: old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-21 00:13 +0000
Re: old and slow base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-20 23:20 -0700
Re: old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-21 07:40 +0000
Killer Micros (was: old and slow base and bounds) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-21 09:56 +0000
Re: old and slow base and bounds, Why I've Dropped In antispam@fricas.org (Waldek Hebisch) - 2025-06-21 14:25 +0000
Re: old and slow base and bounds, Why I've Dropped In Stefan Monnier <monnier@iro.umontreal.ca> - 2025-06-21 11:39 -0400
Re: old and slow base and bounds, Why I've Dropped In Vir Campestris <vir.campestris@invalid.invalid> - 2025-06-21 16:50 +0100
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-21 17:59 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-21 18:26 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-21 19:37 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In Lars Poulsen <lars@cleo.beagle-ears.com> - 2025-06-21 20:27 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-21 20:31 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-21 20:36 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-21 14:27 -0700
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In Terje Mathisen <terje.mathisen@tmsw.no> - 2025-06-24 09:45 +0200
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-22 06:34 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In Andreas Eder <a_eder_muc@web.de> - 2025-06-22 11:52 +0200
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-22 00:55 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In Vir Campestris <vir.campestris@invalid.invalid> - 2025-07-01 14:22 +0100
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-07-01 17:39 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-07-01 18:00 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In antispam@fricas.org (Waldek Hebisch) - 2025-06-22 20:23 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In Lynn Wheeler <lynn@garlic.com> - 2025-06-22 12:15 -1000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-22 22:44 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-23 09:23 -0400
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-23 20:04 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-23 23:16 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In Al Kossow <aek@bitsavers.org> - 2025-06-23 17:02 -0700
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-24 00:25 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-24 00:53 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-24 02:49 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-24 06:21 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In Terje Mathisen <terje.mathisen@tmsw.no> - 2025-06-24 09:59 +0200
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-24 06:16 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In antispam@fricas.org (Waldek Hebisch) - 2025-06-24 14:12 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In Al Kossow <aek@bitsavers.org> - 2025-06-24 07:43 -0700
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-24 14:53 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-24 14:48 +0000
Re: mainframe vs mini, old and slow base and bounds, Why I've Dropped In EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-24 13:01 -0400
Re: old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-21 17:49 +0000
Re: old and slow base and bounds, Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-21 14:36 +0000
Re: old and slow base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-19 13:37 +0000
Re: old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-19 17:52 +0000
Re: old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-19 19:00 +0000
Re: old and slow base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-20 07:42 -0700
Re: cramming 24 bits of address into 16 bits, was old and slow base and bounds John Levine <johnl@taugh.com> - 2025-06-20 18:40 +0000
Re: cramming 24 bits of address into 16 bits, was old and slow base and bounds EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-20 17:15 -0400
Re: cramming 24 bits of address into 16 bits, was old and slow base and bounds Thomas Koenig <tkoenig@netcologne.de> - 2025-06-20 21:30 +0000
Re: cramming 24 bits of address into 16 bits, was old and slow base and bounds John Levine <johnl@taugh.com> - 2025-06-21 17:21 +0000
Re: cramming 24 bits of address into 16 bits, was old and slow base and bounds EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-21 15:46 -0400
Re: cramming 24 bits of address into 16 bits, was old and slow base and bounds Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-21 22:42 -0700
Re: cramming 24 bits of address into 16 bits, was old and slow base and bounds Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-24 10:58 -0700
Re: cramming 24 bits of address into 16 bits, was old and slow base and bounds John Levine <johnl@taugh.com> - 2025-06-24 19:31 +0000
Re: old and slow base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-19 12:36 -0700
Re: old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-19 21:45 +0000
Re: old and slow base and bounds, Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-19 16:05 -0700
Re: old and slow base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-19 23:45 +0000
Re: old and slow base and bounds, Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-20 14:51 +0000
Re: old and slow base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-20 15:55 +0000
Re: old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-19 20:25 +0000
Re: old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-19 12:12 +0000
Re: old and slow base and bounds, Why I've Dropped In EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-19 10:32 -0400
Re: old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-19 14:54 +0000
Re: old and slow base and bounds, Why I've Dropped In EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-19 20:36 -0400
Re: old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-20 01:10 +0000
Re: old and slow base and bounds, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-20 01:15 +0000
Re: old and slow base and bounds, Why I've Dropped In antispam@fricas.org (Waldek Hebisch) - 2025-06-21 12:04 +0000
Re: old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-21 20:32 +0000
Re: old and slow base and bounds, Why I've Dropped In antispam@fricas.org (Waldek Hebisch) - 2025-06-22 01:26 +0000
Re: old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-22 01:36 +0000
Re: old and slow base and bounds, Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-22 08:57 +0000
Re: linking and sortiing, old and slow base and bounds, John Levine <johnl@taugh.com> - 2025-06-22 17:52 +0000
Re: linking and sortiing, old and slow base and bounds, mitchalsup@aol.com (MitchAlsup1) - 2025-06-22 18:25 +0000
Re: linking and sortiing, old and slow base and bounds, scott@slp53.sl.home (Scott Lurndal) - 2025-06-22 20:29 +0000
Re: tape hacks, linking and sortiing John Levine <johnl@taugh.com> - 2025-06-22 22:44 +0000
Re: linking and sortiing, old and slow base and bounds, Thomas Koenig <tkoenig@netcologne.de> - 2025-06-23 06:07 +0000
Re: linking and sortiing, old and slow base and bounds, quadibloc <quadibloc@gmail.com> - 2025-06-23 09:56 +0000
Re: linking and sortiing, old and slow base and bounds, quadibloc <quadibloc@gmail.com> - 2025-06-23 10:01 +0000
Re: linking and sortiing, old and slow base and bounds, Thomas Koenig <tkoenig@netcologne.de> - 2025-06-23 17:13 +0000
Re: old and slow base and bounds, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-22 01:31 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-14 17:00 +0000
Re: Why I've Dropped In John Savard <quadibloc@invalid.invalid> - 2025-07-28 23:18 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-07-28 22:56 -0500
Re: Why I've Dropped In MitchAlsup <user5857@newsgrouper.org.invalid> - 2025-08-26 21:46 +0000
VAX (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-29 08:45 +0000
Re: VAX (was: Why I've Dropped In) John Levine <johnl@taugh.com> - 2025-07-29 16:44 +0000
Re: VAX (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-30 05:59 +0000
Re: VAX BGB <cr88192@gmail.com> - 2025-07-30 04:02 -0500
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-07-30 16:24 +0000
Re: VAX BGB <cr88192@gmail.com> - 2025-07-30 13:24 -0500
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-01 17:02 +0000
Re: VAX BGB <cr88192@gmail.com> - 2025-08-01 15:24 -0500
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-02 15:33 +0000
Re: VAX BGB <cr88192@gmail.com> - 2025-08-02 15:15 -0500
Re: VAX BGB <cr88192@gmail.com> - 2025-08-02 18:55 -0500
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-04 16:33 +0000
Re: VAX MitchAlsup <user5857@newsgrouper.org.invalid> - 2025-08-25 00:56 +0000
Re: VAX MitchAlsup <user5857@newsgrouper.org.invalid> - 2025-08-31 18:04 +0000
What is more important MitchAlsup <user5857@newsgrouper.org.invalid> - 2025-09-04 15:23 +0000
Re: What is more important Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-09-04 10:25 -0700
Re: What is more important MitchAlsup <user5857@newsgrouper.org.invalid> - 2025-09-04 21:00 +0000
Re: What is more important BGB <cr88192@gmail.com> - 2025-09-04 16:54 -0500
Re: What is more important anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-09-05 15:03 +0000
Re: What is more important BGB <cr88192@gmail.com> - 2025-09-05 14:26 -0500
Re: What is more important BGB <cr88192@gmail.com> - 2025-09-05 14:38 -0500
Re: What is more important Robert Finch <robfi680@gmail.com> - 2025-09-05 21:56 -0400
Re: What is more important Thomas Koenig <tkoenig@netcologne.de> - 2025-09-10 13:31 +0000
Re: VAX (was: Why I've Dropped In) Lars Poulsen <lars@cleo.beagle-ears.com> - 2025-07-30 17:17 +0000
Re: VAX (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-01 17:16 +0000
Re: VAX (was: Why I've Dropped In) scott@slp53.sl.home (Scott Lurndal) - 2025-08-01 18:11 +0000
Re: VAX (was: Why I've Dropped In) cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-01 20:41 +0000
Re: VAX (was: Why I've Dropped In) Thomas Koenig <tkoenig@netcologne.de> - 2025-08-02 09:07 +0000
Re: VAX (was: Why I've Dropped In) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-02 23:21 +0000
Re: VAX Stefan Monnier <monnier@iro.umontreal.ca> - 2025-08-02 23:10 -0400
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-03 09:14 +0000
Re: VAX Peter Flass <Peter@Iron-Spring.com> - 2025-08-03 07:41 -0700
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-06 10:24 +0000
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 23:40 +0000
Re: VAX John Ames <commodorejohn@gmail.com> - 2025-08-04 08:32 -0700
Re: VAX BGB <cr88192@gmail.com> - 2025-08-04 11:47 -0500
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-04 17:20 +0000
Re: 32 vs 64 bits, was VAX John Levine <johnl@taugh.com> - 2025-08-04 18:17 +0000
Re: 32 vs 64 bits, was VAX Michael S <already5chosen@yahoo.com> - 2025-08-04 22:17 +0300
Re: 32 vs 64 bits, was VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-05 01:36 +0000
Re: 32 vs 64 bits, was VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-04 20:00 +0000
Re: IBM's 32 vs 64 bits, was VAX John Levine <johnl@taugh.com> - 2025-08-04 21:04 +0000
Re: IBM's 32 vs 64 bits, was VAX Lynn Wheeler <lynn@garlic.com> - 2025-08-07 07:32 -1000
Re: VAX Stefan Monnier <monnier@iro.umontreal.ca> - 2025-08-04 15:40 -0400
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-06 16:34 +0000
Re: VAX Stefan Monnier <monnier@iro.umontreal.ca> - 2025-08-31 16:43 -0400
Re: VAX Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-31 22:26 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-09-01 06:07 +0000
Re: VAX Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-09-01 06:57 +0000
Debian on AMD64 (was: VAX) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-09-01 07:40 +0000
Re: Debian on AMD64 Stefan Monnier <monnier@iro.umontreal.ca> - 2025-09-01 12:15 -0400
Re: Debian on AMD64 BGB <cr88192@gmail.com> - 2025-09-01 11:33 -0500
Re: Debian on AMD64 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-09-01 20:34 +0000
Re: VAX Marco Moock <mm@dorfdsl.de> - 2025-09-21 16:20 +0200
Re: VAX Nuno Silva <nunojsilva@invalid.invalid> - 2025-09-21 15:45 +0100
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-09-21 17:54 +0300
Re: VAX Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-08-04 14:06 -0700
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-05 00:21 +0300
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-04 21:51 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-04 23:38 +0000
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-05 01:39 +0000
Re: VAX "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-08-05 09:25 +0100
Re: VAX Terje Mathisen <terje.mathisen@tmsw.no> - 2025-08-05 17:24 +0200
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-05 15:41 +0000
System calls (was: VAX) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-13 07:32 +0000
Re: System calls (was: VAX) scott@slp53.sl.home (Scott Lurndal) - 2025-08-13 15:03 +0000
Re: System calls (was: VAX) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-13 16:10 +0000
Re: System calls (was: VAX) scott@slp53.sl.home (Scott Lurndal) - 2025-08-13 18:15 +0000
Re: System calls (was: VAX) cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-13 19:40 +0000
Re: System calls (was: VAX) cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-13 19:25 +0000
Re: System calls (was: VAX) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-13 21:23 +0000
Re: System calls (was: VAX) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-14 07:58 +0000
Re: System calls (was: VAX) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-14 13:28 +0000
Re: System calls (was: VAX) cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-14 15:14 +0000
Re: System calls (was: VAX) cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-14 15:25 +0000
Re: System calls (was: VAX) scott@slp53.sl.home (Scott Lurndal) - 2025-08-14 15:32 +0000
Re: System calls (was: VAX) cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-14 15:44 +0000
Re: System calls David Brown <david.brown@hesbynett.no> - 2025-08-14 19:15 +0200
Re: System calls Thomas Koenig <tkoenig@netcologne.de> - 2025-08-14 17:43 +0000
Re: System calls David Brown <david.brown@hesbynett.no> - 2025-08-15 17:49 +0200
Re: System calls cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-14 21:44 +0000
Re: System calls David Brown <david.brown@hesbynett.no> - 2025-08-15 17:49 +0200
Re: System calls cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-15 18:33 +0000
Re: System calls (was: VAX) cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-13 18:51 +0000
Re: System calls (was: VAX) scott@slp53.sl.home (Scott Lurndal) - 2025-08-13 20:28 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-13 19:35 +0000
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 00:49 +0000
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-06 13:48 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-04 23:24 +0000
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-05 01:41 +0000
Re: VAX vallor <vallor@cultnix.org> - 2025-08-05 05:56 +0000
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-05 01:34 +0000
Re: VAX Peter Flass <Peter@Iron-Spring.com> - 2025-08-01 20:06 -0700
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-02 03:37 +0000
Re: VAX ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-08-02 04:14 +0000
Re: VAX "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-08-01 21:35 -0700
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-02 08:07 +0000
Re: VAX Al Kossow <aek@bitsavers.org> - 2025-08-02 01:48 -0700
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-04 23:45 +0000
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-02 23:08 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-03 16:51 +0000
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-04 00:04 +0000
Re: VAX BGB <cr88192@gmail.com> - 2025-08-03 21:07 -0500
Re: VAX Peter Flass <Peter@Iron-Spring.com> - 2025-08-03 20:39 -0700
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-04 04:50 +0000
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-04 12:35 +0300
Re: VAX BGB <cr88192@gmail.com> - 2025-08-04 11:59 -0500
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-04 12:19 +0300
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-04 12:09 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-04 14:51 +0000
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-04 18:28 +0300
Re: VAX Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-08-04 09:53 -0700
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-04 16:58 +0000
Re: VAX "Brian G. Lucas" <bagel99@gmail.com> - 2025-08-05 13:03 -0500
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-04 22:03 +0300
Re: VAX James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-08-04 15:25 -0400
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-04 22:40 +0300
Re: VAX "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-08-04 12:44 -0700
Re: VAX Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-08-04 22:21 -0700
Re: VAX Kaz Kylheku <643-408-1753@kylheku.com> - 2025-08-05 21:25 +0000
Re: VAX Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-08-05 19:14 -0700
Re: VAX Kaz Kylheku <643-408-1753@kylheku.com> - 2025-08-06 04:31 +0000
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-06 11:48 +0300
Re: VAX James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-08-06 11:56 -0400
Re: VAX Kaz Kylheku <643-408-1753@kylheku.com> - 2025-08-05 21:13 +0000
Re: VAX James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-08-06 11:54 -0400
Re: VAX Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-08-06 13:58 -0700
Re: VAX Kaz Kylheku <643-408-1753@kylheku.com> - 2025-08-05 21:08 +0000
Re: VAX Jakob Bohm <egenagwemdimtapsar@jbohm.dk> - 2025-08-17 20:18 +0200
Re: VAX Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-08-17 22:18 -0700
Re: VAX Richard Heathfield <rjh@cpax.org.uk> - 2025-08-18 08:02 +0100
Re: VAX David Brown <david.brown@hesbynett.no> - 2025-08-18 11:34 +0200
Re: VAX Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-08-18 21:57 -0700
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-04 15:11 +0000
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-04 19:00 +0300
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-04 19:04 +0300
Re: VAX Terje Mathisen <terje.mathisen@tmsw.no> - 2025-08-04 22:49 +0200
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-05 00:14 +0300
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-05 01:43 +0300
Re: VAX Terje Mathisen <terje.mathisen@tmsw.no> - 2025-08-05 17:31 +0200
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-05 19:49 +0300
Re: VAX Terje Mathisen <terje.mathisen@tmsw.no> - 2025-08-05 22:17 +0200
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-06 00:21 +0300
Re: VAX Terje Mathisen <terje.mathisen@tmsw.no> - 2025-08-06 16:19 +0200
3-way long addition (was: VAX) Michael S <already5chosen@yahoo.com> - 2025-08-06 20:43 +0300
Re: 3-way long addition Terje Mathisen <terje.mathisen@tmsw.no> - 2025-08-07 15:15 +0200
3-way long addition (was: VAX) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-19 05:47 +0000
Re: 3-way long addition (was: VAX) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-19 07:09 +0000
Re: 3-way long addition Terje Mathisen <terje.mathisen@tmsw.no> - 2025-08-19 12:11 +0200
Re: 3-way long addition anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-19 17:43 +0000
Re: 3-way long addition (was: VAX) Michael S <already5chosen@yahoo.com> - 2025-08-19 17:20 +0300
Re: 3-way long addition (was: VAX) Michael S <already5chosen@yahoo.com> - 2025-08-19 17:24 +0300
Re: 3-way long addition (was: VAX) Michael S <already5chosen@yahoo.com> - 2025-08-19 23:03 +0300
Re: 3-way long addition Terje Mathisen <terje.mathisen@tmsw.no> - 2025-08-20 10:50 +0200
Re: 3-way long addition Michael S <already5chosen@yahoo.com> - 2025-08-20 14:16 +0300
Intel ADX (was: 3-way long addition) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-20 14:08 +0000
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-04 18:25 +0300
Re: VAX BGB <cr88192@gmail.com> - 2025-08-04 12:56 -0500
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-04 14:22 +0000
Re: VAX Terje Mathisen <terje.mathisen@tmsw.no> - 2025-08-04 16:46 +0200
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-04 15:05 +0000
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-04 18:07 +0300
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-04 15:32 +0000
Re: VAX Stefan Monnier <monnier@iro.umontreal.ca> - 2025-08-04 15:09 -0400
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-04 22:31 +0300
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-04 20:29 +0000
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-05 00:08 +0300
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-04 21:23 +0000
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-05 06:46 +0000
Re: VAX BGB <cr88192@gmail.com> - 2025-08-05 03:14 -0500
Re: VAX Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-08-05 11:52 -0700
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-06 05:37 +0000
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 06:20 +0000
Re: VAX BGB <cr88192@gmail.com> - 2025-08-04 12:12 -0500
I32LP64 vs. ILP64 (was: VAX) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-06 11:28 +0000
Re: I32LP64 vs. ILP64 antispam@fricas.org (Waldek Hebisch) - 2025-08-06 15:55 +0000
Re: I32LP64 vs. ILP64 BGB <cr88192@gmail.com> - 2025-08-06 12:47 -0500
Re: I32LP64 vs. ILP64 BGB <cr88192@gmail.com> - 2025-08-06 12:00 -0500
Re: I32LP64 vs. ILP64 (was: VAX) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 23:34 +0000
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-05 05:38 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-06 11:05 +0000
Re: VAX BGB <cr88192@gmail.com> - 2025-08-06 12:12 -0500
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-06 18:22 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-06 10:32 +0000
Re: 64 bits, was VAX John Levine <johnl@taugh.com> - 2025-08-06 17:25 +0000
Re: 64 bits, was VAX Peter Flass <Peter@Iron-Spring.com> - 2025-08-06 12:11 -0700
Re: individual 64 bits, was VAX John Levine <johnl@taugh.com> - 2025-08-06 19:50 +0000
Re: individual 64 bits, was VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-06 20:30 +0000
Re: 64 bits, was VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 23:36 +0000
Re: 64 bits, was VAX Terje Mathisen <terje.mathisen@tmsw.no> - 2025-08-07 15:44 +0200
Re: 64 bits, was VAX Peter Flass <Peter@Iron-Spring.com> - 2025-08-07 07:34 -0700
Re: 64 bits, S/360 was VAX John Levine <johnl@taugh.com> - 2025-08-07 20:54 +0000
Re: 64 bits, was VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-08 03:51 +0000
Bit addressing (was: 64 bits) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-07 14:57 +0000
Re: Bit addressing drb@ihatespam.msu.edu (Dennis Boone) - 2025-08-07 15:54 +0000
Re: Bit addressing Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-08-07 13:01 -0700
Re: Bit addressing (was: 64 bits) Al Kossow <aek@bitsavers.org> - 2025-08-07 13:34 -0700
Re: VAX Lars Poulsen <lars@cleo.beagle-ears.com> - 2025-08-06 23:12 +0000
Re: VAX John Levine <johnl@taugh.com> - 2025-08-06 23:15 +0000
Re: VAX Lars Poulsen <lars@cleo.beagle-ears.com> - 2025-08-06 23:32 +0000
Re: word lengths in C, was VAX John Levine <johnl@taugh.com> - 2025-08-07 02:56 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-07 11:21 +0000
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-07 13:34 +0000
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 23:38 +0000
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-04 12:42 +0300
Re: VAX Al Kossow <aek@bitsavers.org> - 2025-08-04 03:32 -0700
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-05 05:37 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-04 13:42 +0000
Re: VAX Andy Burns <usenet@andyburns.uk> - 2025-08-04 16:50 +0100
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-04 23:52 +0000
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-05 05:35 +0000
Re: VAX cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-05 01:31 +0000
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-05 13:46 +0000
Re: VAX cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-05 17:21 +0000
ILP32 code on 64-bit substrate (was: VAX) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-12 15:28 +0000
Re: ILP32 code on 64-bit substrate (was: VAX) scott@slp53.sl.home (Scott Lurndal) - 2025-08-12 16:08 +0000
Re: ILP32 code on 64-bit substrate BGB <cr88192@gmail.com> - 2025-08-12 11:53 -0500
Re: ILP32 code on 64-bit substrate aph@littlepinkcloud.invalid - 2025-08-12 17:57 +0000
Re: ILP32 code on 64-bit substrate John Levine <johnl@taugh.com> - 2025-08-12 19:09 +0000
Re: ILP32 code on 64-bit substrate OrangeFish <OrangeFish@invalid.invalid> - 2025-08-15 11:42 -0400
Re: ILP32 code on 64-bit substrate anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-13 06:11 +0000
Re: ILP32 code on 64-bit substrate scott@slp53.sl.home (Scott Lurndal) - 2025-08-13 14:24 +0000
Re: ILP32 code on 64-bit substrate anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-13 18:13 +0000
Re: VAX (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-02 09:28 +0000
Re: VAX (was: Why I've Dropped In) Thomas Koenig <tkoenig@netcologne.de> - 2025-08-02 15:29 +0000
Re: VAX Peter Flass <Peter@Iron-Spring.com> - 2025-08-02 15:33 -0700
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-02 23:17 +0000
Re: VAX (was: Why I've Dropped In) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-02 23:20 +0000
Re: VAX (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-04 17:23 +0000
Re: VAX (was: Why I've Dropped In) Thomas Koenig <tkoenig@netcologne.de> - 2025-08-04 18:16 +0000
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-04 14:39 -0400
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-04 19:59 +0000
Re: VAX (was: Why I've Dropped In) scott@slp53.sl.home (Scott Lurndal) - 2025-08-04 18:59 +0000
Re: VAX (was: Why I've Dropped In) Michael S <already5chosen@yahoo.com> - 2025-08-04 22:12 +0300
Re: VAX (was: Why I've Dropped In) Thomas Koenig <tkoenig@netcologne.de> - 2025-08-04 20:13 +0000
Re: VAX (was: Why I've Dropped In) Michael S <already5chosen@yahoo.com> - 2025-08-04 23:54 +0300
Re: VAX (was: Why I've Dropped In) Al Kossow <aek@bitsavers.org> - 2025-08-04 14:41 -0700
Re: VAX BGB <cr88192@gmail.com> - 2025-08-04 17:18 -0500
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-05 01:53 +0000
Re: VAX "Brian G. Lucas" <bagel99@gmail.com> - 2025-08-05 13:04 -0500
O.T. Where is Mitch? Was: VAX Michael S <already5chosen@yahoo.com> - 2025-08-07 23:48 +0300
Re: O.T. Where is Mitch? Was: VAX "Brian G. Lucas" <bagel99@gmail.com> - 2025-08-07 16:01 -0500
Re: O.T. Where is Mitch? Was: VAX BGB <cr88192@gmail.com> - 2025-08-08 01:41 -0500
Re: O.T. Where is Mitch? Was: VAX Terje Mathisen <terje.mathisen@tmsw.no> - 2025-08-08 11:58 +0200
Re: O.T. Where is Mitch? Was: VAX Michael S <already5chosen@yahoo.com> - 2025-08-08 13:20 +0300
Re: O.T. Where is Mitch? Was: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-08 14:22 +0000
Re: O.T. Where is Mitch? Was: VAX Niklas Holsti <niklas.holsti@tidorum.invalid> - 2025-08-08 18:34 +0300
Re: O.T. Where is Mitch? Was: VAX George Neuner <gneuner2@comcast.net> - 2025-08-08 19:07 -0400
Re: VAX (was: Why I've Dropped In) Thomas Koenig <tkoenig@netcologne.de> - 2025-08-05 21:01 +0000
Re: VAX (was: Why I've Dropped In) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 00:59 +0000
Re: VAX Peter Flass <Peter@Iron-Spring.com> - 2025-08-05 20:15 -0700
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-06 05:50 +0000
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 07:28 +0000
Re: VAX cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-06 10:48 +0000
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-06 16:35 +0000
Re: VAX cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-08 01:57 +0000
Re: VAX (was: Why I've Dropped In) John Ames <commodorejohn@gmail.com> - 2025-08-06 08:28 -0700
Re: VAX (was: Why I've Dropped In) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 23:45 +0000
Re: VAX (was: Why I've Dropped In) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-08-07 01:49 +0000
Re: VAX (was: Why I've Dropped In) John Ames <commodorejohn@gmail.com> - 2025-08-07 08:28 -0700
Re: VAX (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-13 09:37 +0000
Re: VAX (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-13 08:22 +0000
Re: VAX (was: Why I've Dropped In) scott@slp53.sl.home (Scott Lurndal) - 2025-08-13 14:26 +0000
Re: VAX (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-13 17:50 +0000
Re: VAX drb@ihatespam.msu.edu (Dennis Boone) - 2025-08-14 17:12 +0000
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-14 15:22 -0400
Re: VAX Al Kossow <aek@bitsavers.org> - 2025-08-14 12:59 -0700
Re: VAX (was: Why I've Dropped In) scott@slp53.sl.home (Scott Lurndal) - 2025-08-13 14:44 +0000
Re: VAX (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-13 17:46 +0000
Re: VAX (was: Why I've Dropped In) ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-08-13 18:26 +0000
Re: VAX Peter Flass <Peter@Iron-Spring.com> - 2025-08-13 12:09 -0700
Re: VAX (was: Why I've Dropped In) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-05 01:47 +0000
Re: VAX (was: Why I've Dropped In) scott@slp53.sl.home (Scott Lurndal) - 2025-08-05 13:58 +0000
Re: VAX (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-06 16:47 +0000
Re: VAX Peter Flass <Peter@Iron-Spring.com> - 2025-08-06 12:12 -0700
Re: VAX Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-08-07 01:36 +0000
Re: VAX (was: Why I've Dropped In) Thomas Koenig <tkoenig@netcologne.de> - 2025-08-07 05:29 +0000
Re: VAX Peter Flass <Peter@Iron-Spring.com> - 2025-08-07 07:26 -0700
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-08 03:57 +0000
Re: VAX Michael S <already5chosen@yahoo.com> - 2025-08-08 11:43 +0300
Re: VAX (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-06 14:00 +0000
Re: VAX (was: Why I've Dropped In) Al Kossow <aek@bitsavers.org> - 2025-08-06 10:20 -0700
Re: VAX (was: Why I've Dropped In) Robert Swindells <rjs@fdy2.co.uk> - 2025-08-06 22:30 +0000
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-06 20:21 -0400
Re: VAX Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-07 02:22 +0000
Re: VAX John Ames <commodorejohn@gmail.com> - 2025-08-07 08:38 -0700
Re: VAX Terje Mathisen <terje.mathisen@tmsw.no> - 2025-08-07 17:52 +0200
Re: VAX George Neuner <gneuner2@comcast.net> - 2025-08-07 21:53 -0400
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-08 06:16 +0000
Re: VAX George Neuner <gneuner2@comcast.net> - 2025-08-08 19:48 -0400
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-07 10:27 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-07 11:06 +0000
Re: VAX (was: Why I've Dropped In) Al Kossow <aek@bitsavers.org> - 2025-08-04 12:27 -0700
Re: VAX (was: Why I've Dropped In) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-05 01:46 +0000
Re: VAX (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-06 16:21 +0000
Re: VAX (was: Why I've Dropped In) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-05 01:43 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-01 23:41 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-03 16:42 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-05 00:55 +0000
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-05 05:44 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-12 15:02 +0000
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-13 14:40 -0400
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-15 03:20 +0000
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-15 15:10 +0000
Re: VAX pages John Levine <johnl@taugh.com> - 2025-08-15 16:53 +0000
Re: VAX pages BGB <cr88192@gmail.com> - 2025-08-15 13:19 -0500
Re: VAX pages Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-08-15 12:03 -0700
Re: VAX pages scott@slp53.sl.home (Scott Lurndal) - 2025-08-15 19:19 +0000
Re: VAX and other pages John Levine <johnl@taugh.com> - 2025-08-15 20:40 +0000
Re: VAX and other pages anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-15 21:22 +0000
Re: VAX and other pages John Levine <johnl@taugh.com> - 2025-08-16 01:22 +0000
Re: VAX and other pages anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-16 05:09 +0000
Re: VAX and other pages Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-08-16 10:00 -0700
Re: VAX and other pages John Levine <johnl@taugh.com> - 2025-08-16 17:06 +0000
Re: VAX and other pages antispam@fricas.org (Waldek Hebisch) - 2025-08-20 01:49 +0000
Re: VAX and other pages John Levine <johnl@taugh.com> - 2025-08-20 02:49 +0000
Re: VAX pages BGB <cr88192@gmail.com> - 2025-08-16 03:17 -0500
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-07-31 04:26 +0000
Re: VAX John Levine <johnl@taugh.com> - 2025-07-31 16:05 +0000
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-07-31 19:01 +0000
Re: VAX John Levine <johnl@taugh.com> - 2025-07-31 19:57 +0000
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-07-31 21:24 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-01 02:18 +0000
Re: VAX encoding John Levine <johnl@taugh.com> - 2025-08-01 15:30 +0000
Re: VAX encoding antispam@fricas.org (Waldek Hebisch) - 2025-08-01 18:08 +0000
Re: VAX encoding scott@slp53.sl.home (Scott Lurndal) - 2025-08-01 18:33 +0000
Re: VAX encoding antispam@fricas.org (Waldek Hebisch) - 2025-08-01 21:24 +0000
Re: VAX encoding Thomas Koenig <tkoenig@netcologne.de> - 2025-08-01 19:13 +0000
Re: VAX encoding MitchAlsup <user5857@newsgrouper.org.invalid> - 2025-08-28 15:10 +0000
Re: VAX encoding EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-29 10:34 -0400
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-02 09:02 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-05 01:43 +0000
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-05 05:48 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-05 14:13 +0000
Re: VAX George Neuner <gneuner2@comcast.net> - 2025-08-05 17:41 -0400
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-06 10:23 -0400
Re: VAX George Neuner <gneuner2@comcast.net> - 2025-08-08 21:43 -0400
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-05 13:56 +0000
Re: VAX cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-05 16:44 +0000
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-06 05:53 +0000
Re: VAX cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-06 11:10 +0000
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-06 20:06 +0000
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-06 17:00 -0400
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-06 21:14 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-07 11:59 +0000
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-07 15:03 +0000
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-06 17:57 -0400
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-07 11:29 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-07 11:38 +0000
Re: VAX BGB <cr88192@gmail.com> - 2025-08-16 15:26 -0500
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-17 06:16 +0000
Re: VAX BGB <cr88192@gmail.com> - 2025-08-17 11:29 -0500
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-17 10:00 -0400
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-17 15:21 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-17 19:10 +0000
Re: VAX BGB <cr88192@gmail.com> - 2025-08-17 15:08 -0500
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-18 11:03 -0400
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-18 15:35 +0000
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-18 17:19 +0000
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-20 14:36 -0400
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-20 16:41 -0400
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-21 16:21 +0000
Re: VAX BGB <cr88192@gmail.com> - 2025-08-17 12:53 -0500
Re: VAX Robert Swindells <rjs@fdy2.co.uk> - 2025-08-06 23:43 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-07 10:47 +0000
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-08 10:08 -0400
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-09 08:07 +0000
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-09 10:03 -0400
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-09 20:54 +0000
Re: VAX Al Kossow <aek@bitsavers.org> - 2025-08-09 14:57 -0700
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-13 14:18 -0400
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-13 20:23 +0000
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-17 13:35 -0400
Re: VAX BGB <cr88192@gmail.com> - 2025-08-17 18:56 -0500
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-20 19:17 -0400
Re: VAX BGB <cr88192@gmail.com> - 2025-08-20 23:50 -0500
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-06 20:41 -0400
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-07 11:16 +0000
Re: VAX cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-09 09:04 +0000
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-09 10:00 +0000
Re: VAX cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-10 12:06 +0000
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-10 15:18 +0000
Re: byte me, PDP-10 edition, was VAX John Levine <johnl@taugh.com> - 2025-08-10 19:55 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-11 08:17 +0000
Re: VAX scott@slp53.sl.home (Scott Lurndal) - 2025-08-11 14:51 +0000
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-11 17:27 +0000
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-10 21:01 +0000
Re: VAX cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-13 11:25 +0000
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-15 05:07 +0000
Re: VAX cross@spitfire.i.gajendra.net (Dan Cross) - 2025-08-15 12:57 +0000
Re: VAX Robert Swindells <rjs@fdy2.co.uk> - 2025-08-15 13:36 +0000
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-18 05:48 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-05 20:34 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-12 15:59 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-20 03:47 +0000
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-21 19:26 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-22 16:36 +0000
Re: VAX Thomas Koenig <tkoenig@netcologne.de> - 2025-08-22 17:21 +0000
Re: VAX John Levine <johnl@taugh.com> - 2025-08-22 16:45 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-23 16:38 +0000
Re: 360/91, was VAX John Levine <johnl@taugh.com> - 2025-08-23 19:36 +0000
Re: VAX anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-01 17:25 +0000
Re: VAX MitchAlsup <user5857@newsgrouper.org.invalid> - 2025-08-27 00:56 +0000
Re: VAX antispam@fricas.org (Waldek Hebisch) - 2025-08-28 07:49 +0000
Re: VAX (was: Why I've Dropped In) MitchAlsup <user5857@newsgrouper.org.invalid> - 2025-08-27 00:35 +0000
Re: VAX (was: Why I've Dropped In) Thomas Koenig <tkoenig@netcologne.de> - 2025-08-27 05:12 +0000
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-27 10:56 -0400
Re: VAX EricP <ThatWouldBeTelling@thevillage.com> - 2025-08-28 13:39 -0400
Re: VAX (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-27 17:19 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-14 17:30 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-14 18:39 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-13 17:42 +0000
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-13 11:00 -0700
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-14 16:04 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-14 16:12 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-14 16:50 +0000
Re: base registers and addres size, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-14 22:02 +0000
Re: base registers and addres size, Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-14 22:58 +0000
Re: base registers and addres size, Why I've Dropped In John Levine <johnl@taugh.com> - 2025-06-15 01:08 +0000
Re: Why I've Dropped In Lynn Wheeler <lynn@garlic.com> - 2025-06-17 16:47 -1000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-18 13:48 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-13 17:52 -0500
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-14 04:04 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-14 10:45 +0000
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-11 17:33 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-11 18:14 +0000
Re: Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-11 12:30 -0700
Re: Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-11 12:31 -0700
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-12 02:17 +0000
Re: Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-12 11:55 -0700
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-13 03:30 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-13 20:40 +0000
Re: Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-15 16:56 -0700
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-11 21:26 +0000
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-12 06:30 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-12 07:57 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-12 14:06 +0000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-12 13:43 +0000
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-13 07:31 +0000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-13 14:48 +0000
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-13 15:38 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-13 17:10 +0000
Re: Why I've Dropped In antispam@fricas.org (Waldek Hebisch) - 2025-06-17 11:44 +0000
Re: Why I've Dropped In David Brown <david.brown@hesbynett.no> - 2025-06-17 16:00 +0200
Code density (was: Why I've Dropped In) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-17 14:17 +0000
Re: Code density (was: Why I've Dropped In) scott@slp53.sl.home (Scott Lurndal) - 2025-06-17 15:11 +0000
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-06-17 18:01 +0000
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-17 23:55 -0400
Re: Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-18 06:22 +0000
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-18 09:32 -0400
Re: Code density "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-06-18 16:19 +0100
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-06-18 18:27 +0000
Re: Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-19 09:21 +0000
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-22 10:05 -0400
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-06-22 17:35 +0000
Re: Code density scott@slp53.sl.home (Scott Lurndal) - 2025-06-22 20:26 +0000
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-06-26 01:12 +0000
Re: Code density scott@slp53.sl.home (Scott Lurndal) - 2025-06-26 15:17 +0000
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-27 07:48 -0400
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-27 08:33 -0400
Re: Code density Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-27 22:41 -0700
Re: Code density Thomas Koenig <tkoenig@netcologne.de> - 2025-06-28 07:45 +0000
Re: Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-28 11:11 +0000
Re: Code density Thomas Koenig <tkoenig@netcologne.de> - 2025-06-28 12:00 +0000
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-06-28 16:01 +0000
Re: Code density Thomas Koenig <tkoenig@netcologne.de> - 2025-06-29 14:54 +0000
Re: Code density Terje Mathisen <terje.mathisen@tmsw.no> - 2025-06-29 18:01 +0200
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-06-29 20:50 +0000
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-29 13:21 -0400
Re: Code density Thomas Koenig <tkoenig@netcologne.de> - 2025-06-29 20:41 +0000
Re: Code density George Neuner <gneuner2@comcast.net> - 2025-06-28 08:05 -0400
Re: Code density "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-28 21:29 -0700
Re: Code density scott@slp53.sl.home (Scott Lurndal) - 2025-06-27 13:55 +0000
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-27 15:09 -0400
Re: Code density scott@slp53.sl.home (Scott Lurndal) - 2025-06-27 21:01 +0000
Re: Code density Thomas Koenig <tkoenig@netcologne.de> - 2025-06-28 09:07 +0000
Re: Code density John Levine <johnl@taugh.com> - 2025-06-28 16:30 +0000
Re: errno, Code density John Levine <johnl@taugh.com> - 2025-06-27 21:44 +0000
Re: errno, Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-29 14:02 -0400
Re: errno, Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-30 06:21 +0000
Re: errno, Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-30 12:51 -0400
Re: errno, Code density scott@slp53.sl.home (Scott Lurndal) - 2025-06-30 17:13 +0000
Re: errno, Code density Michael S <already5chosen@yahoo.com> - 2025-07-01 13:11 +0300
Re: errno, Code density scott@slp53.sl.home (Scott Lurndal) - 2025-07-01 13:18 +0000
Re: errno, Code density Michael S <already5chosen@yahoo.com> - 2025-07-01 16:21 +0300
Re: errno, Code density Michael S <already5chosen@yahoo.com> - 2025-07-01 16:28 +0300
Re: errno, Code density scott@slp53.sl.home (Scott Lurndal) - 2025-07-01 14:08 +0000
Re: errno, Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-07-01 11:09 -0400
Re: assemblers, errno, Code density John Levine <johnl@taugh.com> - 2025-07-01 17:41 +0000
Re: errno, Code density mitchalsup@aol.com (MitchAlsup1) - 2025-06-30 17:11 +0000
Re: errno, Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-07-02 08:06 -0400
Re: errno, Code density mitchalsup@aol.com (MitchAlsup1) - 2025-07-02 15:38 +0000
Re: errno, Code density Michael S <already5chosen@yahoo.com> - 2025-06-30 13:55 +0300
Re: Code density George Neuner <gneuner2@comcast.net> - 2025-06-28 07:02 -0400
Re: Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-30 16:08 +0000
Re: Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-01 16:08 +0000
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-07-01 20:03 +0000
Re: Code density scott@slp53.sl.home (Scott Lurndal) - 2025-07-01 21:07 +0000
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-07-01 23:20 +0000
Re: Code density John Levine <johnl@taugh.com> - 2025-07-02 17:14 +0000
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-07-02 15:38 -0400
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-07-03 08:41 -0400
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-07-16 01:18 +0000
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-07-18 13:23 -0400
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-07-18 19:54 +0000
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-07-20 13:05 -0400
Re: Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-20 17:33 +0000
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-07-20 20:09 +0000
Re: compacting branches, was Code density John Levine <johnl@taugh.com> - 2025-07-21 09:01 +0000
Re: compacting branches, was Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-21 12:33 +0000
Re: compacting branches, was Code density Terje Mathisen <terje.mathisen@tmsw.no> - 2025-07-21 17:01 +0200
Re: compacting branches, was Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-21 15:26 +0000
Re: compacting branches, was Code density Terje Mathisen <terje.mathisen@tmsw.no> - 2025-07-21 18:06 +0200
Re: compacting branches, was Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-21 17:26 +0000
Re: compacting branches, was Code density Terje Mathisen <terje.mathisen@tmsw.no> - 2025-07-21 19:31 +0200
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-07-21 10:50 -0400
Re: Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-21 15:28 +0000
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-07-21 17:08 -0400
Re: Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-02 05:25 +0000
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-07-01 21:49 +0000
Re: Code density scott@slp53.sl.home (Scott Lurndal) - 2025-07-01 23:26 +0000
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-07-02 00:04 +0000
Re: Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-02 05:18 +0000
Re: Code density EricP <ThatWouldBeTelling@thevillage.com> - 2025-07-02 11:20 -0400
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-07-02 15:45 +0000
Re: Code density scott@slp53.sl.home (Scott Lurndal) - 2025-07-02 16:56 +0000
Re: Code density mitchalsup@aol.com (MitchAlsup1) - 2025-07-02 17:06 +0000
Re: Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-18 06:26 +0000
Re: Code density BGB <cr88192@gmail.com> - 2025-07-01 01:16 -0500
Re: Code density anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-01 15:23 +0000
Re: Code density BGB <cr88192@gmail.com> - 2025-07-01 10:53 -0500
Re: Why I've Dropped In EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-11 14:56 -0400
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-11 19:37 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-12 19:01 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-13 20:12 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-13 20:50 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-11 21:17 +0000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-11 21:35 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-11 23:13 +0000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-12 13:41 +0000
Re: Why I've Dropped In EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-12 09:38 -0400
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-12 19:19 +0000
Re: Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-12 12:25 -0700
Re: Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-12 12:27 -0700
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-13 07:03 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-13 20:01 +0000
Re: Why I've Dropped In Robert Finch <robfi680@gmail.com> - 2025-06-14 04:35 -0400
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-14 15:22 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-14 17:30 +0000
Re: Why I've Dropped In Terje Mathisen <terje.mathisen@tmsw.no> - 2025-06-20 17:11 +0200
Re: Why I've Dropped In Stefan Monnier <monnier@iro.umontreal.ca> - 2025-06-20 12:43 -0400
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-20 17:38 +0000
Re: Why I've Dropped In Stefan Monnier <monnier@iro.umontreal.ca> - 2025-06-20 13:48 -0400
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-20 20:46 +0000
Re: Why I've Dropped In Stefan Monnier <monnier@iro.umontreal.ca> - 2025-06-20 18:13 -0400
Re: Why I've Dropped In antispam@fricas.org (Waldek Hebisch) - 2025-06-21 01:48 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-21 02:51 +0000
Re: Why I've Dropped In Terje Mathisen <terje.mathisen@tmsw.no> - 2025-06-24 08:15 +0200
Re: Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-12 12:06 -0700
Re: Why I've Dropped In EricP <ThatWouldBeTelling@thevillage.com> - 2025-06-12 09:12 -0400
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-12 18:55 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-12 20:50 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-11 15:29 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-11 17:22 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-23 03:43 +0000
The Third Wish quadibloc <quadibloc@gmail.com> - 2025-06-23 12:43 +0000
Re: The Third Wish quadibloc <quadibloc@gmail.com> - 2025-06-23 12:47 +0000
Re: The Third Wish quadibloc <quadibloc@gmail.com> - 2025-06-24 17:19 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-06-24 21:57 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-06-25 07:31 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-06-27 05:28 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-02 05:16 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-02 07:04 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-03 05:52 +0000
Re: The Third Wish Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-07-02 22:57 -0700
Re: The Third Wish Thomas Koenig <tkoenig@netcologne.de> - 2025-07-03 06:59 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-03 09:43 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-03 11:24 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-03 11:35 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-16 01:11 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-16 01:08 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-16 18:22 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-16 23:36 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-16 23:58 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-17 03:42 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-17 04:01 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-17 04:10 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-17 04:24 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-17 15:16 +0000
Register windows (was: The Third Wish) Stefan Monnier <monnier@iro.umontreal.ca> - 2025-07-17 12:20 -0400
Re: Register windows mitchalsup@aol.com (MitchAlsup1) - 2025-07-17 16:53 +0000
Re: Register windows (was: The Third Wish) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-17 17:38 +0000
Re: Register windows (was: The Third Wish) scott@slp53.sl.home (Scott Lurndal) - 2025-07-17 19:17 +0000
Re: Register windows mitchalsup@aol.com (MitchAlsup1) - 2025-07-17 19:38 +0000
Re: Register windows Stefan Monnier <monnier@iro.umontreal.ca> - 2025-07-17 16:18 -0400
Re: Register windows Niklas Holsti <niklas.holsti@tidorum.invalid> - 2025-07-18 18:11 +0300
Re: Register windows Stefan Monnier <monnier@iro.umontreal.ca> - 2025-07-18 11:29 -0400
Re: Register windows Niklas Holsti <niklas.holsti@tidorum.invalid> - 2025-07-18 23:17 +0300
Re: Register windows mitchalsup@aol.com (MitchAlsup1) - 2025-07-20 17:28 +0000
Re: Register windows George Neuner <gneuner2@comcast.net> - 2025-07-20 22:27 -0400
Re: Register windows Niklas Holsti <niklas.holsti@tidorum.invalid> - 2025-07-21 12:11 +0300
Re: Register windows John Savard <quadibloc@invalid.invalid> - 2025-07-21 15:42 +0000
Re: Register windows MitchAlsup <user5857@newsgrouper.org.invalid> - 2025-08-21 21:48 +0000
Re: Register windows Thomas Koenig <tkoenig@netcologne.de> - 2025-08-23 08:51 +0000
Re: Register windows Stefan Monnier <monnier@iro.umontreal.ca> - 2025-08-29 17:07 -0400
Re: Register windows BGB <cr88192@gmail.com> - 2025-08-30 01:47 -0500
Re: Register windows antispam@fricas.org (Waldek Hebisch) - 2025-08-30 15:36 +0000
Re: Register windows BGB <cr88192@gmail.com> - 2025-08-30 13:19 -0500
Re: Register windows Stefan Monnier <monnier@iro.umontreal.ca> - 2025-08-30 14:22 -0400
Re: Register windows BGB <cr88192@gmail.com> - 2025-08-30 13:46 -0500
Re: Register windows MitchAlsup <user5857@newsgrouper.org.invalid> - 2025-08-31 16:21 +0000
Re: Register windows Thomas Koenig <tkoenig@netcologne.de> - 2025-09-12 17:47 +0000
Re: Register windows MitchAlsup <user5857@newsgrouper.org.invalid> - 2025-09-12 19:02 +0000
Re: Register windows scott@slp53.sl.home (Scott Lurndal) - 2025-09-14 15:16 +0000
Re: Register windows anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-09-17 05:55 +0000
Re: Register windows scott@slp53.sl.home (Scott Lurndal) - 2025-09-17 13:58 +0000
Re: Register windows anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-08-31 05:36 +0000
Where's Ivan was Re: Register windows Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-07-20 22:27 -0700
Re: Where's Ivan was Re: Register windows John Savard <quadibloc@invalid.invalid> - 2025-07-21 15:45 +0000
Re: Where's Ivan was Re: Register windows Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-07-21 12:05 -0700
Re: Where's Ivan was Re: Register windows scott@slp53.sl.home (Scott Lurndal) - 2025-07-21 19:56 +0000
Re: Where's Ivan was Re: Register windows Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-07-21 22:02 -0700
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-17 15:02 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-17 14:59 +0000
Re: The Third Wish anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-17 16:28 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-17 19:21 +0000
Re: The Third Wish EricP <ThatWouldBeTelling@thevillage.com> - 2025-07-18 12:29 -0400
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-17 14:49 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-17 18:03 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-17 18:27 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-17 20:04 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-17 21:00 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-17 21:26 +0000
Re: The Third Wish Thomas Koenig <tkoenig@netcologne.de> - 2025-07-18 19:47 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-19 02:51 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-17 21:29 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-17 21:45 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-17 21:58 +0000
Re: The Third Wish antispam@fricas.org (Waldek Hebisch) - 2025-07-18 15:39 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-18 17:08 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-18 19:38 +0000
Re: The Third Wish Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-07-17 12:20 -0700
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-17 19:52 +0000
PRF size (was: The Third Wish) Stefan Monnier <monnier@iro.umontreal.ca> - 2025-07-17 16:34 -0400
Re: PRF size mitchalsup@aol.com (MitchAlsup1) - 2025-07-17 21:38 +0000
Re: PRF size EricP <ThatWouldBeTelling@thevillage.com> - 2025-07-20 11:47 -0400
Re: PRF size mitchalsup@aol.com (MitchAlsup1) - 2025-07-20 17:34 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-17 20:32 +0000
Re: The Third Wish Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-07-17 21:35 -0700
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-18 11:18 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-18 11:28 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-18 11:33 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-18 15:12 +0000
Re: The Third Wish Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-07-18 08:46 -0700
Re: The Third Wish scott@slp53.sl.home (Scott Lurndal) - 2025-07-18 16:25 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-18 17:14 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-18 19:39 +0000
Re: The Third Wish anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-18 16:24 +0000
Re: The Third Wish Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-07-18 11:40 -0700
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-18 19:45 +0000
Re: The Third Wish EricP <ThatWouldBeTelling@thevillage.com> - 2025-07-18 14:07 -0400
Re: The Third Wish antispam@fricas.org (Waldek Hebisch) - 2025-07-18 16:10 +0000
Re: The Third Wish anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-07-17 17:06 +0000
Re: The Third Wish antispam@fricas.org (Waldek Hebisch) - 2025-07-18 16:37 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-16 18:09 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-15 22:24 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-16 00:00 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-16 00:22 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-16 01:49 +0000
Re: The Third Wish Thomas Koenig <tkoenig@netcologne.de> - 2025-07-16 17:33 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-16 23:24 +0000
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-16 23:26 +0000
Re: The Third Wish mitchalsup@aol.com (MitchAlsup1) - 2025-07-16 18:06 +0000
Re: The Third Wish "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-07-16 14:55 -0700
Re: The Third Wish John Savard <quadibloc@invalid.invalid> - 2025-07-16 12:26 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-13 10:43 +0000
Re: Why I've Dropped In John Savard <quadibloc@invalid.invalid> - 2025-07-22 04:30 +0000
Re: Why I've Dropped In John Savard <quadibloc@invalid.invalid> - 2025-07-22 16:29 +0000
Satisfaction John Savard <quadibloc@invalid.invalid> - 2025-07-24 11:07 +0000
Re: Satisfaction John Savard <quadibloc@invalid.invalid> - 2025-07-24 16:45 +0000
Re: Satisfaction John Savard <quadibloc@invalid.invalid> - 2025-07-24 20:04 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-16 03:46 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-12 15:38 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-12 19:24 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-13 00:11 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-16 17:14 -0500
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-16 23:37 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-17 01:20 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-17 17:41 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-17 17:59 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-17 14:04 -0500
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-17 21:19 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-18 01:16 -0500
Re: Why I've Dropped In Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2025-06-17 23:35 -0700
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-18 02:10 -0500
Re: Why I've Dropped In antispam@fricas.org (Waldek Hebisch) - 2025-06-25 22:24 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-25 23:00 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-18 16:09 +0000
Re: Why I've Dropped In "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-06-17 12:45 -0700
Re: Why I've Dropped In John Savard <quadibloc@invalid.invalid> - 2025-08-01 04:31 +0000
Re: Why I've Dropped In Stefan Monnier <monnier@iro.umontreal.ca> - 2025-06-17 16:51 -0400
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-17 21:11 +0000
Re: Why I've Dropped In anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-06-18 06:58 +0000
Re: Why I've Dropped In antispam@fricas.org (Waldek Hebisch) - 2025-06-18 14:45 +0000
Re: Why I've Dropped In BGB <cr88192@gmail.com> - 2025-06-17 01:28 -0500
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-17 12:58 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-17 13:12 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-17 17:52 +0000
Re: Why I've Dropped In scott@slp53.sl.home (Scott Lurndal) - 2025-06-17 18:14 +0000
Re: Why I've Dropped In Thomas Koenig <tkoenig@netcologne.de> - 2025-06-18 14:10 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-18 15:14 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-18 18:16 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-18 22:00 +0000
Re: Why I've Dropped In quadibloc <quadibloc@gmail.com> - 2025-06-18 23:20 +0000
Re: Why I've Dropped In mitchalsup@aol.com (MitchAlsup1) - 2025-06-19 01:03 +0000
Page 20 of 50 — ← Prev page 1 … 18 19 [20] 21 22 … 50 Next page →
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2025-08-01 21:35 -0700 |
| Subject | Re: VAX |
| Message-ID | <106k4ie$rgv3$1@dont-email.me> |
| In reply to | #112822 |
On 8/1/2025 9:14 PM, Ted Nolan <tednolan> wrote: > In article <106k15u$qgip$6@dont-email.me>, > Lawrence D'Oliveiro <ldo@nz.invalid> wrote: >> On Fri, 1 Aug 2025 20:06:43 -0700, Peter Flass wrote: >> >>> Wasn't PRISM/MICA supposed to solve this problem, or am I confusing it >>> with something else? >> >> PRISM was going to be a new hardware architecture, and MICA the OS to run >> on it. Yes, they were supposed to solve the problem of where DEC was going >> to go since the VAX architecture was clearly being left in the dust by >> RISC. >> >> I think the MICA kernel was going to support the concept of >> “personalities”, so that a VMS-compatible environment could be implemented >> by one set of upper layers, while another set could provide Unix >> functionality. >> >> I think the project was taking too long, and not making enough progress. >> So DEC management cancelled the whole thing, and brought out a MIPS-based >> machine instead. >> >> The guy in charge got annoyed at the killing of his pet project and left >> in a huff. He took some of those ideas with him to his new employer, to >> create a new OS for them. >> >> The new employer was Microsoft. The guy in question was Dave Cutler. The >> OS they brought out was called “Windows NT”. > > And it's *still* not finished! Well, what about: https://github.com/ZoloZiak/WinNT4 Humm... A little?
[toc] | [prev] | [next] | [standalone]
| From | antispam@fricas.org (Waldek Hebisch) |
|---|---|
| Date | 2025-08-02 08:07 +0000 |
| Subject | Re: VAX |
| Message-ID | <106kh0k$18ipb$1@paganini.bofh.team> |
| In reply to | #112818 |
In comp.arch Peter Flass <Peter@iron-spring.com> wrote:
> On 8/1/25 11:11, Scott Lurndal wrote:
>> anton@mips.complang.tuwien.ac.at (Anton Ertl) writes:
>>> Lars Poulsen <lars@cleo.beagle-ears.com> writes:
>>>> In the days of VAX-11/780, it was "obvious" that operating systems would
>>>> be written in assembler in order to be efficient, and the instruction
>>>> set allowed high productivity for writing systems programs in "native"
>>>> code.
>>>
>>> Yes. I don't think that the productivity would have suffered from a
>>> load/store architecture, though.
>>>
>>>> As for a RISC-VAX: To little old naive me, it seems that it would have
>>>> been possible to create an alternative microcode load that would be able
>>>> to support a RISC ISA on the same hardware, if the idea had occured to a
>>>> well-connected group of graduate students. How good a RISC might have
>>>> been feasible?
>>>
>>> Did the VAX 11/780 have writable microcode?
>>
>> Yes.
>>
>>>
>>> Given that the VAX 11/780 was not (much) pipelined, I don't expect
>>> that using an alternative microcode that implements a RISC ISA would
>>> have performed well.
>>
>> A new ISA also requires development of the complete software
>> infrastructure for building applications (compilers, linkers,
>> assemblers); updating the OS, rebuilding existing applications
>> for the new ISA, field and customer training, etc.
>>
>> Digital eventually did move VMS to Alpha, but it was neither
>> cheap, nor easy. Most alpha customers were existing VAX
>> customers - it's not clear that DEC actually grew the customer
>> base by switching to Alpha.
>>
>
> Wasn't PRISM/MICA supposed to solve this problem, or am I confusing it
> with something else?
IIUC PRISM eventually became Alpha. One piece of supporting sofware
was a VAX emulator IIRC called FX11: it allowed running unmodified
VAX binaries. Another supporting piece was Macro32, which effectively
was a compiler from VAX assembly to Alpha binaries.
One big selling point of Alpha was 64-bit architecture, but IIUC
VMS was never fully ported to 64-bits, that is a lot of VMS
software used 32-bit addresses and some system interfaces were
32-bit only. OTOH Unix for Alpha was claimed to be pure 64-bit.
--
Waldek Hebisch
[toc] | [prev] | [next] | [standalone]
| From | Al Kossow <aek@bitsavers.org> |
|---|---|
| Date | 2025-08-02 01:48 -0700 |
| Subject | Re: VAX |
| Message-ID | <106kjd9$vnvj$1@dont-email.me> |
| In reply to | #112824 |
On 8/2/25 1:07 AM, Waldek Hebisch wrote: > IIUC PRISM eventually became Alpha. Not really. Documents for both, including the rare PRISM docs are on bitsavers. PRISM came out of Cutler's DEC West group, Alpha from the East Coast. I'm not aware of any team member overlap.
[toc] | [prev] | [next] | [standalone]
| From | antispam@fricas.org (Waldek Hebisch) |
|---|---|
| Date | 2025-08-04 23:45 +0000 |
| Subject | Re: VAX |
| Message-ID | <106rgmf$1tua1$3@paganini.bofh.team> |
| In reply to | #112825 |
In comp.arch Al Kossow <aek@bitsavers.org> wrote:
> On 8/2/25 1:07 AM, Waldek Hebisch wrote:
>
>> IIUC PRISM eventually became Alpha.
>
> Not really. Documents for both, including
> the rare PRISM docs are on bitsavers.
> PRISM came out of Cutler's DEC West group,
> Alpha from the East Coast. I'm not aware
> of any team member overlap.
Well, from peoples point of view they were different efforts.
From company point of view there was project to deliver
high-preformace RISC-y machine, it finally succeded when
new team did the work. I think that at least high-level
knowledge gained in PRISM project was useful for Alpha.
I would expect that some detailed work was reused, but
do not know how much.
--
Waldek Hebisch
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-08-02 23:08 +0000 |
| Subject | Re: VAX |
| Message-ID | <106m5pm$1atss$1@dont-email.me> |
| In reply to | #112824 |
On Sat, 2 Aug 2025 08:07:50 -0000 (UTC), Waldek Hebisch wrote: > One big selling point of Alpha was 64-bit architecture, but IIUC > VMS was never fully ported to 64-bits, that is a lot of VMS > software used 32-bit addresses and some system interfaces were > 32-bit only. OTOH Unix for Alpha was claimed to be pure 64-bit. Of the four main OSes for Alpha, the only fully-64-bit ones were DEC Unix and Linux. OpenVMS was a hybrid 32/64-bit implementation, and Windows NT was 32-bit-only.
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2025-08-03 16:51 +0000 |
| Subject | Re: VAX |
| Message-ID | <2025Aug3.185110@mips.complang.tuwien.ac.at> |
| In reply to | #112824 |
antispam@fricas.org (Waldek Hebisch) writes: >One piece of supporting sofware >was a VAX emulator IIRC called FX11: it allowed running unmodified >VAX binaries. There was also a static binary translator for DecStation binaries. I never used it, but a collegue tried to. He found that on the Prolog systems that he tried it with (I think it was Quintus or SICStus), it did not work, because that system did unusual things with the binary, and that did not work on the result of the binary translation. Moral of the story: Better use dynamic binary translation (which Apple did for their 68K->PowerPC transition at around the same time). >OTOH Unix for Alpha was claimed to be pure 64-bit. It depends on the kind of purity you are aspiring to. After a bunch of renamings it was finally called Tru64 UNIX. Not Pur64, but Tru64:-) Before that, it was called Digital UNIX (but once DEC had been bought by Compaq, that was no longer appropriate), and before that, DEC OSF/1 AXP. The C environment for DEC OSF/1 was an I32LP64 setup, not an ILP64 setup, so can you really call it pure? In addition there were some OS features for running ILP32 programs, similar to Linux' MAP_32BIT flag for mmap(). IIRC Netscape Navigator was compiled as ILP32 program (the C compiler had a flag for that), and needed these OS features. - anton -- 'Anyone trying for "industrial quality" ISA should avoid undefined behavior.' Mitch Alsup, <c17fcd89-f024-40e7-a594-88a85ac10d20o@googlegroups.com>
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-08-04 00:04 +0000 |
| Subject | Re: VAX |
| Message-ID | <106otf6$1sov2$1@dont-email.me> |
| In reply to | #112847 |
On Sun, 03 Aug 2025 16:51:10 GMT, Anton Ertl wrote: > The C environment for DEC OSF/1 was an I32LP64 setup, not an ILP64 > setup, so can you really call it pure? As far as I’m aware, I32LP64 is the standard across 64-bit *nix systems. Microsoft’s compilers for 64-bit Windows do LLP64. Not aware of any platforms that do/did ILP64.
[toc] | [prev] | [next] | [standalone]
| From | BGB <cr88192@gmail.com> |
|---|---|
| Date | 2025-08-03 21:07 -0500 |
| Subject | Re: VAX |
| Message-ID | <106p4k6$1u13o$1@dont-email.me> |
| In reply to | #112855 |
On 8/3/2025 7:04 PM, Lawrence D'Oliveiro wrote: > On Sun, 03 Aug 2025 16:51:10 GMT, Anton Ertl wrote: > >> The C environment for DEC OSF/1 was an I32LP64 setup, not an ILP64 >> setup, so can you really call it pure? > > As far as I’m aware, I32LP64 is the standard across 64-bit *nix systems. > > Microsoft’s compilers for 64-bit Windows do LLP64. Not aware of any > platforms that do/did ILP64. Yeah, pretty much nothing does ILP64, and doing so would actually be a problem. Also, C type names: char : 8 bit short : 16 bit int : 32 bit long : 64 bit long long: 64 bit If 'int' were 64-bits, then what about 16 and/or 32 bit types. short short? long short? ... Current system seems preferable. Well, at least in absence of maybe having the compiler specify actual fixed-size types. Or, say, what if there was a world where the actual types were, say: _Int8, _Int16, _Int32, _Int64, _Int128 And, then, say: char, short, int, long, ... Were seen as aliases. Well, maybe along with __int64 and friends, but __int64 and _Int64 could be seen as equivalent. Then of course, the "stdint.h" types. Traditionally, these are a bunch of typedef's to the 'int' and friends. But, one can imagine a hypothetical world where stdint.h contained things like, say: typedef _Int32 int32_t; ...
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <Peter@Iron-Spring.com> |
|---|---|
| Date | 2025-08-03 20:39 -0700 |
| Subject | Re: VAX |
| Message-ID | <106pa28$1v29q$1@dont-email.me> |
| In reply to | #112857 |
On 8/3/25 19:07, BGB wrote: > On 8/3/2025 7:04 PM, Lawrence D'Oliveiro wrote: >> On Sun, 03 Aug 2025 16:51:10 GMT, Anton Ertl wrote: >> >>> The C environment for DEC OSF/1 was an I32LP64 setup, not an ILP64 >>> setup, so can you really call it pure? >> >> As far as I’m aware, I32LP64 is the standard across 64-bit *nix systems. >> >> Microsoft’s compilers for 64-bit Windows do LLP64. Not aware of any >> platforms that do/did ILP64. > > Yeah, pretty much nothing does ILP64, and doing so would actually be a > problem. > > Also, C type names: > char : 8 bit > short : 16 bit > int : 32 bit > long : 64 bit > long long: 64 bit > > If 'int' were 64-bits, then what about 16 and/or 32 bit types. > short short? > long short? > ... > > Current system seems preferable. > Well, at least in absence of maybe having the compiler specify actual > fixed-size types. > > Or, say, what if there was a world where the actual types were, say: > _Int8, _Int16, _Int32, _Int64, _Int128 > And, then, say: > char, short, int, long, ... > Were seen as aliases. > > Well, maybe along with __int64 and friends, but __int64 and _Int64 could > be seen as equivalent. > > > Then of course, the "stdint.h" types. > Traditionally, these are a bunch of typedef's to the 'int' and friends. > But, one can imagine a hypothetical world where stdint.h contained > things like, say: > typedef _Int32 int32_t; > > Like PL/I which lets you specify any precision: FIXED BINARY(31), FIXED BINARY(63) etc. C keeps borrowing more and more PL/I features.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-08-04 04:50 +0000 |
| Subject | Re: VAX |
| Message-ID | <106pe63$1vp0f$1@dont-email.me> |
| In reply to | #112858 |
On Sun, 3 Aug 2025 20:39:52 -0700, Peter Flass wrote: > C keeps borrowing more and more PL/I features. Struct definitions with level numbers??
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2025-08-04 12:35 +0300 |
| Subject | Re: VAX |
| Message-ID | <20250804123501.00004df2@yahoo.com> |
| In reply to | #112858 |
On Sun, 3 Aug 2025 20:39:52 -0700 Peter Flass <Peter@Iron-Spring.com> wrote: > On 8/3/25 19:07, BGB wrote: > > On 8/3/2025 7:04 PM, Lawrence D'Oliveiro wrote: > >> On Sun, 03 Aug 2025 16:51:10 GMT, Anton Ertl wrote: > >> > >>> The C environment for DEC OSF/1 was an I32LP64 setup, not an ILP64 > >>> setup, so can you really call it pure? > >> > >> As far as I’m aware, I32LP64 is the standard across 64-bit *nix > >> systems. > >> > >> Microsoft’s compilers for 64-bit Windows do LLP64. Not aware of any > >> platforms that do/did ILP64. > > > > Yeah, pretty much nothing does ILP64, and doing so would actually > > be a problem. > > > > Also, C type names: > > char : 8 bit > > short : 16 bit > > int : 32 bit > > long : 64 bit > > long long: 64 bit > > > > If 'int' were 64-bits, then what about 16 and/or 32 bit types. > > short short? > > long short? > > ... > > > > Current system seems preferable. > > Well, at least in absence of maybe having the compiler specify > > actual fixed-size types. > > > > Or, say, what if there was a world where the actual types were, say: > > _Int8, _Int16, _Int32, _Int64, _Int128 > > And, then, say: > > char, short, int, long, ... > > Were seen as aliases. > > > > Well, maybe along with __int64 and friends, but __int64 and _Int64 > > could be seen as equivalent. > > > > > > Then of course, the "stdint.h" types. > > Traditionally, these are a bunch of typedef's to the 'int' and > > friends. But, one can imagine a hypothetical world where stdint.h > > contained things like, say: > > typedef _Int32 int32_t; > > > > > > Like PL/I which lets you specify any precision: FIXED BINARY(31), > FIXED BINARY(63) etc. > C23 does not let you specify any precision. Implementation defines BITINT_MAXWIDTH that, according to my understanding, (I didn't read the standard) is allowed to be quite small. It seems, that in real life BITINT_MAXWIDTH >= 128 will be supported on all platforms that would go to trouble of implementing complete C23, even on 32-bit hardware. > C keeps borrowing more and more PL/I features. > How can we know that the feature is borrowed from PL/1 and not for few other languages that had similar features?
[toc] | [prev] | [next] | [standalone]
| From | BGB <cr88192@gmail.com> |
|---|---|
| Date | 2025-08-04 11:59 -0500 |
| Subject | Re: VAX |
| Message-ID | <106qoue$28rbu$2@dont-email.me> |
| In reply to | #112858 |
On 8/3/2025 10:39 PM, Peter Flass wrote:
> On 8/3/25 19:07, BGB wrote:
>> On 8/3/2025 7:04 PM, Lawrence D'Oliveiro wrote:
>>> On Sun, 03 Aug 2025 16:51:10 GMT, Anton Ertl wrote:
>>>
>>>> The C environment for DEC OSF/1 was an I32LP64 setup, not an ILP64
>>>> setup, so can you really call it pure?
>>>
>>> As far as I’m aware, I32LP64 is the standard across 64-bit *nix systems.
>>>
>>> Microsoft’s compilers for 64-bit Windows do LLP64. Not aware of any
>>> platforms that do/did ILP64.
>>
>> Yeah, pretty much nothing does ILP64, and doing so would actually be a
>> problem.
>>
>> Also, C type names:
>> char : 8 bit
>> short : 16 bit
>> int : 32 bit
>> long : 64 bit
>> long long: 64 bit
>>
>> If 'int' were 64-bits, then what about 16 and/or 32 bit types.
>> short short?
>> long short?
>> ...
>>
>> Current system seems preferable.
>> Well, at least in absence of maybe having the compiler specify actual
>> fixed-size types.
>>
>> Or, say, what if there was a world where the actual types were, say:
>> _Int8, _Int16, _Int32, _Int64, _Int128
>> And, then, say:
>> char, short, int, long, ...
>> Were seen as aliases.
>>
>> Well, maybe along with __int64 and friends, but __int64 and _Int64
>> could be seen as equivalent.
>>
>>
>> Then of course, the "stdint.h" types.
>> Traditionally, these are a bunch of typedef's to the 'int' and friends.
>> But, one can imagine a hypothetical world where stdint.h contained
>> things like, say:
>> typedef _Int32 int32_t;
>>
>>
>
> Like PL/I which lets you specify any precision: FIXED BINARY(31), FIXED
> BINARY(63) etc.
>
> C keeps borrowing more and more PL/I features.
>
This would be _BitInt(n) ...
Though, despite originally making it so that power-of-2 _BitInt(n) would
map to the corresponding types when available, I ended up later needing
to make them distinct, to remember the exact bit-widths, and to preserve
the expected overflow behavior for these widths.
There is apparently a discrepancy between BGBCC and Clang when it comes
to this type:
BGBCC: Storage is padded to a power of 2;
Up to 256 bits, after which it is the next multiple of 128.
Clang: Storage is the next multiple of 1 byte.
But, efficiently loading and storing arbitrary N byte values is a harder
problem than using a power-of-2 type and then ignoring or
masking/extending the HOBs.
Main harder case is store, which would need to be turned into a
Load+Mask+Store absent special ISA support.
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2025-08-04 12:19 +0300 |
| Subject | Re: VAX |
| Message-ID | <20250804121938.0000122a@yahoo.com> |
| In reply to | #112857 |
On Sun, 3 Aug 2025 21:07:02 -0500 BGB <cr88192@gmail.com> wrote: > On 8/3/2025 7:04 PM, Lawrence D'Oliveiro wrote: > > On Sun, 03 Aug 2025 16:51:10 GMT, Anton Ertl wrote: > > > >> The C environment for DEC OSF/1 was an I32LP64 setup, not an ILP64 > >> setup, so can you really call it pure? > > > > As far as I’m aware, I32LP64 is the standard across 64-bit *nix > > systems. > > > > Microsoft’s compilers for 64-bit Windows do LLP64. Not aware of any > > platforms that do/did ILP64. > > Yeah, pretty much nothing does ILP64, and doing so would actually be > a problem. > > Also, C type names: > char : 8 bit > short : 16 bit > int : 32 bit Except in embedded 16 bit are not rare > long : 64 bit Except for majority of the world where long is 32 bit > long long: 64 bit > > If 'int' were 64-bits, then what about 16 and/or 32 bit types. > short short? > long short? > ... > > Current system seems preferable. > Well, at least in absence of maybe having the compiler specify actual > fixed-size types. > > Or, say, what if there was a world where the actual types were, say: > _Int8, _Int16, _Int32, _Int64, _Int128 > And, then, say: > char, short, int, long, ... > Were seen as aliases. > Actually, in our world the latest C standard (C23) has them, but the spelling is different: _BitInt(32) and unsigned _BitInt(32). I'm not sure if any major compiler already has them implemented. Bing copilot says that clang does, but I don't tend to believe eveything Bing copilot says. > Well, maybe along with __int64 and friends, but __int64 and _Int64 > could be seen as equivalent. > > > Then of course, the "stdint.h" types. > Traditionally, these are a bunch of typedef's to the 'int' and > friends. But, one can imagine a hypothetical world where stdint.h > contained things like, say: > typedef _Int32 int32_t; > > > ... > >
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2025-08-04 12:09 +0000 |
| Subject | Re: VAX |
| Message-ID | <2025Aug4.140932@mips.complang.tuwien.ac.at> |
| In reply to | #112862 |
Michael S <already5chosen@yahoo.com> writes:
>Actually, in our world the latest C standard (C23) has them, but the
>spelling is different: _BitInt(32) and unsigned _BitInt(32).
>I'm not sure if any major compiler already has them implemented. Bing
>copilot says that clang does, but I don't tend to believe eveything Bing
>copilot says.
I asked godbolt, and tried the following program:
typedef ump unsigned _BitInt(65535);
ump sum3(ump a, ump b, ump c)
{
return a+b+c;
}
and for the C setting gcc-15.1 AMD64 produces 129 lines of assembly
language code; for C++ it complains about the syntax. For 65536 bits,
it complains about being beyond the maximum number of 65535 bits.
For the same program with the C setting clang-20.1 produces 29547
lines of assembly language code; that's more than 28 instructions for
every 64-bit word of output, which seems excessive to me, even if you
don't use ADX instructions (which clang apparently does not); I expect
that clang will produce better code at some point in the future.
Compiling this function also takes noticable time, and when I ask for
1000000 bits, clang still does complain about too many bits, but
godbolt's timeout strikes; I finally found out clang's limit: 8388608
bits. On clang-20.1 the C++ setting also accepts this kind of input.
Followups set to comp.arch.
- anton
--
'Anyone trying for "industrial quality" ISA should avoid undefined behavior.'
Mitch Alsup, <c17fcd89-f024-40e7-a594-88a85ac10d20o@googlegroups.com>
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2025-08-04 14:51 +0000 |
| Subject | Re: VAX |
| Message-ID | <2025Aug4.165141@mips.complang.tuwien.ac.at> |
| In reply to | #112866 |
anton@mips.complang.tuwien.ac.at (Anton Ertl) writes:
>Michael S <already5chosen@yahoo.com> writes:
>>Actually, in our world the latest C standard (C23) has them, but the
>>spelling is different: _BitInt(32) and unsigned _BitInt(32).
>>I'm not sure if any major compiler already has them implemented. Bing
>>copilot says that clang does, but I don't tend to believe eveything Bing
>>copilot says.
>
>I asked godbolt, and tried the following program:
>
>typedef ump unsigned _BitInt(65535);
The actual compiling version is:
typedef unsigned _BitInt(65535) ump;
ump sum3(ump a, ump b, ump c)
{
return a+b+c;
}
>and for the C setting gcc-15.1 AMD64 produces 129 lines of assembly
>language code; for C++ it complains about the syntax. For 65536 bits,
>it complains about being beyond the maximum number of 65535 bits.
>
>For the same program with the C setting clang-20.1 produces 29547
>lines of assembly language code; that's more than 28 instructions for
>every 64-bit word of output, which seems excessive to me, even if you
>don't use ADX instructions (which clang apparently does not); I expect
>that clang will produce better code at some point in the future.
>Compiling this function also takes noticable time, and when I ask for
>1000000 bits, clang still does complain about too many bits, but
>godbolt's timeout strikes; I finally found out clang's limit: 8388608
>bits. On clang-20.1 the C++ setting also accepts this kind of input.
- anton
--
'Anyone trying for "industrial quality" ISA should avoid undefined behavior.'
Mitch Alsup, <c17fcd89-f024-40e7-a594-88a85ac10d20o@googlegroups.com>
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2025-08-04 18:28 +0300 |
| Subject | Re: VAX |
| Message-ID | <20250804182839.00000600@yahoo.com> |
| In reply to | #112870 |
On Mon, 04 Aug 2025 12:09:32 GMT
anton@mips.complang.tuwien.ac.at (Anton Ertl) wrote:
> Michael S <already5chosen@yahoo.com> writes:
> >Actually, in our world the latest C standard (C23) has them, but the
> >spelling is different: _BitInt(32) and unsigned _BitInt(32).
> >I'm not sure if any major compiler already has them implemented. Bing
> >copilot says that clang does, but I don't tend to believe eveything
> >Bing copilot says.
>
> I asked godbolt, and tried the following program:
>
It turned out that I didn't need even goldbolt.
I already had sufficiently advanced gcc and clang installed on my new
Windows PC at work. I probably have them installed on very old home PC
as well, but now I am at work. Playing with compilers instead of
working.
> typedef ump unsigned _BitInt(65535);
>
> ump sum3(ump a, ump b, ump c)
> {
> return a+b+c;
> }
>
> and for the C setting gcc-15.1 AMD64 produces 129 lines of assembly
> language code; for C++ it complains about the syntax. For 65536 bits,
> it complains about being beyond the maximum number of 65535 bits.
>
> For the same program with the C setting clang-20.1 produces 29547
> lines of assembly language code; that's more than 28 instructions for
> every 64-bit word of output, which seems excessive to me, even if you
> don't use ADX instructions (which clang apparently does not); I expect
> that clang will produce better code at some point in the future.
> Compiling this function also takes noticable time, and when I ask for
> 1000000 bits, clang still does complain about too many bits, but
> godbolt's timeout strikes; I finally found out clang's limit: 8388608
> bits. On clang-20.1 the C++ setting also accepts this kind of input.
>
> Followups set to comp.arch.
>
> - anton
I didn't pay much attention to code size yet. Had seen two other
worrying things.
1. Both gcc and clang happily* accept _BitInt() syntax even when
-std=c17 or lower. Is not here a potential name clash for existing
sources that use _BitInt() as a name of the function? I should think
more about it.
2. Windows-specific.
gcc and clang appear to have different ABIs for return value of type
_BitInt(128).
* - the only sign of less than perfect happiness is a warning produced
with -pedantic flag.
Cross-posted to c.lang.c
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2025-08-04 09:53 -0700 |
| Subject | Re: VAX |
| Message-ID | <87sei7do4g.fsf@example.invalid> |
| In reply to | #112874 |
Michael S <already5chosen@yahoo.com> writes:
> On Mon, 04 Aug 2025 12:09:32 GMT
> anton@mips.complang.tuwien.ac.at (Anton Ertl) wrote:
[...]
>> typedef ump unsigned _BitInt(65535);
The correct syntax is :
typedef unsigned _BitInt(65535) ump;
>> ump sum3(ump a, ump b, ump c)
>> {
>> return a+b+c;
>> }
[...]
> 1. Both gcc and clang happily* accept _BitInt() syntax even when
> -std=c17 or lower. Is not here a potential name clash for existing
> sources that use _BitInt() as a name of the function? I should think
> more about it.
In C17 and earlier, _BitInt is a reserved identifier. Any attempt to
use it has undefined behavior. That's exactly why new keywords are
often defined with that ugly syntax.
Both gcc and clang warn about _BitInt with invoked with "-std=c17 -pedantic".
[...]
> * - the only sign of less than perfect happiness is a warning produced
> with -pedantic flag.
Yes, both are behaving reasonably. If you don't use "-pedantic",
you're telling the compiler you don't want standard conformance.
(I'd be happier if conformance were the default, but we're stuck
with it.) But accepting _BitInt in pre-C23 mode is conforming.
> Cross-posted to c.lang.c
I've kept the cross-post to comp.lang.c and comp.arch.
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */
[toc] | [prev] | [next] | [standalone]
| From | Thomas Koenig <tkoenig@netcologne.de> |
|---|---|
| Date | 2025-08-04 16:58 +0000 |
| Subject | Re: VAX |
| Message-ID | <106qoqs$2913l$2@dont-email.me> |
| In reply to | #112882 |
Keith Thompson <Keith.S.Thompson+u@gmail.com> schrieb: > In C17 and earlier, _BitInt is a reserved identifier. Any attempt to > use it has undefined behavior. That's exactly why new keywords are > often defined with that ugly syntax. Sometimes I think there is reason to Fortran's approach of not having defined keywords - old programs just continue to run, even with new statements or intrinsic procedures, maybe with an addition of an EXTERNAL statement. -- This USENET posting was made without artificial intelligence, artificial impertinence, artificial arrogance, artificial stupidity, artificial flavorings or artificial colorants.
[toc] | [prev] | [next] | [standalone]
| From | "Brian G. Lucas" <bagel99@gmail.com> |
|---|---|
| Date | 2025-08-05 13:03 -0500 |
| Subject | Re: VAX |
| Message-ID | <106th0t$2th5u$1@dont-email.me> |
| In reply to | #112884 |
On 8/4/25 11:58 AM, Thomas Koenig wrote: > Keith Thompson <Keith.S.Thompson+u@gmail.com> schrieb: > >> In C17 and earlier, _BitInt is a reserved identifier. Any attempt to >> use it has undefined behavior. That's exactly why new keywords are >> often defined with that ugly syntax. > > Sometimes I think there is reason to Fortran's approach of not > having defined keywords - old programs just continue to run, even > with new statements or intrinsic procedures, maybe with an addition > of an EXTERNAL statement. I agree. I designed my personal programming language <https://github.com/bagel99/esl> without reserved words. It is really not that hard to do in a compiler. brian
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2025-08-04 22:03 +0300 |
| Subject | Re: VAX |
| Message-ID | <20250804220315.00007240@yahoo.com> |
| In reply to | #112882 |
On Mon, 04 Aug 2025 09:53:51 -0700
Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
> Michael S <already5chosen@yahoo.com> writes:
> > On Mon, 04 Aug 2025 12:09:32 GMT
> > anton@mips.complang.tuwien.ac.at (Anton Ertl) wrote:
> [...]
> >> typedef ump unsigned _BitInt(65535);
>
> The correct syntax is :
>
> typedef unsigned _BitInt(65535) ump;
>
> >> ump sum3(ump a, ump b, ump c)
> >> {
> >> return a+b+c;
> >> }
>
> [...]
>
> > 1. Both gcc and clang happily* accept _BitInt() syntax even when
> > -std=c17 or lower. Is not here a potential name clash for existing
> > sources that use _BitInt() as a name of the function? I should think
> > more about it.
>
> In C17 and earlier, _BitInt is a reserved identifier. Any attempt to
> use it has undefined behavior. That's exactly why new keywords are
> often defined with that ugly syntax.
>
That is language lawyer's type of reasoning. Normally gcc maintainers
are wiser than that because, well, by chance gcc happens to be widely
used production compiler. I don't know why this time they had chosen
less conservative road.
[toc] | [prev] | [next] | [standalone]
Page 20 of 50 — ← Prev page 1 … 18 19 [20] 21 22 … 50 Next page →
Back to top | Article view | comp.arch
csiph-web