From: david@kdbarto.org (David Barto)
Subject: [TUHS] So I'm looking through some old SVR3.1 source
Date: Sun, 31 May 2015 11:14:17 -0700 [thread overview]
Message-ID: <BA8E7D4A-23F4-41AC-8B5E-EC653E9D0830@kdbarto.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
Just cuz of this list and recent comments about SVRx and I see this comment in ftrap.s
fpreent: # this is the point we return to
# when we are executing the n+1th
# floating point instruction in a
# contiguous sequence of floating
# point instructions (floating
# pointlessly forever?)
Makes me wonder how many other humorous comments are buried in the code.
David
Oh, if no one out there has a SVR3.1 distribution (apparently for the 3b2), I’ve got one to send out….
next reply other threads:[~2015-05-31 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 18:14 David Barto [this message]
2015-05-31 18:29 ` Cory Smelosky
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=BA8E7D4A-23F4-41AC-8B5E-EC653E9D0830@kdbarto.org \
--to=david@kdbarto.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).