All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: newby.-interpreting C
Date: Thu, 30 Dec 2004 12:40:11 +0100	[thread overview]
Message-ID: <20041230114011.GA2460@lug-owl.de> (raw)
In-Reply-To: <16851.58832.659413.893211@gargle.gargle.HOWL>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

On Thu, 2004-12-30 11:26:08 +0000, Glynn Clements <glynn@gclements.plus.com>
wrote in message <16851.58832.659413.893211@gargle.gargle.HOWL>:
> 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.

As is the VAX :)

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-12-30 11:40 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
2004-12-30 11:40     ` Jan-Benedict Glaw [this message]

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=20041230114011.GA2460@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.