Lines Matching refs:instructions

14 could be to use switch cases which list all the instructions along with formats
24 TableGen uses relationship models to map instructions with each other. These
27 describe all the instructions using that model. TableGen parses all the relation
29 instructions with each other. These tables are emitted in the
36     // Used to reduce search space only to the instructions using this
40     // List of fields/attributes that should be same for all the instructions in
42     // by all the instructions related by this relationship.
45     // List of fields/attributes that are same for all the instructions
55     // each column in the relation table. These are the instructions a key
67 to define a relationship model that relates predicated instructions to their
69 fields. For this relationship, non-predicated instructions are treated as key
76     // instructions modeling this relationship. This is done to reduce the
77     // search space only to these set of instructions.
84     // instructions need to have same value for BaseOpcode field. It can be any
89     // List of attributes that can be used to define key and column instructions
91     // to the function used for querying relation tables. Column instructions
92     // are the instructions they (key) can transform into.
96     // instructions involved in this relationship model.
99     // The key column contains non-predicated instructions.
102     // Two value columns - first column contains instructions with
103     // PredSense=true while second column has instructions with PredSense=false.
108 non-predicated instructions with their predicated forms. It also outputs the
117 instructions:
136 In this step, we modify these instructions to include the information
166 Please note that all the above instructions use ``PredRel`` as a base class.
168 instructions for ``getPredOpcode`` model. Any instruction not derived from
171 to have the same value for all 3 instructions in order to be related. Next,