Lines Matching full:your

9 During the course of using LLVM, you may wish to customize it for your research
20 that you intend to use with your extension, and there are ``many`` LLVM analyses
24 instruction, and is transparent to optimization passes.  If your added
50    Add an entry for your intrinsic.  Describe its memory access characteristics
58    If it is possible to constant fold your intrinsic, add support to it in the
63    Add test cases for your test cases to the test suite
68 Add support to the .td file for the target(s) of your choice in
93    Add code to print the node to ``getOperationName``.  If your new node can be
96     appropriate number of arguments, and add a case for your node to the switch
98     of arguments as your new node.
104    minimum, you will need to add a case statement for your node in
108    natively support the new node.  In this case, you must also add code in your
109    node's case statement in ``LegalizeOp`` to Expand your node into simpler,
116     will also need to add code to your node's case statement in ``LegalizeOp``
117     to Promote your node's operands to a larger size, and perform the correct
125    Add a case for your node in ``ExpandOp`` to teach the legalizer how to
127    into high and low halves.  This case will be used to support your node with a
132    If your node can be combined with itself, or other existing nodes in a
141    DAGToDAGISel).  The default behavior for a target is to assume that your new
143    does not natively support your node, then tell the target to either Promote
145    code you wrote in ``LegalizeOp`` above to decompose your new node into other
153    match an instruction to your new node, you must add a def for that node to
161    pattern for your new node that uses one or more target nodes.  Documentation
169    Add test cases for your new node to the test suite.
183    add a number for your instruction and an enum name
187    add a definition for the class that will represent your instruction
191    add a prototype for a visitor to your new instruction type
195    add a new token to parse your instruction from assembly text file
199    add the grammar on how your instruction can be read and what it will
204    add a case for your instruction and how it will be parsed from bitcode
208    add a case for your instruction and how it will be parsed from bitcode
212    add a case for how your instruction will be printed out to assembly
218 #. Test your instruction
222    add support for your instruction to code generators, or add a lowering pass.
226    add your test cases to the test suite.
271    BitstreamWriter &Stream)`` to serialize your type
275    modify ``bool BitcodeReader::ParseTypeType()`` to read your data type
314    BitstreamWriter &Stream)`` to serialize your type
318    modify ``bool BitcodeReader::ParseTypeType()`` to read your data type