> There is a means if someone wants to update gcc-common-1.cfg to allow user
> macro maps.
[...]
Thanks, Chris. I'll investigate this.
Kind regards
Ingolf
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users
Hi Sebastian.
> Why would you use
> this instead of -mfloat-abi=hard? For a statically linked executable
> this makes little sense.
My goal is to link with a 3rd party object file which had been compiled with
-mfloat-abi=softfp and which cannot be recompiled. In fact, there are also
other
On 5/4/2023 4:11 am, Sebastian Huber wrote:
> If you really need such a multilib, then you can patch
> gcc/config/arm/t-rtems. I
> don't know if you can add custom patches to the RTEMS Source Builder.
There is a means if someone wants to update gcc-common-1.cfg to allow user macro
maps.
1. User
Hello Ingolf,
the -mfloat-abi=softfp instructs the compiler to emit floating-point
instructions if other machine options specify a FPU. Why would you use
this instead of -mfloat-abi=hard? For a statically linked executable
this makes little sense. You still have to take care of the FPU
Hi,
we are currently using the RTEMS source builder to build the toolchain, RTEMS
and a few BSPs for ARM (32bit) targets. Apparently, RTEMS generally uses
-mfloat-abi=hard for all arm32 targets. Can this easily be changed to compile
with -mfloat-abi=softfp instead? Or extend the multilib build
