• State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 21 subscribers
  • Views 2542 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Development Studio 2022.2 no longer recognizes options +nofp, +nocrypto etc.

Oscar Huang

I have a program, which can be compiled and linked with ARMCompiler6.18, but it failed to link with ARMCompiler6.19, which comes with Development Studio 2022.2. The error is:

Error: L6415E: Could not find a unique set of libraries compatible with this image.  Suggest using the --cpu option to select a specific library.

I used this option in my makefile: -mcpu=cortex-r82+nofp+nocrypto+nosimd

If I change the  --mcpu option value to --mcpu=cortex-r82 by removing +nofp+nocrypto+nosimd, the program can compile and link. It looks like the linker no longer understands the feature options +nofp, +nocrypto etc.

Parents
  • 0 in reply to Ronan Synnott

    Ronan,

    Thanks for your answer. According to ka004846, I should be able to use +nofp option to ensure no floating point is used. But actually 6.19 reports linking error if I use +nofp option. What do you think the behavior of 6.19 is correct? 

    We are working with a Cortex-R82 implementation without FP.

    Thanks

    -Oscar

Reply
  • 0 in reply to Ronan Synnott

    Ronan,

    Thanks for your answer. According to ka004846, I should be able to use +nofp option to ensure no floating point is used. But actually 6.19 reports linking error if I use +nofp option. What do you think the behavior of 6.19 is correct? 

    We are working with a Cortex-R82 implementation without FP.

    Thanks

    -Oscar

Children