forked from OSchip/llvm-project
a128292b90
Some of the lower implementations were relying on this, however the type was not set depending on which form .lower* helper form you were using. For instance, if you used an unconditonal lower(), the type was never set. Most of the lower actions do not benefit from a type parameter, and just expand in terms of the original operation's types. However, some lowerings could benefit from an additional type hint to combine a promotion and an expansion. An example of this is for add/sub sat. The DAG integer legalization tries to use smarter expansions directly when promoting the integer type, and doesn't always produce the same instruction with a wider type. Treat this as an optional hint argument, that only means something for specific lower actions. It may be useful to generalize this mechanism to pass a full list of type indexes and desired types, but I haven't run into a case like that yet. |
||
---|---|---|
.. | ||
GMIR.rst | ||
GenericOpcode.rst | ||
IRTranslator.rst | ||
InstructionSelect.rst | ||
KnownBits.rst | ||
Legalizer.rst | ||
Pipeline.rst | ||
Porting.rst | ||
RegBankSelect.rst | ||
Resources.rst | ||
block-extract.png | ||
index.rst | ||
pipeline-overview-customized.png | ||
pipeline-overview-with-combiners.png | ||
pipeline-overview.png | ||
testing-pass-level.png | ||
testing-unit-level.png |