• Locked Locked
  • Replies 4 replies
  • Subscribers 119 subscribers
  • Views 3640 views
  • Users 0 members are here
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

Optimization of algorithm on ARMCortex A8(using NEON)

Girisha SG
Note: This was originally posted on 1st June 2011 at http://forums.arm.com

I am new to code optimization for speed(is the main focus)/memory etc

I am looking out for ,

1. We have the algorithms implemented using floating point operations. As I understand NEON has floating point units & hence we dont have to rewrite the algorithms in fixed points, is there anything like floating point operations are slower than fixed point operations or they are same or any other differences with respect to final CPU load/speed?
2. Do we need to take any special care/special optimization techniques for NEON?
3. I would like to know optimization techniques for ARM Cortex A8 (except using intrinsics :), like cache/memory optimizations), do's & dont's.
4. Keywords/anything else to compiler/linker to instruct RVDS to generate optimized code
5. How can I instruct the complier/linker to use NEON accelarator?
6. Any other guidlines to speed optimization using RVDS & GCC compilers.
Parents
  • Note: This was originally posted on 1st June 2011 at http://forums.arm.com

    1 - Floating point is a little bit slower than integer operation, but the gap is not too important.
    If your source data and your result data are 32 bit float, it is not usefull to use fixed point operation.
    If your datas are integers, it could be a good idea to try fixed point mode.

    2 - Yes there is a lot of hint to optimize NEON:
    - data alignment
    - pipeline optimisation
    - never transfer NEON register to ARM register.
    - NEON do not have Divide and Square root opération, if you have to use these VPf opération it could reduce significatively the performance.


    3 - The only correct way to optimize NEON code is to do it in assembly.

    4, 5, 6
    I can't help you about those points.

    Etienne
Reply
  • Note: This was originally posted on 1st June 2011 at http://forums.arm.com

    1 - Floating point is a little bit slower than integer operation, but the gap is not too important.
    If your source data and your result data are 32 bit float, it is not usefull to use fixed point operation.
    If your datas are integers, it could be a good idea to try fixed point mode.

    2 - Yes there is a lot of hint to optimize NEON:
    - data alignment
    - pipeline optimisation
    - never transfer NEON register to ARM register.
    - NEON do not have Divide and Square root opération, if you have to use these VPf opération it could reduce significatively the performance.


    3 - The only correct way to optimize NEON code is to do it in assembly.

    4, 5, 6
    I can't help you about those points.

    Etienne
Children
No data