[all-commits] [llvm/llvm-project] 34a659: [MLIR] Erase location of folded constants (#75415)

[Billy Zhu via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 34a65980d7d2e1b05e3fc88535cafe606ee55e04
      https://github.com/llvm/llvm-project/commit/34a65980d7d2e1b05e3fc88535cafe606ee55e04
  Author: Billy Zhu <billyzhu at modular.com>
  Date:   2023-12-21 (Thu, 21 Dec 2023)

  Changed paths:
    M mlir/include/mlir/Transforms/FoldUtils.h
    M mlir/lib/Transforms/SCCP.cpp
    M mlir/lib/Transforms/Utils/FoldUtils.cpp
    M mlir/test/Dialect/Transform/test-pattern-application.mlir
    A mlir/test/Transforms/canonicalize-debuginfo.mlir
    A mlir/test/Transforms/constant-fold-debuginfo.mlir
    M mlir/test/lib/Transforms/TestIntRangeInference.cpp

  Log Message:
  -----------
  [MLIR] Erase location of folded constants (#75415)

Follow up to the discussion from #75258, and serves as an alternate
solution for #74670.

Set the location to Unknown for deduplicated / moved / materialized
constants by OperationFolder. This makes sure that the folded constants
don't end up with an arbitrary location of one of the original ops that
became it, and that hoisted ops don't confuse the stepping order.