Yaniv via llvm-dev
2017-Nov-07 15:27 UTC
[llvm-dev] Mapping between instruction ins/outs to instruction bits-field
Hi, How does the mapping between instruction inputs and outputs to the instruction bits-field is done?>From what I saw it either by name matching or by positionalmatching of unassigned bits-fields, and the two methods can't be mixed. Is it correct? Supposing the above is correct then, setting inputs names in MIOperandInfo (of custom Operand) should behave as if they were specified directly in the out/ins list? Thanks, Yaniv
Yaniv via llvm-dev
2017-Nov-09 05:09 UTC
[llvm-dev] Mapping between instruction ins/outs to instruction bits-field
CGIOperandList::CGIOperandList() ignores names that are specified in MIOperandInfo (Not my preferred logic). I did find "noNamedPositionallyEncodedOperands" that will probably do fine in most of my cases. Anyway, thanks for your help. On Tue, 2017-11-07 at 17:27 +0200, Yaniv wrote:> Hi, > > How does the mapping between instruction inputs and outputs > to the instruction bits-field is done? > > From what I saw it either by name matching or by positional > matching of unassigned bits-fields, and the two methods can't > be mixed. Is it correct? > > Supposing the above is correct then, setting inputs names in > MIOperandInfo (of custom Operand) should behave as if they were > specified directly in the out/ins list? > > Thanks, > Yaniv >