[PATCH] Allowing MC backends to decide relaxation based on fixup resolution

[colinl at codeaurora.org]

Hi grosbach, rafael, mlambert, sidneym,

Currently a failure to resolve a fixup implies instruction relaxation which may not be correct for all targets.  In Hexagon, fixups might always or never be relaxed depending a combination of fixup type and instruction opcode.

This change adds a parameter to MCAsmBackend::fixupNeedsRelaxation() indicating whether the fixup was resolved and allows the backend to make the full relaxation decision.

Backends that do not use relaxation only have their function signatures changed.

REPOSITORY
  rL LLVM

http://reviews.llvm.org/D8217

Files:
  include/llvm/MC/MCAsmBackend.h
  lib/MC/MCAssembler.cpp
  lib/Target/AArch64/MCTargetDesc/AArch64AsmBackend.cpp
  lib/Target/ARM/MCTargetDesc/ARMAsmBackend.cpp
  lib/Target/Hexagon/MCTargetDesc/HexagonAsmBackend.cpp
  lib/Target/R600/MCTargetDesc/AMDGPUAsmBackend.cpp
  lib/Target/Sparc/MCTargetDesc/SparcAsmBackend.cpp
  lib/Target/SystemZ/MCTargetDesc/SystemZMCAsmBackend.cpp
  lib/Target/X86/MCTargetDesc/X86AsmBackend.cpp

EMAIL PREFERENCES
  http://reviews.llvm.org/settings/panel/emailpreferences/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D8217.21608.patch
Type: text/x-patch
Size: 7584 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150310/efcfad8e/attachment.bin>