[llvm-branch-commits] [llvm] ExpandFp: Require RuntimeLibcallsInfo analysis (PR #165197)

Matt Arsenault via llvm-branch-commits llvm-branch-commits at lists.llvm.org
Fri Oct 31 22:05:26 PDT 2025


arsenm wrote:

> if every function in a module will always have the same set of available libcalls 

Yes, the set of RuntimeLibcalls should be consistent through a module, and only invalidated on link 

> then this way of making it a module analysis is ok at the cost of usability of the module analysis in function passes, but imo this is something that a function cares about, not a module. don't feel too strongly about this though

Separately I am going to introduce a new LibcallLoweringInfo, which will need to become another analysis which will be function level (though it's really Module + subtarget, so I'm questioning if it should really be a function analysis as well)

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


More information about the llvm-branch-commits mailing list