aboutsummaryrefslogtreecommitdiff
path: root/mlir/lib/Bindings/Python/MainModule.cpp
diff options
context:
space:
mode:
authorMin-Yih Hsu <min.hsu@sifive.com>2025-10-03 20:48:26 -0700
committerGitHub <noreply@github.com>2025-10-03 20:48:26 -0700
commit977b546c32d8978bc5682125e64e84aeee41ee76 (patch)
treec66f0efeb0f757d76dc8573fdfb103546e68d058 /mlir/lib/Bindings/Python/MainModule.cpp
parent910e536fb09f39493906005b9a8d7d1fbcc20e28 (diff)
downloadllvm-977b546c32d8978bc5682125e64e84aeee41ee76.zip
llvm-977b546c32d8978bc5682125e64e84aeee41ee76.tar.gz
llvm-977b546c32d8978bc5682125e64e84aeee41ee76.tar.bz2
[TableGen][SchedModel] Introduce a new SchedPredicate that checks against SubtargetFeature (#161888)
Introduce a new SchedPredicate, `FeatureSchedPredicate`, that holds true when a certain SubtargetFeature is enabled. This could be useful when we want to configure a scheduling model with subtarget features. I add this as a separate SchedPredicate rather than piggy-back on the existing `SchedPredicate<[{....}]>` because first and foremost, `SchedPredicate` is expected to only operate on MachineInstr, so it does _not_ appear in `MCGenSubtargetInfo::resolveVariantSchedClass` but only show up in `TargetGenSubtargetInfo::resolveSchedClass`. Yet I think `FeatureSchedPredicate` will be useful for both MCInst and MachineInstr. There is another subtle difference between `resolveVariantSchedClass` and `resolveSchedClass` regarding how we access the MCSubtargetInfo instance, if we really want to express `FeatureSchedPredicate` using `SchedPredicate<[{.....}]>`. So I thought it'll be easier to add another new SchedPredicate for SubtargetFeature.
Diffstat (limited to 'mlir/lib/Bindings/Python/MainModule.cpp')
0 files changed, 0 insertions, 0 deletions