From: Glynn Clements <glynn@gclements.plus.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: newby.-interpreting C
Date: Thu, 30 Dec 2004 11:26:08 +0000 [thread overview]
Message-ID: <16851.58832.659413.893211@gargle.gargle.HOWL> (raw)
In-Reply-To: <20041220211709.GD2460@lug-owl.de>
Jan-Benedict Glaw wrote:
> General rule: if you don't *need* this for a good reason, or if you even
> don't know what it does, you don't need it, since it also introduces a
> performance penalty: CPUs tend to be fast at naturally aligned memory
> accesses, but quite slow on non-aligned accesses.
On most processor types, unaligned accesses will fail (either generate
an exception or return bogus data). The x86 family is the exception,
in that unaligned access merely reduces performance.
--
Glynn Clements <glynn@gclements.plus.com>
next prev parent reply other threads:[~2004-12-30 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 19:07 newby.-interpreting C soraberri
2004-12-20 19:38 ` Nir Dremer
2004-12-20 21:17 ` Jan-Benedict Glaw
2004-12-21 15:39 ` soraberri
2004-12-30 11:26 ` Glynn Clements [this message]
2004-12-30 11:40 ` Jan-Benedict Glaw
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=16851.58832.659413.893211@gargle.gargle.HOWL \
--to=glynn@gclements.plus.com \
--cc=linux-c-programming@vger.kernel.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).