Displaying 6 results from an estimated 6 matches for "simplifyfaddinst".
2020 Nov 16
1
Complex proposal v3 + roundtable agenda
...ing the pattern matcher to recognize intrinsics
> gets us a long way. But we'd also need to update IR passes in places
> where the Opcode is explicitly checked. E.g.:
>
> ```
> switch (Opcode) {
> <snipped>
> case Instruction::FAdd: <== ***HERE***
> return SimplifyFAddInst(LHS, RHS, FastMathFlags(), Q, MaxRecurse);
> ```
>
> And when a transformation succeeds, we'd need to update how the result
> is returned. E.g.:
>
> ```
> // (-X) + Y --> Y - X
> Value *X, *Y;
> if (match(&I, m_c_FAdd(m_FNeg(m_Value(X)), m_Value(Y))))
>...
2020 Nov 12
2
Complex proposal v3 + roundtable agenda
...multiply.
It's true that teaching the pattern matcher to recognize intrinsics
gets us a long way. But we'd also need to update IR passes in places
where the Opcode is explicitly checked. E.g.:
```
switch (Opcode) {
<snipped>
case Instruction::FAdd: <== ***HERE***
return SimplifyFAddInst(LHS, RHS, FastMathFlags(), Q, MaxRecurse);
```
And when a transformation succeeds, we'd need to update how the result
is returned. E.g.:
```
// (-X) + Y --> Y - X
Value *X, *Y;
if (match(&I, m_c_FAdd(m_FNeg(m_Value(X)), m_Value(Y))))
return BinaryOperator::CreateFSubFMF(Y, X,...
2020 Nov 13
0
Complex proposal v3 + roundtable agenda
...ng the pattern matcher to recognize intrinsics
> gets us a long way. But we'd also need to update IR passes in places
> where the Opcode is explicitly checked. E.g.:
>
> ```
> switch (Opcode) {
> <snipped>
> case Instruction::FAdd: <== ***HERE***
> return SimplifyFAddInst(LHS, RHS, FastMathFlags(), Q, MaxRecurse);
> ```
>
> And when a transformation succeeds, we'd need to update how the result
> is returned. E.g.:
>
> ```
> // (-X) + Y --> Y - X
> Value *X, *Y;
> if (match(&I, m_c_FAdd(m_FNeg(m_Value(X)), m_Value(Y))))
>...
2013 Dec 16
0
[LLVMdev] Float undef value propagation
On Sun, Dec 15, 2013 at 5:12 PM, Philip Reames <listmail at philipreames.com>wrote:
> On 12/14/2013 05:18 PM, Dan Gohman wrote:
>
>> On Thu, Dec 12, 2013 at 5:43 PM, Owen Anderson <resistor at mac.com
>> <mailto:resistor at mac.com>> wrote:
>>
>>
>> On Dec 12, 2013, at 4:57 PM, Philip Reames
>> <listmail at philipreames.com
2013 Dec 16
3
[LLVMdev] Float undef value propagation
On 12/14/2013 05:18 PM, Dan Gohman wrote:
> On Thu, Dec 12, 2013 at 5:43 PM, Owen Anderson <resistor at mac.com
> <mailto:resistor at mac.com>> wrote:
>
>
> On Dec 12, 2013, at 4:57 PM, Philip Reames
> <listmail at philipreames.com <mailto:listmail at philipreames.com>> wrote:
>
>> undef + any == NaN (since undef can be NaN) or undef +
2020 Nov 12
5
Complex proposal v3 + roundtable agenda
On Thu, Nov 12, 2020 at 12:03 PM Florian Hahn via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> Hi,
>
> There’s growing interest among our users to make better use of dedicated hardware instructions for complex math and I would like to re-start the discussion on the topic. Given that this original thread was started a while ago apologies if I missed anything already discussed