From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] structure allocation.
Date: Wed, 8 Mar 2006 15:10:14 +1100 [thread overview]
Message-ID: <775b8d190603072010v282cd1afl8677895d3407d914@mail.gmail.com> (raw)
In-Reply-To: <225d545abee6717eec8ffe272836f235@collyer.net>
i still like hjdicks it is obscure enough that no-one would think it's
a feature (or guess it). it was required because we had a large
slab of 3rd-party code that assumed it could read packets off the
wire (assuming correct endian) and do no marshaling.
#pragam pack
looks like a feature.
i was there when it happened (after a nice italian meal).
ken asked "Do i really have to do this?"
P: Yes, there's buckets of code that rely on it.
K: *some expression of disbelief*
P: well hj are just dicks
done deal
it also turned out to be important for inferno on machines with
greater than 32 bit alignment requirements. the 64 bit mips
is an example. took but a recompile with hjdicks in the right
place (it takes an optional alignment parameter). same with
the ps2 which has 128 bit issues.
thanks for telling me that it has been changed.
brucee
On 3/8/06, geoff@collyer.net <geoff@collyer.net> wrote:
> I was implicitly referring to C compilers. Heck, Pascal had packed
> data in the early 1970s, possibly even the late 1960s.
next prev parent reply other threads:[~2006-03-08 4:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 2:30 erik quanstrom
2006-03-07 2:37 ` geoff
2006-03-07 3:00 ` erik quanstrom
2006-03-07 3:11 ` Russ Cox
2006-03-07 4:13 ` geoff
2006-03-07 15:41 ` Ronald G Minnich
2006-03-07 15:53 ` C H Forsyth
2006-03-08 0:06 ` erik quanstrom
2006-03-08 2:21 ` Ronald G Minnich
2006-03-08 2:50 ` geoff
2006-03-08 4:10 ` Bruce Ellis [this message]
2006-03-08 4:37 ` Russ Cox
2006-03-08 4:55 ` Bruce Ellis
2006-03-08 5:03 ` Russ Cox
2006-03-08 5:05 ` Bruce Ellis
2006-03-08 5:09 ` Russ Cox
2006-03-08 5:12 ` Bruce Ellis
2006-03-08 12:11 ` Brantley Coile
2006-03-07 17:47 ` Bakul Shah
2006-03-07 9:23 ` Charles Forsyth
2006-03-07 11:54 ` erik quanstrom
2006-03-07 13:55 ` jmk
[not found] ` <000501c641de$afc905d0$14aaa8c0@utelsystems.local>
2006-03-07 14:21 ` "Nils O. Selåsdal"
2006-03-07 14:30 ` uriel
2006-03-07 14:43 ` Russ Cox
2006-03-07 14:48 ` C H Forsyth
2006-03-08 0:28 ` erik quanstrom
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=775b8d190603072010v282cd1afl8677895d3407d914@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=9fans@cse.psu.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).