llvm-project.git/llvm/lib/Target/PowerPC/PPCLowerMASSVEntries.cpp, branch users/nico/python-2

[NFC] Rename `Intrinsic::getDeclaration` to `getOrInsertDeclaration` (#111752)

2024-10-11T12:26:03+00:00

Rename the function to reflect its correct behavior and to be consistent
with `Module::getOrInsertFunction`. This is also in preparation of
adding a new `Intrinsic::getDeclaration` that will have behavior similar
to `Module::getFunction` (i.e, just lookup, no creation).

[NFC][LLVM] Clean up TLI VECFUNC macros. (#93178)

2024-05-24T10:16:27+00:00

Move the undef'ing of library specific macros to the places in the code
base where they are defined.

[PowerPC] Add pwr7 and pwr10 support to IBM MASSV pass on AIX

2021-07-26T23:21:38+00:00

Before MASSV only supported P8 and P9 on AIX ans Linux . This patch proposes
MASSV to add support of P7 and P10 only on AIX too.

Differential: https://reviews.llvm.org/D106678

[PowerPC] Updated the error message of MASSV pass to mention vectorization

2021-07-16T14:45:09+00:00

 is needed be enable on P8 and later targets.

 Differential Revision: https://reviews.llvm.org/D106091

[PowerPC] Removing _massv place holder

2021-03-08T21:43:24+00:00

Since P8 is the oldest machine supported by MASSV pass,
_massv place holder is removed and the oldest version of
MASSV functions is assumed. If the P9 vector specific is
detected in the compilation process, the P8 prefix will
be updated to P9.

Differential Revision: https://reviews.llvm.org/D98064

[llvm] Populate SmallVector at construction time (NFC)

2021-01-29T06:21:14+00:00

[PowerPC] dyn_cast should be dyn_cast_or_null in MASSV pass

2020-11-24T16:21:12+00:00

It is possible that we have different constants in different slots
of second vector double (float) of pow function. So, in this case
Exp->getSplatValue() will return nullptr. Here, I handle it properly.

Reviewed By: steven.zhang, PowerPC

Differential Revision: https://reviews.llvm.org/D91729

Use llvm::is_contained where appropriate (NFC)

2020-08-02T04:51:06+00:00

Use llvm::is_contained where appropriate (NFC)

Reviewed By: kazu

Differential Revision: https://reviews.llvm.org/D85083

DAGCombiner optimization for pow(x,0.75) and pow(x,0.25) on double and single precision even in case massv function is asked

2020-06-12T14:02:16+00:00

Here, I am proposing to add an special case for massv powf4/powd2 function (SIMD counterpart of powf/pow function in MASSV library) in MASSV pass to get later optimizations like conversion from pow(x,0.75) and pow(x,0.25) for double and single precision to sequence of sqrt's in the DAGCombiner in vector float case. My reason for doing this is: the optimized pow(x,0.75) and pow(x,0.25) for double and single precision to sequence of sqrt's is faster than powf4/powd2 on P8 and P9.

In case MASSV functions is called, and if the exponent of pow is 0.75 or 0.25, we will get the sequence of sqrt's and if exponent is not 0.75 or 0.25 we will get the appropriate MASSV function.

Reviewed By: steven.zhang

Tags: #LLVM #PowerPC

Differential Revision: https://reviews.llvm.org/D80744

[llvm][NFC][CallSite] Remove Implementation uses of CallSite

2020-04-14T21:49:47+00:00

Reviewers: dblaikie, davidxl, craig.topper

Subscribers: arsenm, dschuff, nemanjai, jvesely, nhaehnle, sbc100, jgravelle-google, hiraditya, aheejin, kbarton, kerbowa, llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D78142