GNU Arm Embedded Toolchain

--specs files guide

Asked by Viktor

Hi Arm Team,

Is there a guide for which specs file to use for the various multi-lib options?

For example,
arm-none-eabi-gcc -mthumb -march=armv7 -mfloat-abi=hard -mfpu=vfpv3-d16 -specs=rdimon.specs -o hello hello.c
does not work, but
arm-none-eabi-gcc -mthumb -march=armv7 -mfloat-abi=hard -mfpu=vfpv3-d16 -specs=pid.specs -o hello hello.c
is ok.

I can't seem to find any documentation in the toolchain directory or online related to this.

Thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
GNU Arm Embedded Toolchain Edit question
Assignee:
No assignee Edit question
Solved by:
Terry Guo
Solved:
Last query:
Last reply:
Revision history for this message
Best Terry Guo (terry.guo) said : 		#1

Hi Victor,

I guess the arm-none-eabi-gcc you are talking isn't the one released in this website. Because I just tried and no such issue for gcc arm embedded tool chain. Which multilib will be chose really depends on the target options like -mthumb or -march=armv7, and doesn't depend on the spec files. The spec files only decide things like whether your are going to use c library or which version you are going to use, for example generic newlib or nano-newlib in our case.

There is no dedicated explanation to which spec files you should choose. But you can find some descriptions in our readme.txt.

Revision history for this message
Viktor (vchong) said : 		#2

Hi Terry,

I was using 4.7 2013q3 release which didn't work for above multilib option with -specs=rdimon.specs.
I tried 4.8 2014q2 version and it's ok.

Thanks for the info and quick reply!