• Locked Locked
  • Replies 6 replies
  • Subscribers 119 subscribers
  • Views 4155 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

Optimizer removes ssub16 used to set GE flags

Mike Handler
Note: This was originally posted on 27th April 2009 at http://forums.arm.com

I'm using RVCT 3.0 compiler with the optimizer (e.g., -O3). My code has inline assembly.

Here's my problem: If the inline assembly uses a parallel subtract instruction (e.g., SSUB16) to set the GE flags for use by the SEL instruction, the optimizer removes the SSUB16.

It seems that the optimizer removes the SSUB16 because it doesn't see the register result being used, even though the GE results are indeed used.

Here's an example:
__inline int MAX16(int a1_a0, int b1_b0)
{
   register int maxVal16;
   __asm
   {
      ssub16  maxVal16, a1_a0, b1_b0
      sel     maxVal16, a1_a0, b1_b0
   };
   return(maxVal16);
}
int findMax(int a, int b )
{
   return (MAX16(a, b ));
}


The dump file has
    findMax
    $a
    .text
        0x00000000:    e6800fb1    ....    SEL      r0,r0,r1
        0x00000004:    e12fff1e    ../.    BX       lr



Is there a way to prevent this problem without adding cycles?   I can fix the problem by using a volatile ptr for the ssub16 result, but that adds extra cycles.

Thanks in advance for any help.
Parents
  • Arm Employee Badge
    Note: This was originally posted on 28th April 2009 at http://forums.arm.com

    It sounds like you could break up your single C function in to smaller pieces and only use the pragma O0 for the problematic part(s).

    The extreme solution is to simply dump the assembler in to a separate file using fromelf, fix the optimization bug by hand, and put the result through armasm.
Reply
  • Arm Employee Badge
    Note: This was originally posted on 28th April 2009 at http://forums.arm.com

    It sounds like you could break up your single C function in to smaller pieces and only use the pragma O0 for the problematic part(s).

    The extreme solution is to simply dump the assembler in to a separate file using fromelf, fix the optimization bug by hand, and put the result through armasm.
Children
No data