From: rob@research.att.com
To: sam-fans@hawkwind.utcs.toronto.edu
Date: Sat, 18 Dec 1993 11:23:02 -0500 [thread overview]
Message-ID: <93Dec18.112410est.24030@hawkwind.utcs.toronto.edu> (raw)
sam's biggest engineering mistake is the passing
of pointers across the connection. it worsens the
problem by assuming a pointer fits in a 4-byte
word. it's easy to fix, though, if you're willing
to change the protocol to pass longer values for
longs. see the routines in mesg.c on both sides
with names like inlong() and so on. you can do
this in a way that will remain compatible among
all your local machines but you will become
incompatible with external machines.
i'm pretty sure this is the major problem with the
alpha. a variant of the problem occurred on the
cray long ago.
you also might need to change the structures Block and
List or else change the Block management not to use
the List routines.
-rob
reply other threads:[~1993-12-18 16:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=93Dec18.112410est.24030@hawkwind.utcs.toronto.edu \
--to=rob@research.att.com \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/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).