[all-commits] [llvm/llvm-project] 19279f: [debug-info] If one sees a spill with a dbg.addr u...

[Michael Gottesman via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 19279ffc77b8d224c447d4eb0ee0c727ab64babf
      https://github.com/llvm/llvm-project/commit/19279ffc77b8d224c447d4eb0ee0c727ab64babf
  Author: Michael Gottesman <mgottesman at apple.com>
  Date:   2022-02-11 (Fri, 11 Feb 2022)

  Changed paths:
    M llvm/lib/Transforms/Coroutines/CoroFrame.cpp
    A llvm/test/Transforms/Coroutines/coro-debug-dbg.addr-swift.ll
    A llvm/test/Transforms/Coroutines/coro-debug-dbg.addr.ll

  Log Message:
  -----------
  [debug-info] If one sees a spill with a dbg.addr use, salvageDebugInfo upon it and don't hoist it.

This ensures that if we have a dbg.addr in a coroutine funclet that is on one of
our function arguments, that the dbg.addr is not mapped to undef and also that
later it isn't hoisted to the front of the basic block. Instead it remains at
its original cloned location.

rdar://83957028

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