Re: HLASM Floating Point Field - Remainder?

On Jun 27, 9:33 pm, Barry Schwarz <schwa...@xxxxxxxxx> wrote:

In my admittedly limited experience (and I don't use VM at all), I
have never seen a product intended for the mainframe express time in
floating point.

IEEE double is well suited to hold time in seconds since 1900 (or
1970,
Unix-style) with microsecond resolution, and so is IBM Hex FP. With
at
least 53 bits of precision you can actually cover 300 years at that
resolution, and FP makes it easy to do interpolations on various
scales,
as is needed on non-S/370 machines (i.e. machines without STCK). (The
old POWER machines, up to PPC601 included, did have a real-time
clock.)

So it's true that FP times are perhaps less useful on S/370's
children.

Michel.

.

Relevant Pages

  • Re: floating point glitch
    ... it's inherent in how floating point conversions work. ... on all IEEE 754 machines. ...
    (comp.lang.python)
  • Re: Same input, different output on different computers!
    ... > You can see that I have not been keeping up with current processor design. ... > in both integer and floating point computation than a 16-bit machine. ... > floating point representation than did the smaller word size machines. ... difference in architecture, regardless of what the finer details may be. ...
    (comp.os.linux.misc)
  • Re: converting float to ascii w/o printf
    ... Currently I am using sprintfto format this output into ... the rule here is never use floating point at all if it can be avoided. ... If you know what the range of values and required accuracy is, scaled integer arithmetic will be faster and more efficient, especially if you can arrange the data to allow shifts, rather than multiply and divide. ... Floating point on small machines is slow, inefficient, adds complexity and rounding errors everywhere it's used and you can usually get better control and predictable accuracy using other methods. ...
    (comp.arch.embedded)
  • Re: converting float to ascii w/o printf
    ... When you are using a micro of 16k ROM or more, the floating point overhead doesn't really matter. ... it does matter on the machines with less then 8k. ... sledgehammer and if I were your project manager, I would encourage you to find a more creative solution :-). ...
    (comp.arch.embedded)
  • Re: 8 bit microcontroller market
    ... 2k are way too much for simple state machines... ... multiplications on an 8bitter can take up to 1k (depending on the ... Implement one by hand might take a few hundred LOC ... Implementing floating point multiplication is trivial on any 8 ...
    (comp.arch.embedded)