[all-commits] [llvm/llvm-project] 0946e4: [Assignment Tracking][12/*] Account for assignment...

[Orlando Cazalet-Hyams via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 0946e463e8649896654b0dd39193db76a5789e11
      https://github.com/llvm/llvm-project/commit/0946e463e8649896654b0dd39193db76a5789e11
  Author: OCHyams <orlando.hyams at sony.com>
  Date:   2022-11-15 (Tue, 15 Nov 2022)

  Changed paths:
    M llvm/lib/Transforms/Utils/Local.cpp
    M llvm/lib/Transforms/Utils/PromoteMemoryToRegister.cpp
    A llvm/test/DebugInfo/Generic/assignment-tracking/mem2reg/phi.ll
    A llvm/test/DebugInfo/Generic/assignment-tracking/mem2reg/single-block-alloca.ll
    A llvm/test/DebugInfo/Generic/assignment-tracking/mem2reg/single-store-alloca.ll

  Log Message:
  -----------
  [Assignment Tracking][12/*] Account for assignment tracking in mem2reg

The Assignment Tracking debug-info feature is outlined in this RFC:

https://discourse.llvm.org/t/
rfc-assignment-tracking-a-better-way-of-specifying-variable-locations-in-ir

The changes for assignment tracking in mem2reg don't require much of a
deviation from existing behaviour. dbg.assign intrinsics linked to an alloca
are treated much in the same way as dbg.declare users of an alloca, except that
we don't insert dbg.value intrinsics to describe assignments when there is
already a dbg.assign intrinsic present, e.g. one linked to a store that is
going to be removed.

Reviewed By: jmorse

Differential Revision: https://reviews.llvm.org/D133295