Displaying 2 results from an estimated 2 matches for "getnegargument".
2018 Sep 26
2
[FPEnv] FNEG instruction
...shuffle canonicalizations on unary
(or ternary) operations? That may be a better fix in the long run.
> But glancing at Reassociate.cpp is scarier. It does a lot of stuff like
> this:
> if (BinaryOperator::isNeg(TheOp) || BinaryOperator::isFNeg(TheOp))
> X = BinaryOperator::getNegArgument(TheOp);
>
> I think that's going to fail without a (terrible) hack to treat the
> proposed fneg as a binop. So that's probably a preliminary requirement:
> find all uses of BinaryOperator::isFNeg() and update them to use m_FNeg().
> That should be done ahead of the IR change...
2018 Sep 25
2
[FPEnv] FNEG instruction
On Tue, Sep 25, 2018 at 1:39 PM Sanjay Patel <spatel at rotateright.com> wrote:
> I have 1 concern about adding an explicit fneg op to IR:
>
> Currently, fneg qualifies as a binop in IR (since there's no other way to
> represent it), and we have IR transforms that are based on matching that
> pattern (m_BinOp). With a proper unary fneg instruction, those transforms
>