Lines Matching refs:bitset

47 in another bitset.
61 bitset:
65    <bitset name="#instruction" size="64">
69    </bitset>
76    <bitset name="#instruction-cat2" extends="#instruction">
105    </bitset>
108 bitset matches against a given bit pattern.  The leaf node's match/mask/
117    <bitset name="#instruction-cat2-1src" extends="#instruction-cat2">
137    </bitset>
139    <bitset name="absneg.f" extends="#instruction-cat2-1src">
141    </bitset>
144 the bitset inheritance tree) which has a single src register.  At the
151 You'll notice that ``SRC1`` refers back to a different bitset hierarchy
154 which have bitset types, parameters can be "passed" in via ``<param>``
157 outside of that bitset control the encoding/decoding, such as in the
162    <bitset name="#multisrc" size="16">
167    </bitset>
171    <bitset name="#multisrc-gpr" extends="#multisrc">
179    </bitset>
181 At some level in the bitset inheritance hiearchy, there is expected to be a
182 ``<display>`` element specifying a template string used during bitset
185 which are just echoed through to the resulting decoded bitset.
201 In many cases, a bitset is not convenient for describing the expected
205 of the size of the bitset inheritance tree.  For example, *every* cat2
209 An ``<override>`` in a bitset allows to redefine the display string, and/or
213 bitset (ie. the default case).
243    <bitset name="#instruction" size="64">
272    </bitset>
275 is a ``struct ir3_instruction *``.  In the case of bitset hierarchies with
277 along with a function that maps the bitset encode source to an enum value