• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Subscribers 20 subscribers
  • Views 610 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

ARM Compiler 6.13 binary difference caused by UXTH and BEQ/BNE

Xinpeng Cao

When I build my ARM-CortexR5 project with ARM Compiler 6.13 twice, the binaries generated from first ELF and second ELF are different, afterwards I build the project 17 times, this issue is reproduced 3 times.

  • Sometimes the UXTH instruction is used.
  • Sometimes the BEQ is used rather than BNE.

This issue confused me for weeks, how to avoid the issues? Which version fixed it?

Product: DS-5 Professional 5.29.1
Component: ARM Compiler 6.13
Tool: armclang [5d895a00]

Parents
  • +1

    I guess the UXTH issue is fixed by the following defect, please help to confirm.

    [SDCOMP-53837] When compiling for T32 state, the compiler could generate incorrect code for a 16-bit literal value. This has been fixed.

Reply
  • +1

    I guess the UXTH issue is fixed by the following defect, please help to confirm.

    [SDCOMP-53837] When compiling for T32 state, the compiler could generate incorrect code for a 16-bit literal value. This has been fixed.

Children
No data