Displaying 1 result from an estimated 1 matches for "prefernotcombinetoorframeindex".
2019 Mar 13
2
llvm combines "ADD frameindex, constant" to OR
...onverted to OR permanently. As a result, generated code use OR and
it causes run time error depends on the address of frame pointer.
I also checked visitOR, but I cannot find any undoing there.
My question is:
1. Is there any way to control this to avoid OR folding,
like TargetLowering::preferNotCombineToOrFrameIndex?
(or should we add new?)
2. How to optimize FrameIndex? I desire DAGCombiner use alignment
information on data, stack frame, or something.
Best Regards,
-- Kazushi