Re: A right alternative to IEEE-754's format

Newsgroups	comp.arch
Date	2018-04-18 14:10 -0700
References	(16 earlier) <paqn14$747$1@gioia.aioe.org> <pasm94$bhp$1@dont-email.me> <pb39l3$1gqe$1@gioia.aioe.org> <c878e1f3-29e3-42c1-ae24-bc2279f753a4@googlegroups.com> <9NsBC.2041$eR.1329@fx30.iad>
Message-ID	<e66232e2-e537-4bd9-96d9-07ac0f756594@googlegroups.com> (permalink)
Subject	Re: A right alternative to IEEE-754's format
From	matthey7@gmail.com

Show all headers | View raw

On Tuesday, April 17, 2018 at 3:27:51 PM UTC-5, EricP wrote:
> Another issue solved with a compacting linker is with load and store
> offsets sizes. For global variables the compiler doesn't know
> how far away they might be, or if they might be located in a DLL.
> For the vast majority of global variables, they are linked locally
> and data structures are smaller than 2GB, so 32 bit offsets would do.
> But you don't find this out until link time.
> It is easiest if all loads and stores are emitted as
> 64-bit PC-relative offsets, but that wastes a lot of space.

You are really talking about deficiencies in the x86_64 ISA and the statically linked library implementation. The x86_64 ISA does not support an immediate displacement larger than 32 bits. This means significant changes to the code emitted instead of a minor adjustment of the immediate displacement. The x86_64 ABI partially gets around these limitations with a multitude of code models.

https://eli.thegreenplace.net/2012/01/03/understanding-the-x64-code-models

The large number of code models, limitations and inconsistencies of the x86_64 ISA no doubt create challenges for compiler designers.

There is a better way for a 64 bit CISC like ISA with variable length instructions, 16 GP registers and good code density to handle this. We start with the following addressing modes:

(d16,PC) and (d16,Rn) <- fast and more compact than x86_64 limitations
(d32,PC) <- fast and more compact than (d32,Rn)
(d32,Rn) <- needed for data accesses
(d64,Rn) and (d64,PC) <- rarely used for large data and can be relatively slow

Now the compiler can emit unsized displacements and branches and the assembler and/or cross-module optimizer can find the right size with minimal changes to the code. Code can go anywhere in the 64 bit address space (better security and MMU becomes optional) rather than the low 2 or 4 GB address space. Multi-instruction address generation is unnecessary. Trampolines are unnecessary. Fewer code models are necessary. Substantially better code density is achieved with (d16,PC). Merging text/code and data sections (requires PC relative stores) gives further code density improvements as PC relative accesses can give shorter instructions. Finally, 64 bit PIC code is achieved without a performance penalty or limitations. The assembler code and disassemblies are easier to read and debug. A more efficient 16 bit variable length encoding with no prefixes can be used. All this can be done with a 64 bit 68k ISA with fewer changes than were needed for x86_64. I could finish my 68k_64 ISA but then CPU designers would complain than it is too complex and certain addressing modes are not common enough so it would be a waste of my time. Sorry compiler designers. Complexity must go into the compiler instead of the CPU design except for high performance x86_64 CPUs.

The better way to do libraries than .so/dll static link libraries is to open dynamic libraries which return a library base which is then used with an offset to jump to functions and access objects/variables. The library can then go anywhere in the 64 bit address space for better security and does not require an MMU. There are no conflicts with loading to a static address. A version number can be requested on open to get newer versions of the library giving fewer version problems than statically linked libraries.

We are stuck using inferior technology from the past when better technology from the past is available. ;)

> A compacting linker solves this issue too. If it locates the
> majority of small data structures close to the code,
> then it can use 32-bit PC-offsets and patch the load/store
> instructions as appropriate. Any data structures larger
> than 2GB can be located farther away and use 64-bit offsets.
> Similarly for DLL export variables.

Sounds like the x86_64 ABI Medium Code Model. See the link I posted above.

> The compiler also needs to emit alignment hints into the
> object code as the linker needs to know where aligned loop
> starts or branch destinations should be,
> with no-op insertion by the linker.

Most compilers already emit alignment directives for the assembler. The assembler could pass them on to the linker or cross-module optimizer as well or separate files with cross-module optimization data can be generated.

> So this meant that some work that is currently usually done
> by the compiler, local branch resolution and code alignment,
> would be handed over to the compacting linker.
> Sames code, it just runs in a different place.

I tend to favor a 2nd pass through the compiler for cross-module optimization rather than moving much of the functionality of the compiler into the linker.

Back to comp.arch | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Re: A right alternative to IEEE-754's format jim.brakefield@ieee.org - 2018-03-28 16:23 -0700
  Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-03-29 08:59 -0700
    Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-03-29 15:56 -0500
      Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-03-29 15:58 -0500
      Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-03-30 11:35 +0200
        Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-03-30 12:08 +0000
          Re: A right alternative to IEEE-754's format already5chosen@yahoo.com - 2018-03-30 06:12 -0700
            Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-03-30 14:28 +0000
              Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-03-30 09:35 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-03-30 16:51 +0000
            Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-03-30 09:26 -0700
          Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-03-30 15:23 +0200
            Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-03-30 14:38 +0000
              Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-03-30 20:23 +0200
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-03-31 08:28 +0000
                Re: A right alternative to IEEE-754's format anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2018-03-31 14:05 +0000
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-03-31 17:23 +0200
                Re: A right alternative to IEEE-754's format anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2018-03-31 15:43 +0000
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-03-31 10:56 -0700
                Re: A right alternative to IEEE-754's format anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2018-04-01 12:44 +0000
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-01 13:03 +0000
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-01 15:44 +0200
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-01 14:14 +0000
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-01 12:02 -0700
                Re: A right alternative to IEEE-754's format Niklas Holsti <niklas.holsti@tidorum.invalid> - 2018-03-31 21:37 +0300
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-03-31 19:45 +0200
                Re: A right alternative to IEEE-754's format anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2018-03-31 17:57 +0000
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-03-31 22:50 +0200
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-03-31 15:11 -0700
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-03-31 19:53 -0700
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-02 16:08 +0200
                Re: A right alternative to IEEE-754's format already5chosen@yahoo.com - 2018-04-02 11:05 -0700
                Re: A right alternative to IEEE-754's format Ivan Godard <ivan@millcomputing.com> - 2018-04-02 11:36 -0700
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-02 11:48 -0700
                Re: A right alternative to IEEE-754's format Melzzzzz <Melzzzzz@zzzzz.com> - 2018-04-02 19:00 +0000
                Re: A right alternative to IEEE-754's format "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid> - 2018-04-02 13:28 -0700
                Re: A right alternative to IEEE-754's format John Levine <johnl@taugh.com> - 2018-04-03 01:39 +0000
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-03 10:30 +0200
                Re: A right alternative to IEEE-754's format already5chosen@yahoo.com - 2018-04-02 14:14 -0700
                Re: A right alternative to IEEE-754's format Ivan Godard <ivan@millcomputing.com> - 2018-04-02 16:11 -0700
                Re: A right alternative to IEEE-754's format Richard Damon <Richard@Damon-Family.org> - 2018-04-02 22:49 -0400
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-03 08:16 +0200
                Re: A right alternative to IEEE-754's format anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2018-04-01 12:47 +0000
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-01 12:06 -0700
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-02 22:08 +0200
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-02 14:14 -0700
                Re: A right alternative to IEEE-754's format Ivan Godard <ivan@millcomputing.com> - 2018-04-02 16:16 -0700
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-02 16:48 -0700
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-03 11:31 +0200
                Re: A right alternative to IEEE-754's format Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-05 07:01 -0700
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-05 16:09 +0200
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-03 11:12 +0200
                Re: A right alternative to IEEE-754's format mrs@kithrup.com (Mike Stump) - 2018-04-03 18:27 +0000
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-03 11:45 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-03 19:41 +0000
                Re: A right alternative to IEEE-754's format George Neuner <gneuner2@comcast.net> - 2018-04-04 11:09 -0400
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-04 17:02 +0000
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-04 11:33 -0700
                Re: A right alternative to IEEE-754's format John Levine <johnl@taugh.com> - 2018-04-04 19:36 +0000
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-04 22:02 +0000
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-04 22:04 +0000
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-04 16:49 -0700
                Re: A right alternative to IEEE-754's format George Neuner <gneuner2@comcast.net> - 2018-04-05 16:18 -0400
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-04 22:41 +0200
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-04 16:51 -0700
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-05 13:26 +0200
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-04 22:31 +0200
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-03 14:41 -0700
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-03 16:49 -0700
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-02 21:49 +0200
                Re: A right alternative to IEEE-754's format already5chosen@yahoo.com - 2018-04-02 14:28 -0700
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-03 11:45 +0200
                Re: A right alternative to IEEE-754's format already5chosen@yahoo.com - 2018-04-03 03:53 -0700
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-03 14:05 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-09 07:30 -0400
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-09 13:48 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-09 12:02 -0400
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-09 16:45 +0000
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-09 10:22 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-09 17:39 +0000
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-10 13:59 -0700
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-09 13:43 -0400
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-09 17:56 +0000
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-09 14:47 -0400
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-09 10:19 -0700
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-10 13:26 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-12 11:23 -0400
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-12 11:17 -0700
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-12 12:31 -0700
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-12 13:58 -0700
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-12 17:12 -0400
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-12 15:18 -0700
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-12 16:43 -0700
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-12 19:45 -0700
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-12 20:45 -0700
                Re: A right alternative to IEEE-754's format "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid> - 2018-04-12 21:34 -0700
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-13 09:09 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-13 08:51 -0400
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-13 05:57 -0700
                Re: A right alternative to IEEE-754's format Alex McDonald <alex@rivadpm.com> - 2018-04-13 14:17 +0100
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-13 06:23 -0700
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-12 21:36 -0700
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-12 23:50 -0500
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-12 21:53 -0700
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-12 21:56 -0700
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-13 02:37 -0500
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-13 02:26 -0500
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-13 10:14 +0200
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-13 03:19 -0500
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-13 13:48 +0200
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-13 05:35 -0700
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-13 09:22 -0400
                Re: A right alternative to IEEE-754's format Ivan Godard <ivan@millcomputing.com> - 2018-04-13 11:36 -0700
                Re: A right alternative to IEEE-754's format already5chosen@yahoo.com - 2018-04-13 05:21 -0700
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-13 15:28 +0200
                Re: A right alternative to IEEE-754's format already5chosen@yahoo.com - 2018-04-13 07:10 -0700
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-13 16:43 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-13 12:10 -0400
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-13 10:43 -0700
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-13 09:34 -0400
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-13 06:36 -0700
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-13 12:35 -0400
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-13 12:36 -0400
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-14 12:15 +0200
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-13 10:58 -0700
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-13 11:03 -0700
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-13 11:21 -0700
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-13 14:30 -0400
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-13 11:36 -0700
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-13 11:31 -0700
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-13 11:34 -0700
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-13 14:36 -0400
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-13 14:38 -0400
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-13 18:58 +0000
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-13 15:02 -0400
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-13 15:42 -0700
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-13 16:48 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-13 12:48 -0400
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-14 12:48 +0200
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-14 11:13 -0500
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-14 20:18 +0200
                Re: A right alternative to IEEE-754's format matthey7@gmail.com - 2018-04-14 09:19 -0700
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-14 20:44 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-16 18:55 -0400
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-16 19:02 -0400
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-16 17:11 -0700
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-16 17:32 -0700
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-16 20:42 -0700
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-17 10:14 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-17 09:49 -0400
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-17 16:53 +0200
                Re: A right alternative to IEEE-754's format Ivan Godard <ivan@millcomputing.com> - 2018-04-17 16:38 -0700
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-17 11:16 -0700
                Re: A right alternative to IEEE-754's format matthey7@gmail.com - 2018-04-16 21:59 -0700
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-17 10:01 -0400
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-17 08:31 -0700
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-17 10:03 +0200
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-17 08:27 -0700
                Re: A right alternative to IEEE-754's format anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2018-04-17 15:28 +0000
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-17 16:23 +0000
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-17 12:33 -0700
                Re: A right alternative to IEEE-754's format EricP <ThatWouldBeTelling@thevillage.com> - 2018-04-17 16:27 -0400
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-18 09:12 +0200
                Re: A right alternative to IEEE-754's format matthey7@gmail.com - 2018-04-18 14:10 -0700
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-18 15:30 -0700
                Re: A right alternative to IEEE-754's format matthey7@gmail.com - 2018-04-18 17:48 -0700
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-19 08:42 +0200
                Re: A right alternative to IEEE-754's format EricP <ThatWouldBeTelling@thevillage.com> - 2018-04-19 13:35 -0400
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-19 13:04 -0500
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-19 12:18 -0700
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-20 16:35 -0500
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-20 15:24 -0700
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-19 11:57 -0700
                Re: A right alternative to IEEE-754's format EricP <ThatWouldBeTelling@thevillage.com> - 2018-04-20 15:12 -0400
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-19 12:48 -0700
                Re: A right alternative to IEEE-754's format matthey7@gmail.com - 2018-04-19 15:52 -0700
                Re: A right alternative to IEEE-754's format Ivan Godard <ivan@millcomputing.com> - 2018-04-22 10:52 -0700
                Re: A right alternative to IEEE-754's format EricP <ThatWouldBeTelling@thevillage.com> - 2018-04-22 14:42 -0400
                Re: A right alternative to IEEE-754's format Ivan Godard <ivan@millcomputing.com> - 2018-04-22 12:36 -0700
                Re: A right alternative to IEEE-754's format matthey7@gmail.com - 2018-04-19 16:05 -0700
                Re: A right alternative to IEEE-754's format EricP <ThatWouldBeTelling@thevillage.com> - 2018-04-20 15:15 -0400
                Re: A right alternative to IEEE-754's format EricP <ThatWouldBeTelling@thevillage.com> - 2018-04-19 13:16 -0400
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-19 10:29 -0700
                Re: A right alternative to IEEE-754's format EricP <ThatWouldBeTelling@thevillage.com> - 2018-04-20 14:53 -0400
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-20 13:23 -0700
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-19 12:45 -0700
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-20 16:17 -0500
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-17 10:16 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-17 10:22 -0400
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-17 16:57 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-17 11:33 -0400
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-17 20:53 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-17 16:38 -0400
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-17 23:13 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-17 18:21 -0400
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-13 09:15 -0400
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-13 16:23 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-13 13:06 -0400
                Re: A right alternative to IEEE-754's format mrs@kithrup.com (Mike Stump) - 2018-04-22 19:59 +0000
                Re: A right alternative to IEEE-754's format mrs@kithrup.com (Mike Stump) - 2018-04-22 19:52 +0000
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-23 08:42 -0400
                Re: A right alternative to IEEE-754's format Bill Findlay <findlaybill@blueyonder.co.uk> - 2018-04-23 14:11 +0100
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-23 15:35 +0200
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-23 11:37 -0400
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-24 17:36 +0200
                Re: A right alternative to IEEE-754's format matthey7@gmail.com - 2018-04-12 15:13 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-13 10:47 +0000
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-13 10:30 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-13 17:52 +0000
                Re: A right alternative to IEEE-754's format Ivan Godard <ivan@millcomputing.com> - 2018-04-12 13:47 -0700
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-12 16:57 -0400
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-13 09:44 -0400
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-13 10:57 -0700
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-13 14:09 -0400
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-13 14:12 -0700
                Re: A right alternative to IEEE-754's format Stephen Fuld <SFuld@alumni.cmu.edu.invalid> - 2018-04-13 14:50 -0700
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-13 17:26 -0500
                Re: A right alternative to IEEE-754's format Stephen Fuld <SFuld@alumni.cmu.edu.invalid> - 2018-04-13 15:30 -0700
                Re: A right alternative to IEEE-754's format John Levine <johnl@taugh.com> - 2018-04-13 22:38 +0000
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-14 08:21 +0000
                Re: A right alternative to IEEE-754's format Alex McDonald <alex@rivadpm.com> - 2018-04-14 11:55 +0100
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-14 11:20 -0500
                Re: A right alternative to IEEE-754's format Stephen Fuld <SFuld@alumni.cmu.edu.invalid> - 2018-04-14 09:30 -0700
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-14 09:35 -0700
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-14 11:36 -0500
                Re: A right alternative to IEEE-754's format John Levine <johnl@taugh.com> - 2018-04-13 22:34 +0000
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-13 17:27 -0500
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-13 15:48 -0700
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-14 09:45 +0200
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-14 11:29 -0500
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-15 21:36 +0200
                Re: A right alternative to IEEE-754's format already5chosen@yahoo.com - 2018-04-15 13:26 -0700
                Re: A right alternative to IEEE-754's format already5chosen@yahoo.com - 2018-04-15 13:47 -0700
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-15 13:33 -0700
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-16 09:34 +0200
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-16 09:25 +0000
                Re: A right alternative to IEEE-754's format already5chosen@yahoo.com - 2018-04-16 04:38 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-16 14:03 +0000
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-16 07:26 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-16 14:34 +0000
                Re: A right alternative to IEEE-754's format already5chosen@yahoo.com - 2018-04-16 13:48 -0700
                Re: A right alternative to IEEE-754's format Ivan Godard <ivan@millcomputing.com> - 2018-04-16 15:06 -0700
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-16 16:16 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-17 08:58 +0000
                Re: A right alternative to IEEE-754's format Bill Findlay <findlaybill@blueyonder.co.uk> - 2018-04-17 15:53 +0100
                Re: A right alternative to IEEE-754's format Ivan Godard <ivan@millcomputing.com> - 2018-04-17 16:28 -0700
                Re: A right alternative to IEEE-754's format Stephen Fuld <SFuld@alumni.cmu.edu.invalid> - 2018-04-17 18:05 -0700
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-18 00:00 -0400
                Re: A right alternative to IEEE-754's format Bill Findlay <findlaybill@blueyonder.co.uk> - 2018-04-18 13:35 +0100
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-18 11:20 -0400
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-18 20:40 +0000
                Re: A right alternative to IEEE-754's format "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-18 07:57 -0400
                Re: A right alternative to IEEE-754's format Bill Findlay <findlaybill@blueyonder.co.uk> - 2018-04-18 13:34 +0100
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-16 11:23 -0500
                Re: A right alternative to IEEE-754's format anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2018-04-16 11:25 +0000
                Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-15 15:42 -0500
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-04-12 20:35 +0200
                Re: A right alternative to IEEE-754's format mrs@kithrup.com (Mike Stump) - 2018-04-22 18:55 +0000
                Re: A right alternative to IEEE-754's format David Brown <david.brown@hesbynett.no> - 2018-05-04 17:00 +0200
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-09 07:29 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-09 15:05 +0000
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-09 12:04 -0400
                Re: A right alternative to IEEE-754's format Ivan Godard <ivan@millcomputing.com> - 2018-04-09 09:17 -0700
                Re: A right alternative to IEEE-754's format mrs@kithrup.com (Mike Stump) - 2018-04-03 18:53 +0000
                Re: A right alternative to IEEE-754's format Quadibloc <jsavard@ecn.ab.ca> - 2018-04-03 13:12 -0700
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-03-31 14:56 -0700
                Re: A right alternative to IEEE-754's format anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2018-04-01 15:53 +0000
                Re: A right alternative to IEEE-754's format Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-01 08:52 -0700
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-01 12:51 -0400
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-02 14:17 +0200
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-02 12:55 +0000
                Re: A right alternative to IEEE-754's format Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-05 07:13 -0700
                Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-05 18:07 +0200
                Re: A right alternative to IEEE-754's format Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-06 01:01 -0700
                Re: A right alternative to IEEE-754's format Walter Banks <walter@bytecraft.com> - 2018-04-07 08:17 -0400
                Re: A right alternative to IEEE-754's format Tim Rentsch <txr@alumni.caltech.edu> - 2018-05-24 09:31 -0700
                Re: A right alternative to IEEE-754's format anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2018-04-01 16:43 +0000
                C is an antique, switch to a real language. ggtgp@yahoo.com - 2018-04-01 19:26 -0700
                Re: C is an antique, switch to a real language. Walter Banks <walter@bytecraft.com> - 2018-04-02 10:43 -0400
                Re: C is an antique, switch to a real language. already5chosen@yahoo.com - 2018-04-02 11:20 -0700
                Re: C is an antique, switch to a real language. ggtgp@yahoo.com - 2018-04-02 22:20 -0700
                Re: C is an antique, switch to a real language. Melzzzzz <Melzzzzz@zzzzz.com> - 2018-04-03 07:16 +0000
                Re: C is an antique, switch to a real language. George Neuner <gneuner2@comcast.net> - 2018-04-03 12:50 -0400
                Re: C is an antique, switch to a real language. nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-03 17:39 +0000
                Re: C is an antique, switch to a real language. George Neuner <gneuner2@comcast.net> - 2018-04-04 11:53 -0400
                Re: C is an antique, switch to a real language. Megol <golem960@gmail.com> - 2018-04-03 02:11 -0700
                Re: C is an antique, switch to a real language. already5chosen@yahoo.com - 2018-04-03 03:08 -0700
                Re: C is an antique, switch to a real language. ggtgp@yahoo.com - 2018-04-03 22:29 -0700
                Re: C is an antique, switch to a real language. Andreas Eder <a_eder_muc@web.de> - 2018-04-04 07:40 +0200
                Re: C is an antique, switch to a real language. nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-04 09:49 +0000
                Re: C is an antique, switch to a real language. Quadibloc <jsavard@ecn.ab.ca> - 2018-04-04 03:39 -0700
                Re: C is an antique, switch to a real language. nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-04 10:52 +0000
                Re: C is an antique, switch to a real language. Quadibloc <jsavard@ecn.ab.ca> - 2018-04-04 11:26 -0700
                Re: C is an antique, switch to a real language. nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-04 19:08 +0000
                Re: C is an antique, switch to a real language. Quadibloc <jsavard@ecn.ab.ca> - 2018-04-05 08:38 -0700
                Re: C is an antique, switch to a real language. MitchAlsup <MitchAlsup@aol.com> - 2018-04-04 09:47 -0700
                Re: C is an antique, switch to a real language. Melzzzzz <Melzzzzz@zzzzz.com> - 2018-04-04 16:51 +0000
                Re: C is an antique, switch to a real language. Andy Valencia <vandys@vsta.org> - 2018-04-04 10:57 -0700
                Re: C is an antique, switch to a real language. Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-05 07:55 +0200
                Re: C is an antique, switch to a real language. anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2018-04-04 10:21 +0000
                Re: C is an antique, switch to a real language. Andy Valencia <vandys@vsta.org> - 2018-04-04 06:40 -0700
                Re: C is an antique, switch to a real language. George Neuner <gneuner2@comcast.net> - 2018-04-04 13:45 -0400
                Re: C is an antique, switch to a real language. "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-02 08:07 -0700
                Re: C is an antique, switch to a real language. Melzzzzz <Melzzzzz@zzzzz.com> - 2018-04-02 16:41 +0000
                Re: C is an antique, switch to a real language. "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-04-02 10:09 -0700
                Re: C is an antique, switch to a real language. ggtgp@yahoo.com - 2018-04-02 22:06 -0700
                Re: C is an antique, switch to a real language. Melzzzzz <Melzzzzz@zzzzz.com> - 2018-04-03 07:13 +0000
                Re: A right alternative to IEEE-754's format Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-06 01:15 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-03-31 18:31 +0000
                Re: A right alternative to IEEE-754's format Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-01 08:57 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-01 17:49 +0000
                Re: A right alternative to IEEE-754's format Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-05 06:55 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-05 15:32 +0000
                Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-04-05 09:15 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-05 18:07 +0000
                Re: A right alternative to IEEE-754's format Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-06 04:19 -0700
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-06 13:42 +0000
                Re: A right alternative to IEEE-754's format Tim Rentsch <txr@alumni.caltech.edu> - 2018-05-24 09:30 -0700
        Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-02 23:07 -0500
          Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-03 07:40 +0200
            Re: A right alternative to IEEE-754's format Robert Wessel <robertwessel2@yahoo.com> - 2018-04-03 01:33 -0500
            Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-03 09:30 +0000
              Re: A right alternative to IEEE-754's format Terje Mathisen <terje.mathisen@tmsw.no> - 2018-04-03 12:03 +0200
                Re: A right alternative to IEEE-754's format nmm@wheeler.UUCP (Nick Maclaren) - 2018-04-03 10:42 +0000
    Re: A right alternative to IEEE-754's format jim.brakefield@ieee.org - 2018-03-30 12:58 -0700
  Re: A right alternative to IEEE-754's format EricP <ThatWouldBeTelling@thevillage.com> - 2018-03-29 13:25 -0400
    Re: A right alternative to IEEE-754's format MitchAlsup <MitchAlsup@aol.com> - 2018-03-29 16:32 -0700
      Re: A right alternative to IEEE-754's format BGB <cr88192@hotmail.com> - 2018-03-30 10:38 -0500

csiph-web