[all-commits] [llvm/llvm-project] c5d240: WebAssembly: Don't store MachineFunction in Machin...

[Matt Arsenault via All-commits]

  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: c5d240093b60729829cb55823448e30bdfc69142
      https://github.com/llvm/llvm-project/commit/c5d240093b60729829cb55823448e30bdfc69142
  Author: Matt Arsenault <Matthew.Arsenault at amd.com>
  Date:   2020-06-24 (Wed, 24 Jun 2020)

  Changed paths:
    M llvm/lib/Target/WebAssembly/WebAssemblyExplicitLocals.cpp
    M llvm/lib/Target/WebAssembly/WebAssemblyLowerBrUnless.cpp
    M llvm/lib/Target/WebAssembly/WebAssemblyMachineFunctionInfo.cpp
    M llvm/lib/Target/WebAssembly/WebAssemblyMachineFunctionInfo.h
    M llvm/lib/Target/WebAssembly/WebAssemblyPeephole.cpp
    M llvm/lib/Target/WebAssembly/WebAssemblyRegNumbering.cpp
    M llvm/lib/Target/WebAssembly/WebAssemblyRegStackify.cpp

  Log Message:
  -----------
  WebAssembly: Don't store MachineFunction in MachineFunctionInfo

Soon it will be disallowed to depend on MachineFunction state in the
constructor. This was only being used to get the MachineRegisterInfo
for an assert, which I'm not sure is necessarily worth it. I would
think any missing defs would be caught by the verifier later instead.