The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Dan Cross <crossd@gmail.com>
Cc: Paul Ruizendaal <pnr@planet.nl>, "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: CRC calculation in the 1980s
Date: Tue, 19 Sep 2023 12:22:33 -0400	[thread overview]
Message-ID: <CABH=_VTSQ3HOyx=RoNzhxaha_6H-kZCKz=ijPfK0tFBQpHRScA@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W7iObAp0sitA0-uYOD9uJGLAncJ2ukhr+8Er6_POCPxhw@mail.gmail.com>

On 9/19/23, Dan Cross <crossd@gmail.com> wrote:
(regarding the CRC instruction on VAX)
>
> I thought that was a general polynomial root finder instruction that
> used Horner's Method?  Obviously it could be used in CRC calculations,
> but I remember it being more general. I also remember reading about it
> in the VAX architecture manual and thinking, "wow,
> that's...something."

VAX had both a CRC instruction and a polynomial instruction.  CRC
operated on byte strings and did fixed-point calculation.  The
polynomial instructions (POLYF and POLYD) operated on single-precision
(F) or double-precision (D) data.  Unfortunately the algorithm used by
POLYF and POLYD wasn't very accurate--there were other algorithms that
did a better job preserving precision.  Anyone doing serious
calculations in floating point avoided POLYF and POLYD.  These were
two more of the instructions that were dropped from the microVAX
architecture and emulated by the OS.

-Paul W.

  reply	other threads:[~2023-09-19 16:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 23:02 [TUHS] " Paul Ruizendaal
2023-09-18 23:34 ` [TUHS] " Robert Brockway
2023-09-19  0:02 ` segaloco via TUHS
2023-09-19 15:34 ` Paul Winalski
2023-09-19 15:50   ` Dan Cross
2023-09-19 16:22     ` Paul Winalski [this message]
2023-09-19 11:42 Noel Chiappa
2023-09-19 12:54 ` Lars Brinkhoff
2023-09-19 16:00 ` Paul Ruizendaal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABH=_VTSQ3HOyx=RoNzhxaha_6H-kZCKz=ijPfK0tFBQpHRScA@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=crossd@gmail.com \
    --cc=pnr@planet.nl \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).