[llvm] [Analysis] Reuse RuntimeLibCalls.td for TargetLibraryInfo (PR #199529)

[Matt Arsenault via llvm-commits]

https://github.com/arsenm commented:

This is a different migration ordering than I was thinking. Yes, we should add the type information to RuntimeLibcalls. I wasn't thinking about generating TargetLibraryInfo from this, but eventually migrating TargetLibraryInfo uses to LibcallLoweringInfo.

Can you split this into 2 parts? First just adding the type signatures into RuntimeLibcalls. The hard part is getting these C-type specified signatures into RuntimeLibcalls::getFunctionTy. We need the C type to ABI lowering path 



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