• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 3734 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

project.out uses VFP , compiler library (file.o) does not even though hard is specified

cobsonchael
Mastermind 7930 points

Other Parts Discussed in Thread: SYSBIOS, AM3352

so i thought i had this fixed before but since i upgraded CCS to 6.2 and SYSBIOS to 6.46.1.38 (rebuilt to add fatfs support for another project) i am getting the following errors:

Description Resource Path Location Type
error: Model840i 3352.out uses VFP register arguments, c:/ti/ccsv6/tools/compiler/gcc-arm-none-eabi-4_9-2015q3/bin/../lib/gcc/arm-none-eabi/4.9.3\libgcc.a(_divdi3.o) does not Model840i 3352 C/C++ Problem
error: Model840i 3352.out uses VFP register arguments, c:/ti/ccsv6/tools/compiler/gcc-arm-none-eabi-4_9-2015q3/bin/../lib/gcc/arm-none-eabi/4.9.3\libgcc.a(_udivdi3.o) does not Model840i 3352 C/C++ Problem
error: Model840i 3352.out uses VFP register arguments, c:/ti/ccsv6/tools/compiler/gcc-arm-none-eabi-4_9-2015q3/bin/../lib/gcc/arm-none-eabi/4.9.3\libgcc.a(bpabi.o) does not Model840i 3352 C/C++ Problem
failed to merge target specific data of file c:/ti/ccsv6/tools/compiler/gcc-arm-none-eabi-4_9-2015q3/bin/../lib/gcc/arm-none-eabi/4.9.3\libgcc.a(_divdi3.o) Model840i 3352 C/C++ Problem
failed to merge target specific data of file c:/ti/ccsv6/tools/compiler/gcc-arm-none-eabi-4_9-2015q3/bin/../lib/gcc/arm-none-eabi/4.9.3\libgcc.a(_udivdi3.o) Model840i 3352 C/C++ Problem
failed to merge target specific data of file c:/ti/ccsv6/tools/compiler/gcc-arm-none-eabi-4_9-2015q3/bin/../lib/gcc/arm-none-eabi/4.9.3\libgcc.a(bpabi.o) Model840i 3352 C/C++ Problem

i am using GNU 4.9.3 (Linaro) to compile for an AM3352.  

i had this problem when first creating the project and i thought i fixed it by adding "hard" to the -mfloat-abi field.

so i have no idea as to where to look for this issue.  it just says my out file has this which would assume my code BUT if hard is specified in my build options for my project i just don't see what could create this issue. our code doesn't even do any floating point math. where do i even start looking for this? i would think if a library was added that caused this it would specify the library itself, right?  my -mfpu is blank, does that need to be loaded to something?