[all-commits] [llvm/llvm-project] bd9145: Reapply [AMDGPU] Avoid resource propagation for re...

[Janek van Oirschot via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: bd9145c8c21334e099d51b3e66f49d51d24931ee
      https://github.com/llvm/llvm-project/commit/bd9145c8c21334e099d51b3e66f49d51d24931ee
  Author: Janek van Oirschot <janek.vanoirschot at amd.com>
  Date:   2024-11-15 (Fri, 15 Nov 2024)

  Changed paths:
    M llvm/include/llvm/MC/MCExpr.h
    M llvm/lib/MC/MCExpr.cpp
    M llvm/lib/MC/MCParser/AsmParser.cpp
    M llvm/lib/Target/AMDGPU/AMDGPUMCResourceInfo.cpp
    M llvm/lib/Target/AMDGPU/MCTargetDesc/AMDGPUMCExpr.cpp
    M llvm/lib/Target/AMDGPU/MCTargetDesc/AMDGPUMCExpr.h
    M llvm/test/CodeGen/AMDGPU/function-resource-usage.ll
    A llvm/test/CodeGen/AMDGPU/multi-call-resource-usage-mcexpr.ll
    A llvm/test/CodeGen/AMDGPU/recursive-resource-usage-mcexpr.ll

  Log Message:
  -----------
  Reapply [AMDGPU] Avoid resource propagation for recursion through multiple functions (#112251)

I was wrong last patch. I viewed the `Visited` set purely as a possible
recursion deterrent where functions calling a callee multiple times are
handled elsewhere. This doesn't consider cases where a function is
called multiple times by different callers still part of the same call
graph. New test shows the aforementioned case.

Reapplies #111004, fixes #115562.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications