mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Daniel Drake <dsd@gentoo.org>
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
	kune@deine-taler.de, johannes@sipsolutions.net
Subject: Re: [RFC] Documentation about unaligned memory access
Date: Sat, 24 Nov 2007 14:34:41 +0100	[thread overview]
Message-ID: <20071124143441.41657307@poseidon.drzeus.cx> (raw)
In-Reply-To: <20071123001554.12F8B9D4A1F@zog.reactivated.net>

On Fri, 23 Nov 2007 00:15:53 +0000 (GMT)
Daniel Drake <dsd@gentoo.org> wrote:

> Being spoilt by the luxuries of i386/x86_64 I've never really had a good
> grasp on unaligned memory access problems on other architectures and decided
> it was time to figure it out. As a result I've written this documentation
> which I plan to submit for inclusion as
> Documentation/unaligned_memory_access.txt
> 
> Before I do so, any comments on the following?
> 

A very nice, and much needed document. I think you should include one thing though:

memcpy() is _only_ safe when one of the pointers is char* or void*. If it is anything more complex than that, gcc will assume alignment and optimise based on that. E.g. memcpy() of two long:s generates the same assembly as doing an assignment.

(Technically it is no different for char* and void*, but since they have byte alignment, gcc can't really do anything creative.)

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

  parent reply	other threads:[~2007-11-24 14:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23  0:15 Daniel Drake
2007-11-23  0:27 ` Avuton Olrich
2007-11-23  1:29 ` Alan Cox
2007-11-23  3:04   ` Kyle Moffett
2007-11-23  6:18   ` dean gaudet
2007-11-23  9:46     ` Arne Georg Gleditsch
2007-11-26 14:50       ` dean gaudet
2007-11-23  1:29 ` David Miller
2007-11-23 10:06 ` Jan Engelhardt
2007-11-23 11:43 ` Heikki Orsila
2007-11-25 11:16   ` Geert Uytterhoeven
2007-11-25 11:24     ` Heikki Orsila
2007-11-26  0:48       ` Alan Cox
2007-11-26 17:12   ` Ben Dooks
2007-11-27  7:51   ` Kumar Gala
2007-11-23 22:02 ` Vadim Lobanov
2007-11-23 22:52 ` Dmitri Vorobiev
2007-11-24 13:34 ` Pierre Ossman [this message]
2007-11-24 15:50   ` Luciano Rocha
2007-11-24 16:19     ` Pierre Ossman
2007-11-24 17:22       ` Luciano Rocha
2007-11-24 17:35         ` Pierre Ossman
2007-11-24 18:28           ` Luciano Rocha
2007-11-24 17:53         ` Haavard Skinnemoen
2007-11-25  8:27 ` Denys Vlasenko
2007-11-25 14:13 ` Olaf Titz
2007-11-26  9:14 ` DM
2007-11-26 14:47 ` Johannes Berg
2007-11-27  0:40   ` Arnaldo Carvalho de Melo
2007-11-26 14:51 ` Johannes Berg
2007-11-30  8:18 ` Jörn Engel
     [not found] <fa.U+CIv4JClOmn6KppLkEOSk7RW0Y@ifi.uio.no>
2007-11-23  1:24 ` Robert Hancock
2007-11-23  2:07   ` Andi Kleen

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=20071124143441.41657307@poseidon.drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=davem@davemloft.net \
    --cc=dsd@gentoo.org \
    --cc=johannes@sipsolutions.net \
    --cc=kune@deine-taler.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®