• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 21 subscribers
  • Views 1404 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

"Unknown Stack Size" problem with unsigned int operations

André Moutinho

Operations with unsigned int seems to cause the "Unknown Stack Size" problem during syntactic analysis.

Does anyone know how to fix this?

__arm_div_large (ARM, 0 bytes, Stack size unknown bytes, aeabi_sdiv.o(.text))

[Called By]

>> __aeabi_uidivmod

Thanks
Andre

Parents
  • 0

    This is basically the same problem as with vsprintf(), only this time it's a runtime library support routine that the analyzer doesn't know about. You'll run into this same problem every time your code refers to any of the functions in the runtime library. Or for that matter, any function the analysis tool doesn't have stack consumption data about.

Reply
  • 0

    This is basically the same problem as with vsprintf(), only this time it's a runtime library support routine that the analyzer doesn't know about. You'll run into this same problem every time your code refers to any of the functions in the runtime library. Or for that matter, any function the analysis tool doesn't have stack consumption data about.

Children