Use LegalizerInfo::isLegalOrCustom instead.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
TBH I don't understand why D99283 introduced this target lowering hook in the first place. Comments on the review say "The annoying part (for AArch64) is that the legality checks don't work with custom legalization". Did isLegalOrCustom not exist back then? Or does it not do the right thing? (I don't see any tests failing with this patch.)
Comment Actions
Legality rules can't be context dependent on the specific operands used, but IIRC here it only wants to use it if the operands are constants
Comment Actions
Well in practice the implementations of isConstantUnsignedBitfieldExtractLegal did exactly the same as the legal-or-custom check anyway, so it still seems redundant.