From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= <mans@mansr.com>
Date: Thu, 13 Jul 2017 13:34:52 +0100
Subject: [U-Boot] Data Abort with gcc 7.1
In-Reply-To: <20170713123209.qmeuv7jej2cpvvrk@flea> (Maxime Ripard's message
 of "Thu, 13 Jul 2017 14:32:09 +0200")
References: <20170711165455.xtpi4qdncftbuglt@flea>
 <yw1xfue1tbd2.fsf@mansr.com> <20170713065200.49f2f89b@i7>
 <yw1xbmootznh.fsf@mansr.com>
 <CALeDE9PSkG2iAitVtUtXNOwTPjHo0qoaWYi=Bk8+Zf+ZjghK6w@mail.gmail.com>
 <20170713123209.qmeuv7jej2cpvvrk@flea>
Message-ID: <yw1xy3rssefn.fsf@mansr.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
To: u-boot@lists.denx.de

Maxime Ripard <maxime.ripard@free-electrons.com> writes:

> On Thu, Jul 13, 2017 at 11:20:34AM +0100, Peter Robinson wrote:
>> >>> What hardware did this happen on?  If it was on ARMv5, adding the packed
>> >>> attribute is probably the correct fix.  If it was ARMv6 or later,
>> >>> something else is broken as well.
>> >>
>> >> It does not matter if this was ARMv6+ hardware or not. The current
>> >> U-Boot code is wrong and we need to fix it.
>> >
>> > The question is how many errors there are.  That's why I asked about the
>> > hardware.
>> 
>> I've seen it on a number of devices but they were all ARMv7+
>> (AllWinner, Rockchips etc)
>
> It was on an Allwinner SoCs with a Cortex-A7 CPU, so armv7. However,
> as far as I know, the unaligned accesses are disable in u-boot.

Yes, so it seems, although I can't fathom why.

-- 
Måns Rullgård