There is an ongoing activity to merge the feature-ipc branch to master.
Tamas
-----Original Message----- From: DeMars, Alan ademars@ti.com Sent: 01 February 2019 23:16 To: Tamas Ban Tamas.Ban@arm.com Cc: nd nd@arm.com Subject: RE: Required GCC tools for reference implementation
Excellent!
Will this change be merged into the feature-ipc branch soon?
Alan
-----Original Message----- From: TF-M [mailto:tf-m-bounces@lists.trustedfirmware.org] On Behalf Of Tamas Ban via TF-M Sent: Friday, February 01, 2019 2:01 PM To: tf-m@lists.trustedfirmware.org Cc: nd Subject: [EXTERNAL] Re: [Tf-m] Required GCC tools for reference implementation
Hi Alan,
Since this change the GNUARM v7.3 also supported: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/421/
Tamas
-----Original Message----- From: TF-M tf-m-bounces@lists.trustedfirmware.org On Behalf Of DeMars, Alan via TF-M Sent: 01 February 2019 20:59 To: tf-m@lists.trustedfirmware.org Subject: [Tf-m] Required GCC tools for reference implementation
Is there a compelling reason that the reference implementation of the PSA requires the use of the gcc-arm-none-eabi-6-2017-q1-update gnu tools?
The linker in these tools generates a non-standard s_veneers.o file that cannot be consumed by some CLANG linkers. It should be a relocatable object file with absolute symbols, but instead it's static executable file.
If I use a newer GCC linker (ie: gcc-arm-none-eabi-7-2017-q4-major) for the final link of the secure image, the generated s_veneers.o file is of the correct type.
Alan DeMars