From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 64-Bit programming model.
Date: Fri, 30 Sep 2005 20:19:18 -0700 [thread overview]
Message-ID: <9ab217670509302019h139a3d72j@mail.gmail.com> (raw)
In-Reply-To: <433DFDEC.9040301@lanl.gov>
2005/9/30, Ronald G Minnich <rminnich@lanl.gov>:
> Jim McKie wrote:
>
> > > ... are best served if there is a single choice widespread in the
> > > emerging 64-bit systems. This removes a source of subtle errors in
> > > porting to a 64-bit environment, and encourages more rapid
> > > exploitation of the technology options.
> >
> > I think that's backwards, you get sloppy in a monoculture.
>
> yeah, good point. We kept our alphas alive here for a long time for one
> reason: to make sure they kept us honest. For one thing, they would
> really complain about bad alighment. Pentiums are way too kind when you
> do something stupid like misalign a long or vlong.
>
> I was sad when it came time to turn them off.
>
> It's too easy to be stupid with just one architecture.
>
> ron
I just ran into an alignment bug yesterday doing credential passing
over Unix Domain Sockets on amd64. Admittedly, I should have read the
RFC (and more of the sunrpc code, which is where I stole mine from),
but it is really easy to run into alignment issues when you're only
using one architecture.
Though I don't necessarily agree with Jim if I understand him
correctly. I don't think that providing interfaces to make code
compilation on systems of different bit sizes promotes `a sloppy
monoculture.'
--Devon
next prev parent reply other threads:[~2005-10-01 3:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 11:31 Vester Thacker
2005-09-30 13:31 ` Charles Forsyth
2005-09-30 15:18 ` David Leimbach
2005-09-30 15:44 ` Karl Magdsick
2005-09-30 16:06 ` Charles Forsyth
[not found] ` <45544405a9a74e554cd5b645a672fb3e@terzarima.net>
2005-09-30 16:14 ` Karl Magdsick
2005-09-30 16:21 ` Russ Cox
2005-09-30 16:53 ` bakul+plan9
2005-09-30 16:14 ` Devon H. O'Dell
2005-09-30 18:07 ` Charles Forsyth
2005-09-30 19:01 ` erik quanstrom
2005-10-01 13:52 ` Charles Forsyth
2005-10-01 23:37 ` Ronald G Minnich
[not found] ` <f344c691fd8960b43b2c77f308ed2ea3@terzarima.net>
2005-09-30 21:27 ` Vester Thacker
2005-09-30 23:28 ` Jim McKie
2005-10-01 3:09 ` Ronald G Minnich
2005-10-01 3:19 ` Devon H. O'Dell [this message]
2005-10-01 4:46 ` erik quanstrom
2005-10-01 22:50 ` Jim McKie
2005-10-01 23:43 ` erik quanstrom
2005-10-01 13:50 ` Russ Cox
2005-10-01 18:28 ` Devon H. O'Dell
2005-10-01 14:28 ` Charles Forsyth
2005-10-01 14:20 ` Charles Forsyth
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=9ab217670509302019h139a3d72j@mail.gmail.com \
--to=devon.odell@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).