search for: arminstructionselector

...is, but I would imagine that none of the patterns using that are supported yet, and that's why we don't see any errors for ARM yet. > How ARM handle this? and I removed all ARM related code in RISCVXXX.cpp, > only keep skeleton for easy debug, please give me some hint, thanks a lot! ARMInstructionSelector has an ARMSubtarget reference called STI. We'll probably have to rename that to Subtarget to support something like this in the future. What you need to do when you run into this kind of error is to add the relevant members to your InstructionSelector. Each target may make slightly different a...

...692 unswitchNontrivialInvariants([snip]) [function] 40180 getAttrKind([snip]) [function] 35811 clang::DumpCompilerOptionsAction::ExecuteAction() [function] 32417 llvm::UpgradeIntrinsicCall([snip]) [function] 30239 bool llvm::InstructionSelector::executeMatchTable<(anonymous namespace)::ARMInstructionSelector const, [snip]) const [function] 29352 Next, let's look at the file view diffstat. This can be useful because it goes beyond simply identifying the files which grew the most. It actually describes which *functions* grew the most in those files, creating more opportunites to do something about...

...vialInvariants([snip]) [function] 40180 > getAttrKind([snip]) [function] 35811 > clang::DumpCompilerOptionsAction::ExecuteAction() [function] 32417 > llvm::UpgradeIntrinsicCall([snip]) [function] 30239 > bool llvm::InstructionSelector::executeMatchTable<(anonymous namespace)::ARMInstructionSelector const, [snip]) const [function] 29352 > > > Next, let's look at the file view diffstat. This can be useful because it goes > beyond simply identifying the files which grew the most. It actually describes > which *functions* grew the most in those files, creating more opportunit...

...snip]) [function] 40180 >> getAttrKind([snip]) [function] 35811 >> clang::DumpCompilerOptionsAction::ExecuteAction() [function] 32417 >> llvm::UpgradeIntrinsicCall([snip]) [function] 30239 >> bool llvm::InstructionSelector::executeMatchTable<(anonymous namespace)::ARMInstructionSelector const, [snip]) const [function] 29352 >> >> >> Next, let's look at the file view diffstat. This can be useful because it goes >> beyond simply identifying the files which grew the most. It actually describes >> which *functions* grew the most in those files, crea...