Arm Multilib Question
sebastian.huber at embedded-brains.de
Fri Oct 11 13:55:27 UTC 2019
On 11/10/2019 15:46, Joel Sherrill wrote:
> I'm trying to find the right multilib for the ARM Deos BSP. They compile
> their native
> ARINC 653 applications with these:
> arm-eabi-gcc -MP -MMD -nostdinc -gdwarf-2 -fno-exceptions
> -mabi=aapcs-linux -march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16
> -mthumb -mthumb-interwork -O0 -fno-threadsafe-statics
> -fno-use-cxa-atexit -fno-rtti
I am not sure if -mabi=aapcs-linux is a nop or dangerous. Why do they
use this option.
The -mthumb-interwork is superfluous.
The -fno-exceptions and -fno-rtti make more sense if you build libstdc++
also with it.
> Neither arm-eabi nor arm-rtems will link this. arm-eabi picks a variant
> for crtn0.o but doesn't seem to find a libm even though one is there in
> the same multilib path and ends up with the math function undefined.
> arm-rtems is just missing the multlib info as best I can tell.
> error: /tmp/cc8zsaRc.o uses VFP register arguments, armtest does not
> failed to merge target specific data of file /tmp/cc8zsaRc.o
> I have attached my simple example. Do we have a multlib that should be
> matching this or does one need to be added?
> Assistance definitely appreciated.
GCC 8, 9 and 10 are not supported by the ARM BSPs right now.
You can try this with GCC 10:
-mthumb -march=armv7-a+simd -mfloat-abi=hard
Why do they use -mfpu=vfpv3-d16? This seems to be quite a non-standard
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the devel