From: Thierry Reding <thierry.reding@avionic-design.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] ARM: prevent misaligned array inits
Date: Thu, 4 Oct 2012 14:02:06 +0200 [thread overview]
Message-ID: <20121004120206.GA28819@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <1349203564-27150-1-git-send-email-albert.u.boot@aribaud.net>
On Tue, Oct 02, 2012 at 08:46:04PM +0200, Albert ARIBAUD wrote:
> Under option -munaligned-access, gcc can perform local char
> or 16-bit array initializations using misaligned native
> accesses which will throw a data abort exception. Fix files
> where these array initializations were unneeded, and for
> files known to contain such initializations, enforce gcc
> option -mno-unaligned-access.
>
> Signed-off-by: Albert ARIBAUD <albert.u.boot@aribaud.net>
> ---
> Please test this patch with gcc 4.7 on boards which do data aborts
> or resets due to misaligned accesses and report result to me.
I've tested this on TEC, on top of Tom's tegra/next branch. Without the
patch, U-Boot hangs right after:
Loading Device Tree to 010f9000, end 010ff2d4 ... OK
With the patch applied the system boots to the login prompt, so:
Tested-by: Thierry Reding <thierry.reding@avionic-design.de>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20121004/c51258b7/attachment.pgp>
next prev parent reply other threads:[~2012-10-04 12:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 18:46 [U-Boot] [RFC] ARM: prevent misaligned array inits Albert ARIBAUD
2012-10-02 19:13 ` Joakim Tjernlund
2012-10-02 20:05 ` Albert ARIBAUD
2012-10-03 8:22 ` Joakim Tjernlund
2012-10-02 20:06 ` Stephen Warren
2012-10-02 21:20 ` Albert ARIBAUD
2012-10-02 21:42 ` Måns Rullgård
2012-10-03 7:29 ` Mark Marshall
2012-10-04 20:22 ` Albert ARIBAUD
2012-10-04 12:02 ` Thierry Reding [this message]
2012-10-04 19:10 ` Lucas Stach
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=20121004120206.GA28819@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=u-boot@lists.denx.de \
/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