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

From	Ivan Godard <ivan@millcomputing.com>
Newsgroups	comp.arch
Subject	Re: A right alternative to IEEE-754's format
Date	2018-04-22 10:52 -0700
Organization	A noiseless patient Spider
Message-ID	<pbii5a$4o7$1@dont-email.me> (permalink)
References	(17 earlier) <e66232e2-e537-4bd9-96d9-07ac0f756594@googlegroups.com> <adfd6fbc-1498-45e2-b88c-a2b9a87c9ad8@googlegroups.com> <5s4CC.24659$vY2.8020@fx05.iad> <f9128285-d1e9-417a-8768-2e7c2309a80c@googlegroups.com> <48faf4a6-c02e-4508-a405-41d0872583ad@googlegroups.com>

Show all headers | View raw

On 4/19/2018 3:52 PM, matthey7@gmail.com wrote:
> On Thursday, April 19, 2018 at 2:48:54 PM UTC-5, Quadibloc wrote:
>> On Thursday, April 19, 2018 at 11:36:03 AM UTC-6, EricP wrote:
>>
>>> If so, that is unfortunate as there is no reason to assume
>>> PC relative data is read only or execute only.
>>
>> Well, "PC relative" means *relative to the program counter*. Since pages are
>> independently put in memory wherever it happens to be room, and the program
>> counter always points to executable code, how can a PC relative address point to anything but something that's in a page of executable code?
> 
> Text and read only data has commonly been placed in code/text sections by compilers and accessed using PC relative loads. This is excellent for code density although it blurs a strict separation of code and data also. Some operating systems have moved the text and read only data to a read only no execute data section to improve (probably minimally) security.
> 
> I know of 4 ways it is possible to use PC relative addressing to access data in other sections.
> 
> 1) Some operating systems support specifying fixed (often virtual) section addresses which allow PC relative displacements to be calculated. The disadvantages are conflicts of fixed addresses and decreased security.
> 
> 2) Use an ABI code model to limit the 64 bit address range to that supported by PC relative addressing in the hardware. It practically requires an MMU for virtual address translation and limits the usable address space. It requires selecting the correct code model at compile time when it is not obvious what code model is needed or efficient. PIC code is not really position independent because it can't go anywhere in the 64 bit virtual address space. Large PIC code becomes very inefficient. There may be a minor security decrease due to the limited address space. It is simple and effective just feels like an artificial limitation which should not exist for a 64 bit CPU.
> 
> 2) It is possible for a relocatable scatter loader to calculate PC relative displacements and fix them up like absolute addresses before execution using relocation tables in the executable. This is a royal pain without cross-module/linker optimizations and a (d64,PC) addressing mode with 64 bit addressing. Also, there needs to be some way to improve spatial locality of the sections for there to be much of an advantage over using absolute addressing with relocation (absolute addressing is simple in hardware but gives poor code density). If I understand EricP, his "memory regions" are an attempt to improve spacial locality so (d32,PC) could be commonly used to save 4 bytes per access over absolute addressing.
> 
> 3) The code/text, data and BSS sections can be merged and placed in contiguous memory with padding to MMU page boundaries (if an MMU is present) so the different sections can have different MMU protections. This allows accessing all sections with PC relative addressing and requires no relocation at run time. It gives the best code density as spacial locality is consistently nearly optimal while allowing for full relocatability anywhere in the 64 bit address space. It does require cross-module optimization to merge sections in other units but then the PC relative displacements can be easily calculated (before the linker). The executable would require a larger chunk of memory but would fragment memory less than scatter loading sections. Maybe there are other downsides but I have not heard them even though 2 people do not like this option without giving their logic.
> 
> I would appreciate any corrections by the experts here. ;)
> 

4) Remove PC-relative addressing for load and store (permitting only 
branch/call, and PC-rel target address must be in an executable region), 
and add a base register that points to a RO data region. And one that 
points to the stack frame, and one that points to global static, and one 
that points to thread-local. With offsets of 0/1/2/4 bytes. Four bits to 
specify mode (2 for base, two for offset). Mill.

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

Thread

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

csiph-web