[llvm-dev] Dealing with illegal operand mappings in RegBankSelect (original) (raw)
Quentin Colombet via llvm-dev llvm-dev at lists.llvm.org
Tue Feb 26 16:25:49 PST 2019
- Previous message: [llvm-dev] Dealing with illegal operand mappings in RegBankSelect
- Next message: [llvm-dev] Dealing with illegal operand mappings in RegBankSelect
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Feb 26, 2019, at 4:18 PM, Matt Arsenault <arsenm2 at gmail.com> wrote:
On Feb 26, 2019, at 7:01 PM, Quentin Colombet <qcolombet at apple.com <mailto:qcolombet at apple.com>> wrote: I don’t get what you mean by “applyMapping to deal with it”. Won’t applyMapping will insert copies to rewrite these, hence how is this different from what the repairing code does? Unless, maybe, you’re talking about the target specific RegisterBankInfo::applyMapping not RegBankSelect::applyMapping. If that’s the case what do you do in here that we could maybe generalize? Sorry, I mean report them as legal so they are left as-is with no copy inserted. I can see the operand is illegal and do everything needed in the target applyMappingImpl (first sample case is https://reviews.llvm.org/D58512 <https://reviews.llvm.org/D58512>)
Wow, that’s quite a lot of code to fix a couple of operands :)
Couldn’t we do that expansion as part of the selection of the “pseudo copy”?
-Matt
-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190226/403b5076/attachment-0001.html>
- Previous message: [llvm-dev] Dealing with illegal operand mappings in RegBankSelect
- Next message: [llvm-dev] Dealing with illegal operand mappings in RegBankSelect
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]