All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <poky@yoctoproject.org>
Subject: Re: Bad ARM code with GCC 4.7.1
Date: Thu, 10 May 2012 11:49:09 -0500	[thread overview]
Message-ID: <4FABF185.5060205@windriver.com> (raw)
In-Reply-To: <CAMKF1sqUt4QrNh9ff0ZERDCttdUSams-wUcOR4e4hDs+7z-Txw@mail.gmail.com>

On 5/10/12 11:30 AM, Khem Raj wrote:
> On Thu, May 10, 2012 at 9:17 AM, Gary Thomas<gary@mlbassoc.com>  wrote:
>>
>> My board is DM3730, much like a BeagleBoard
>>   ARM architecture: armv7a
>>   Linux kernel 3.0
>
> hmmm that should be able to handle alignment faults in hardware

As far as I know, most armv7a handle alignment in the kernel, but there are 
newer crops of CPUs coming out that will no longer have alignment handlers as a 
"speed optimization".. (I think they're a bit nuts myself, but anyway.)

But if the code in question is inside the kernel, then the alignment faults 
won't work -- or will they?  (Certainly won't from within the alignment handlers 
of course...)

--Mark

>>
>>
>>>
>>> gcc generate unaligned accesses by default
>>>
>>> Does adding -mno-unaligned-access to cflags help ?
>>
>>
>> I'll check.
>
> Its not entirely clear whats going on so post the complete function disassembly
> so further context can be seen as well.
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky



  reply	other threads:[~2012-05-10 16:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 14:28 Bad ARM code with GCC 4.7.1 Gary Thomas
2012-05-10 15:46 ` Khem Raj
2012-05-10 16:17   ` Gary Thomas
2012-05-10 16:30     ` Khem Raj
2012-05-10 16:49       ` Mark Hatle [this message]
2012-05-10 17:00         ` Khem Raj
2012-05-10 17:08       ` Gary Thomas
2012-05-10 20:06         ` Martin Jansa

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=4FABF185.5060205@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=poky@yoctoproject.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.