qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2 26/43] tests/tcg/arm: fix up test-arm-iwmmxt


From: Richard Henderson
Subject: Re: [Qemu-devel] [PATCH v2 26/43] tests/tcg/arm: fix up test-arm-iwmmxt test
Date: Fri, 20 Apr 2018 11:16:06 -1000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0

On 04/19/2018 10:18 PM, Alex Bennée wrote:
> 
> Richard Henderson <address@hidden> writes:
> 
>> On 04/19/2018 03:58 AM, Alex Bennée wrote:
>>> +test-arm-iwmmxt: CFLAGS+=-marm -march=iwmmxt -mabi=aapcs
>>> +test-arm-iwmmxt: test-arm-iwmmxt.S
>>
>> This appears to be insufficient.
>> If I begin with armv7l-linux-gnueabihf-gcc, then I get
>>
>>   CROSS-BUILD arm guest-tests with armv7l-linux-gnueabihf-gcc
>> cc1: error: iWMMXt and NEON are incompatible
> 
> Was this with the docker fall-back?

No, apparently my docker install is "sudo", and so is unused.

> It worked with my local:
> 
> 07:37:25 address@hidden:~/l/q/qemu.git] softmmu/demacro-cputlb-rfc + 
> arm-linux-gnueabihf-gcc --version
> arm-linux-gnueabihf-gcc (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
> Copyright (C) 2015 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

My arm cross is self-built, with configure options mirroring a native fedora
arm gcc:

Target: armv7l-linux-gnueabihf
Configured with: ../comb/configure --with-sysroot
--prefix=/home/rth/work/gcc/run-cross --enable-languages=c,c++,lto
--target=armv7l-linux-gnueabihf --with-system-zlib --enable-__cxa_atexit
--enable-gnu-unique-object --enable-linker-build-id
--with-linker-hash-style=gnu --enable-initfini-array --with-cpu=cortex-a15
--with-float=hard --with-fpu=neon-vfpv4 --with-abi=aapcs-linux
Thread model: posix
gcc version 7.0.0 20161220 (experimental) [master revision
f7619de:63fb493:269ead384b0fdd3dd4f7030be44e54e5a19c4e8c] (GCC)


r~



reply via email to

[Prev in Thread] Current Thread [Next in Thread]