[llvm-dev] Handling node through TargetLowering::LowerOperation vs TargetLowering::ReplaceNodeResults
Przemyslaw Ossowski via llvm-dev
llvm-dev at lists.llvm.org
Tue Jan 28 12:40:08 PST 2020
Thank you Craig for explanation.
Could be the same algorithm used for custom legalizing given node in
LowerOperation and ReplaceNodeResults in case results and inputs of the
node are illegal?
Or actually such situation is impossible and for given node either
LowerOperation or ReplaceNodeResults can be only called?
wt., 28 sty 2020, 18:48 użytkownik Craig Topper <craig.topper at gmail.com>
> ReplaceNodeResults is called by the type legalizer for custom legalizing
> any of the results of a node that have an illegal type.
> LowerOperation is called by the type legalizer to custom legalize node
> inputs that have an illegal type. I believe technically it calls
> LowerOperationWrapper, but that forwards to LowerOperation by default.
> LowerOperation is also called for custom legalizing nodes with legal types
> after type legalization by both the vector op legalizer and the DAG
> legalizer. In those cases LowerOperation is called directly and does not
> call LowerOperationWrapper.
> On Tue, Jan 28, 2020 at 9:10 AM Przemyslaw Ossowski via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>> I see that for different targets in classes which inherits from
>> TargetLowering there are implemented both methods:
>> LowerOperation and ReplaceNodeResults
>> What decides that for one given ISD we have to add handling in
>> LowerOperation and for other in ReplaceNodeResults, when for both
>> SetOperationAction is configured to be Custom?
>> Is it related with number of results of given operation and
>> LowerOperation is called when there is only one SDValue?
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev