• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 4 replies
  • Subscribers 349 subscribers
  • Views 6382 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

compile time constant expressions

Mike Rieker
Note: This was originally posted on 12th March 2009 at http://forums.arm.com

I am seeing code like this generated from the armcc v4.0 compiler (just downloaded it a couple hours ago):

  MOV r0,#5
  CLZ r0,r0
  RSB r7,r0,#0x3f

So I would think the compiler would know that R7 has 34 in it or whatever.  It isn't so bad these three instructions, it's just that in this case the code goes on to divide by the r7 value and so generates a call to __aeabi_uldivmod whereas I was expecting the compiler to generate a UMULL or something like that.

Is there some command-line optimization option I can use to fix this?  I am using this command line:

  armcc --cpu=ARM926EJ-S --inline -Otime -O3 -S -o test.s test.c

Thanks!
Mike
Parents
  • 0 Arm Employee Badge
    Note: This was originally posted on 14th March 2009 at http://forums.arm.com

    In case of these three instuctions , compiler should not be calling any devide function.

    Correct, however, the OP stated that the reason why the code was doubly inefficient was because the result was being passed onto a divide operation that could presumably also just have been optimised to a constant assignment. My example was just to generate the CLZ instruction containing assembly sequence posted.

    BYW CLZ is ARM assembly insturction.

    Correct, the __clz() intrinsic provides a way of generating this instruction from C code, or an equivalent assembly sequence for processors not implementing CLZ, e.g. ARM7TDMI.

    s.
Reply
  • 0 Arm Employee Badge
    Note: This was originally posted on 14th March 2009 at http://forums.arm.com

    In case of these three instuctions , compiler should not be calling any devide function.

    Correct, however, the OP stated that the reason why the code was doubly inefficient was because the result was being passed onto a divide operation that could presumably also just have been optimised to a constant assignment. My example was just to generate the CLZ instruction containing assembly sequence posted.

    BYW CLZ is ARM assembly insturction.

    Correct, the __clz() intrinsic provides a way of generating this instruction from C code, or an equivalent assembly sequence for processors not implementing CLZ, e.g. ARM7TDMI.

    s.
Children
No data