Implementation in NEON of non uniform address jumps

Parents
  • Note: This was originally posted on 13th July 2012 at http://forums.arm.com

    Without details of what goes wrong it is very hard to provide any specific help. In general "O3" is very aggressive and assumes you have coded to the C standard (this allows it to make more assumptions and so optimize more). If any of your code is "off spec" then you'll start getting issues.

    I would suggest one of:
    * Don't use O3 if you have issues
    * Look at using "objdump" (gcc) "fromelf" RVCT to dump the disassembly to see if you can spot the issue.
    * Try some smaller C files containing each function and compile most with O2 and then test each file individually with O3. This can help narrow it down.
Reply
  • Note: This was originally posted on 13th July 2012 at http://forums.arm.com

    Without details of what goes wrong it is very hard to provide any specific help. In general "O3" is very aggressive and assumes you have coded to the C standard (this allows it to make more assumptions and so optimize more). If any of your code is "off spec" then you'll start getting issues.

    I would suggest one of:
    * Don't use O3 if you have issues
    * Look at using "objdump" (gcc) "fromelf" RVCT to dump the disassembly to see if you can spot the issue.
    * Try some smaller C files containing each function and compile most with O2 and then test each file individually with O3. This can help narrow it down.
Children
No data
More questions in this forum