[llvm-bugs] [Bug 45025] New: [entry values] ARM isCopyInstrImpl incorrect for VMOVS

via llvm-bugs llvm-bugs at lists.llvm.org
Tue Feb 25 17:06:17 PST 2020


            Bug ID: 45025
           Summary: [entry values] ARM isCopyInstrImpl incorrect for VMOVS
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: Backend: ARM
          Assignee: unassignedbugs at nondot.org
          Reporter: vsk at apple.com
                CC: llvm-bugs at lists.llvm.org, smithp352 at googlemail.com,
                    Ties.Stuij at arm.com

We get the following assertion failure when building ARM code:

Assertion failed: (!TRI->isSuperOrSubRegisterEq(Reg, DestReg) &&
"TargetInstrInfo::describeLoadedValue can't describe super- or " "sub-regs for
copy instructions"

The following instruction is passed to TargetInstrInfo::describeLoadedValue:

$s1 = VMOVS killed $s21, 14, $noreg, implicit-def $d0

ARMBaseInstrInfo::isCopyInstrImpl reports that this is a copy:

  Optional<DestSourcePair> isCopyInstr(const MachineInstr &MI) const {
    if (MI.isCopy()) {
      return DestSourcePair{MI.getOperand(0), MI.getOperand(1)};
    return isCopyInstrImpl(MI); // <- Reached.


  if (!MI.isMoveReg() ||
      (MI.getOpcode() == ARM::VORRq &&
       MI.getOperand(1).getReg() != MI.getOperand(2).getReg()))
    return None;
  return DestSourcePair{MI.getOperand(0), MI.getOperand(1)}; // <- Reached.

According to TRI, llvm think that s1 is a sub-register of s21. I'm not sure
that's what the docs say:
(this makes it look like s{0..31} are independent single-word registers).

Regardless, istm that ARMBaseInstrInfo::isCopyInstrImpl should be taking a
whitelisting approach, not a blacklist. I.e. we should not allow non-copy
instructions we haven't explicitly handled be treated as copies.

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200226/72b94cc0/attachment.html>

More information about the llvm-bugs mailing list