public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
	Christoph Hellwig <hch@lst.de>,
	linux-kernel@vger.kernel.org
Subject: Re: get/put unaligned helpers
Date: Thu, 12 Feb 2009 14:55:38 +0200	[thread overview]
Message-ID: <49941C4A.4050401@panasas.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0902121241570.7279@ftp.linux-mips.org>

Maciej W. Rozycki wrote:
> On Thu, 12 Feb 2009, Boaz Harrosh wrote:
> 
>> Speaking of which. When all this is done do you intend to also export
>> the unaligned.h headers to user-mode just like the aligned Endian helpers?
>>
>> That could help in a couple of projects, so you have my vote.
> 
>  Why would you need that?  GCC provides a portable, platform-independent 
> way.  It has had it for ten years at the very least.
> 

Do you mean the __built_in_swabXX() and all these guys.

I was under the impression they need to be aligned because otherwise that means
something is done wrong. Because the aligned version on lots of CPUs is one instruction
where unaligned access is better, or must, be emulated (byte accessed).

Assembly wise the two accesses are different and sometimes the compiler has no way to
know, where the programmer can know for sure.

But I like to be educated any day, please explain what to use when.

>   Maciej

Thanks
Boaz

  reply	other threads:[~2009-02-12 12:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 14:35 get/put unaligned helpers Christoph Hellwig
2009-02-11 15:48 ` Harvey Harrison
2009-02-12  8:50   ` Boaz Harrosh
2009-02-12 12:44     ` Maciej W. Rozycki
2009-02-12 12:55       ` Boaz Harrosh [this message]
2009-02-12 14:39         ` Maciej W. Rozycki
2009-02-12 18:43     ` Stefan Richter
2009-02-12 20:20     ` Harvey Harrison
2009-02-13 22:07 ` Harvey Harrison

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=49941C4A.4050401@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=harvey.harrison@gmail.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.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