[all-commits] [llvm/llvm-project] 8c3445: [AArch64][LOH] Don't ignore regmasks in bundles by...

[Ahmed Bougacha via All-commits]

  Branch: refs/heads/release/14.x
  Home:   https://github.com/llvm/llvm-project
  Commit: 8c3445ac1c8b92cfc34282f6c8f6cdc3495878bf
      https://github.com/llvm/llvm-project/commit/8c3445ac1c8b92cfc34282f6c8f6cdc3495878bf
  Author: Ahmed Bougacha <ahmed at bougacha.org>
  Date:   2022-04-14 (Thu, 14 Apr 2022)

  Changed paths:
    M llvm/lib/Target/AArch64/AArch64CollectLOH.cpp
    M llvm/test/CodeGen/AArch64/loh.mir

  Log Message:
  -----------
  [AArch64][LOH] Don't ignore regmasks in bundles by iterating over instrs.

The LOH pass iterates over instructions to build its custom register
state machine, but it uses the top-level bundle iterator.
This should be okay, because when the wrapper BUNDLE MI is built,
it aggregates the register defs/uses in its instructions into MOs.

However, that doesn't apply to regmasks, and accumulating regmasks
across multiple instructions would be messy business.
There are a couple AnalyzePhysRegInBundle (/Virt) helpers that
do look at regmasks, but those don't fit in very well here.

AArch64 has started to use a few bundle instructions, specifically
as glorified pseudos for variant call instructions, which have regmasks.
So the LOH pass ends up ignoring regmasks.

Concretely, this has been wrong for a while, but, on aarch64, the
most common bundle (rv_marker call) was always followed by the
attached call instruction, a plain BL with a regmask.  Which
was properly detected by the pass.

However, we recently started keeping the attached call in the bundle,
so the regmask is now ignored.  And the pass happily combines ADRPs, of
say, x8, across the bundle, resulting in corrupt pointers later.

(cherry picked from commit cfa4fe7c51870fe6b480d541938f556cf0736fa2)