aboutsummaryrefslogtreecommitdiff
path: root/lldb/test/API/python_api
diff options
context:
space:
mode:
authorMatt Arsenault <Matthew.Arsenault@amd.com>2025-12-03 16:00:12 -0500
committerGitHub <noreply@github.com>2025-12-03 22:00:12 +0100
commit04c81a99735c04b2018eeb687e74f9860e1d0e1b (patch)
tree273d8f6dbf7a0117f9182389e6f458bdead0cfbf /lldb/test/API/python_api
parent5cbd294ca2390069181d984644dac6ca34b5e95c (diff)
downloadllvm-04c81a99735c04b2018eeb687e74f9860e1d0e1b.tar.gz
llvm-04c81a99735c04b2018eeb687e74f9860e1d0e1b.tar.bz2
llvm-04c81a99735c04b2018eeb687e74f9860e1d0e1b.zip
CodeGen: Add LibcallLoweringInfo analysis pass (#168622)
The libcall lowering decisions should be program dependent, depending on the current module's RuntimeLibcallInfo. We need another related analysis derived from that plus the current function's subtarget to provide concrete lowering decisions. This takes on a somewhat unusual form. It's a Module analysis, with a lookup keyed on the subtarget. This is a separate module analysis from RuntimeLibraryAnalysis to avoid that depending on codegen. It's not a function pass to avoid depending on any particular function, to avoid repeated subtarget map lookups in most of the use passes, and to avoid any recomputation in the common case of one subtarget (and keeps it reusable across repeated compilations). This also switches ExpandFp and PreISelIntrinsicLowering as a sample function and module pass. Note this is not yet wired up to SelectionDAG, which is still using the LibcallLoweringInfo constructed inside of TargetLowering.
Diffstat (limited to 'lldb/test/API/python_api')
0 files changed, 0 insertions, 0 deletions