libyuv r481 in Chromium M27 does not cross compile for arm

[GoogleCodeExporter]

From discuss
There are errors when trying to crosscompile libyuv integration of chromium. 
Can someone help me find the problem. 
The compiler output is the following:
{standard input}: Assembler messages:
{standard input}:1373: Error: ']' expected -- `vld2.u8 {q0,q1},[r0:128]!'
{standard input}:1375: Error: ']' expected -- `vst1.u8 {q0},[r1:128]!'
{standard input}:1376: Error: ']' expected -- `vst1.u8 {q1},[r2:128]!'
{standard input}:1423: Error: ']' expected -- `vld1.u8 {q0},[r0:128]!'
{standard input}:1424: Error: ']' expected -- `vld1.u8 {q1},[r1:128]!'
{standard input}:1426: Error: ']' expected -- `vst2.u8 {q0,q1},[r2:128]!'
ninja: build stopped: subcommand failed.

The problematic code is in row_neon.cc (SplitUV_NEON, MergeUV_NEON). Actually 
it's the :128 which bothers the compiler, removing it or changing the : to a , 
results in a compileable chromium but it segfaults on startup. So my guess, my 
corrections are wrong.

Original issue reported on code.google.com by fbarch...@google.com on 10 Jun 2013 at 3:23

[GoogleCodeExporter]

How about vld2.u8 {q0,q1},[r0, :128]!

Original comment by kma@google.com on 10 Jun 2013 at 4:31

[GoogleCodeExporter]

This affects
arm-none-linux-gnueabi-gcc (GCC) 4.5.4 20111126 (prerelease)
r721 simplifies the vld1.u8 to vld1.8

Original comment by fbarch...@google.com on 12 Jun 2013 at 3:03

[GoogleCodeExporter]

Closing bug.  Feel free to re-file if there is more information.
Using new version (r729 is current version) would fix issue.
Appears old version of gcc did not like alignment notation.  Using newer 
version of gcc may fix issue.

Original comment by fbarch...@google.com on 17 Jun 2013 at 5:35

• Changed state: Fixed