From: Lars Brinkhoff <lars.spam@nocrew.org>
To: Richard.Earnshaw@arm.com
Cc: Andrew Cagney <ac131313@cygnus.com>,
twall@oculustech.com, gdb@sources.redhat.com
Subject: Re: packing/unpacking 4-octet longs
Date: Wed, 05 Dec 2001 10:11:00 -0000 [thread overview]
Message-ID: <854rn5fsix.fsf@junk.nocrew.org> (raw)
In-Reply-To: <200112051645.QAA06737@cam-mail2.cambridge.arm.com>
Richard Earnshaw <rearnsha@arm.com> writes:
> > > 0xaabbccdd is stored as 0xbb 0xaa 0xdd 0xcc.
> > I'm pretty sure that there is another very old wacko architecture
> > that did something similar to this, I'm trying to remember which.
> > pdp11?
> PDP11, I think.
Yes. That ordering is sometimes called "PDP-endian" (incorrectly
in my opinion, since there are many different PDP architectures).
> It's a bit before my time, but IIRC it's because earlier PDPS (8?
> 9?) were 16-bit machines, so there wasn't really any concept of
> word-ordering beyond that: 16-bit words were little-endian, but the
> most significant word was always at the lowest address (or the other
> way around).
Not quite. All earlier PDP architectures were word-adressable. PDP-1
and PDP-4/7/9 had 18-bit words, PDP-5/8 had 12-bit words, and PDP-6/10
had 36-bit words. I don't know if the other machines had multiple-word
operands, but the PDP-6/10 stored the most significant word first.
PDP-11 was the first 16-bit machine, and the first byte-addressable.
--
Lars Brinkhoff http://lars.nocrew.org/ Linux, GCC, PDP-10
Brinkhoff Consulting http://www.brinkhoff.se/ programming
next prev parent reply other threads:[~2001-12-05 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 5:44 Timothy Wall
2001-12-05 8:26 ` Andrew Cagney
2001-12-05 8:46 ` Richard Earnshaw
2001-12-05 10:11 ` Lars Brinkhoff [this message]
2001-12-05 10:42 ` Andrew Cagney
2001-12-06 2:03 ` Richard Earnshaw
2001-12-05 9:31 ` Timothy Wall
2001-12-05 10:03 ` Andrew Cagney
2001-12-05 10:20 ` Timothy Wall
2001-12-05 10:49 ` Andrew Cagney
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=854rn5fsix.fsf@junk.nocrew.org \
--to=lars.spam@nocrew.org \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=twall@oculustech.com \
/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