GNU Arm Embedded Toolchain

  1. Bug #1738730
  2. Comment #4

Comment 4 for bug 1738730

Revision history for this message
Murat Ursavas (murat-ursavas) wrote : Re: Simple OR'ed assignment breaks the code silently

Couldn't find something definite. Just have seen this one:

****************************

2015-12-17 Thomas Preud'homme <email address hidden>

  * config/arm/arm.h (TARGET_USE_MOVT): Check MOVT/MOVW availability
  with TARGET_HAVE_MOVT.
  (TARGET_HAVE_MOVT): Define.
  * config/arm/arm.c (const_ok_for_op): Check MOVT/MOVW
  availability with TARGET_HAVE_MOVT.
  * config/arm/arm.md (arm_movt): Use TARGET_HAVE_MOVT to check movt
  availability.
  (addsi splitter): Use TARGET_USE_MOVT to check whether to use
  movt + movw.
  (symbol_refs movsi splitter): Remove TARGET_32BIT check.
  (arm_movtas_ze): Use TARGET_HAVE_MOVT to check movt availability.
  * config/arm/constraints.md (define_constraint "j"): Use
  TARGET_HAVE_MOVT to check movt availability.
***********************

Maybe removing TARGET_32BIT could have an effect on this issue. It's a long shot, but I don't have further ideas based on this document:

https://gcc.gnu.org/svn/gcc/branches/ARM/embedded-5-branch/gcc/ChangeLog.arm