[llvm] [AMDGPU] Flatten recursive register resource info propagation (PR #142766)

[Janek van Oirschot via llvm-commits]

JanekvO wrote:

That'd be the way to go if we'd have all functions' resource info at the time of printing but with the resource info only known for the current function being processed, it's a lot harder to do something along these lines at this point in processing (at least, as far as I'm aware). Changing the resource usage info pass to a module pass for gathering resource usage for all functions is what caused issues with the pass pipeline, so also a tough sell as well for an approach. I could cache the already processed/printed functions and use that for recursion to determine resource info for functions within said recursion but I think it'd be much of the same as I have right now, just less traversing MCExprs.

However, I may be missing something so please do let me know if there's an (obvious) approach available here.

Thanks

https://github.com/llvm/llvm-project/pull/142766