<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/llvm/test/CodeGen/PowerPC, branch meklort-10.0.1</title>
<subtitle>Project Ortega BCM5719 LLVM</subtitle>
<id>https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1</id>
<link rel='self' href='https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/'/>
<updated>2020-06-26T20:45:41+00:00</updated>
<entry>
<title>[DAGCombine] Check the uses of negated floating constant and remove the hack</title>
<updated>2020-06-26T20:45:41+00:00</updated>
<author>
<name>QingShan Zhang</name>
<email>qshanz@cn.ibm.com</email>
</author>
<published>2020-03-05T03:42:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=76ceebb0d96361de2b61bf8e504d306d1f2e492f'/>
<id>urn:sha1:76ceebb0d96361de2b61bf8e504d306d1f2e492f</id>
<content type='text'>
PowerPC hits an assertion due to somewhat the same reason as https://reviews.llvm.org/D70975.
Though there are already some hack, it still failed with some case, when the operand 0 is NOT
a const fp, it is another fma that with const fp. And that const fp is negated which result in multi-uses.

A better fix is to check the uses of the negated const fp. If there are already use of its negated
value, we will have benefit as no extra Node is added.

Differential revision: https://reviews.llvm.org/D75501

(cherry picked from commit 3906ae387f0775dfe4426e4336748269fafbd190)
</content>
</entry>
<entry>
<title>[PPCAsmPrinter] support 'L' output template for memory operands</title>
<updated>2020-06-25T23:19:39+00:00</updated>
<author>
<name>Nick Desaulniers</name>
<email>ndesaulniers@google.com</email>
</author>
<published>2020-06-15T21:21:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=b294e611271abeb5c9c49d7fb216b9bdcc323872'/>
<id>urn:sha1:b294e611271abeb5c9c49d7fb216b9bdcc323872</id>
<content type='text'>
Summary:
L is meant to support the second word used by 32b calling conventions for 64b arguments.

This is required for build 32b PowerPC Linux kernels after upstream
commit 334710b1496a ("powerpc/uaccess: Implement unsafe_put_user() using 'asm goto'")

Thanks for the report from @nathanchance, and reference to GCC's
implementation from @segher.

Fixes: pr/46186
Fixes: https://github.com/ClangBuiltLinux/linux/issues/1044

Reviewers: echristo, hfinkel, MaskRay

Reviewed By: MaskRay

Subscribers: MaskRay, wuzish, nemanjai, hiraditya, kbarton, steven.zhang, llvm-commits, segher, nathanchance, srhines

Tags: #llvm

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

(cherry picked from commit 2d8e105db6bea10a6b96e4a094e73a87987ef909)
</content>
</entry>
<entry>
<title>[PowerPC] Do not assume operand of ADDI is an immediate</title>
<updated>2020-06-23T21:46:06+00:00</updated>
<author>
<name>Nemanja Ivanovic</name>
<email>nemanja.i.ibm@gmail.com</email>
</author>
<published>2020-06-08T03:16:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=1f3be0e9b7b476780e5226aa95488a4a0a262961'/>
<id>urn:sha1:1f3be0e9b7b476780e5226aa95488a4a0a262961</id>
<content type='text'>
After pseudo-expansion, we may end up with ADDI (add immediate)
instructions where the operand is not an immediate but a relocation.
For such instructions, attempts to get the immediate result in
assertion failures for obvious reasons.

Fixes: https://bugs.llvm.org/show_bug.cgi?id=45432
(cherry picked from commit a56d057dfe3127c111c3470606c04e96d35b1fa3)
</content>
</entry>
<entry>
<title>[PowerPC] Unaligned FP default should apply to scalars only</title>
<updated>2020-06-23T20:57:14+00:00</updated>
<author>
<name>Nemanja Ivanovic</name>
<email>nemanja.i.ibm@gmail.com</email>
</author>
<published>2020-05-26T14:58:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=177a9ac3c6bcb89ca2f900e20caad92fdeabe9d2'/>
<id>urn:sha1:177a9ac3c6bcb89ca2f900e20caad92fdeabe9d2</id>
<content type='text'>
As reported in PR45186, we could be in a situation where we don't
want to handle unaligned memory accesses for FP scalars but still
have VSX (which allows unaligned access for vectors). Change the
default to only apply to scalars.

Fixes: https://bugs.llvm.org/show_bug.cgi?id=45186
(cherry picked from commit 099a875f28d0131a6ae85af91b9eb8627917fbbe)
</content>
</entry>
<entry>
<title>[PowerPC] Prevent legalization loop from promoting SELECT_CC from v4i32 to v4i32</title>
<updated>2020-06-22T22:09:29+00:00</updated>
<author>
<name>Nemanja Ivanovic</name>
<email>nemanjai@ca.ibm.com</email>
</author>
<published>2020-05-26T01:07:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=eac91d5864010a25e7e693ad565b64467dfa6ab9'/>
<id>urn:sha1:eac91d5864010a25e7e693ad565b64467dfa6ab9</id>
<content type='text'>
As reported in https://bugs.llvm.org/show_bug.cgi?id=45709 we can hit an
infinite loop in legalization since we set the legalization action for
ISD::SELECT_CC for all fixed length vector types to Promote. Without some
different legalization action for the type being promoted to, the legalizer
simply loops. Since we don't have patterns to match the node, the right
legalization action should be Expand.

Differential revision: https://reviews.llvm.org/D79854

(cherry picked from commit 793cc518b9428a0b7a40c59d4ecd5939a7bc84f7)
</content>
</entry>
<entry>
<title>[PowerPC] Add missing handling for half precision</title>
<updated>2020-06-22T22:03:26+00:00</updated>
<author>
<name>Tom Stellard</name>
<email>tstellar@redhat.com</email>
</author>
<published>2020-05-28T21:09:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=1abba52044ddc7d79a985fc9ec0734db54ebe6b3'/>
<id>urn:sha1:1abba52044ddc7d79a985fc9ec0734db54ebe6b3</id>
<content type='text'>
The fix for PR39865 took care of some of the handling for half precision
but it missed a number of issues that still exist. This patch fixes the
remaining issues that cause crashes in the PPC back end.

Fixes: https://bugs.llvm.org/show_bug.cgi?id=45776

Differential revision: https://reviews.llvm.org/D79283

(cherry picked from commit 1a493b0fa556a07c728862c3c3f70bfd8683bef0)
</content>
</entry>
<entry>
<title>[PowerPC] Do not attempt to reuse load for 64-bit FP_TO_UINT without FPCVT</title>
<updated>2020-05-19T15:31:01+00:00</updated>
<author>
<name>Nemanja Ivanovic</name>
<email>nemanja.i.ibm@gmail.com</email>
</author>
<published>2020-04-20T17:59:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=3de89abf189e63da4edbfda509ed3d421bdba1a9'/>
<id>urn:sha1:3de89abf189e63da4edbfda509ed3d421bdba1a9</id>
<content type='text'>
We call the function that attempts to reuse the conversion without checking
whether the target matches the constraints that the callee expects. This patch
adds the check prior to the call.

Fixes: https://bugs.llvm.org/show_bug.cgi?id=43976

Differential revision: https://reviews.llvm.org/D77564

(cherry picked from commit 64b31d96dfd6c05e6d52d8798726dec60502cfde)
</content>
</entry>
<entry>
<title>[PowerPC] Don't generate ST_VSR_SCAL_INT if power8-vector is disabled</title>
<updated>2020-04-22T21:54:22+00:00</updated>
<author>
<name>Kai Luo</name>
<email>lkail@cn.ibm.com</email>
</author>
<published>2020-04-01T02:15:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=b11ecd196540d87cb7db190d405056984740d2ce'/>
<id>urn:sha1:b11ecd196540d87cb7db190d405056984740d2ce</id>
<content type='text'>
Summary:
In https://bugs.llvm.org/show_bug.cgi?id=45297, it fails selecting
instructions for `PPCISD::ST_VSR_SCAL_INT`. The reason it generate the
`PPCISD::ST_VSR_SCAL_INT` with `-power8-vector` in IR is PPC's
combiner checks `hasP8Altivec` rather than `hasP8Vector`. This patch
should resolve PR45297.

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

(cherry picked from commit 8eb40e41f6ec99985a292e342ec303a0bd6f5f41)
</content>
</entry>
<entry>
<title>[PowerPC] Fix test for PR45297 to adapt build without asserts. NFC.</title>
<updated>2020-04-22T21:54:22+00:00</updated>
<author>
<name>Kai Luo</name>
<email>lkail@cn.ibm.com</email>
</author>
<published>2020-03-27T05:28:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=66cfbf17a18513de5551d6cdda563a2864d13400'/>
<id>urn:sha1:66cfbf17a18513de5551d6cdda563a2864d13400</id>
<content type='text'>
(cherry picked from commit 26b46b67d806a5299a93b1b3bca1548cb47487ff)
</content>
</entry>
<entry>
<title>[PowerPC] Enhance test for PR45297. NFC.</title>
<updated>2020-04-22T21:54:22+00:00</updated>
<author>
<name>Kai Luo</name>
<email>lkail@cn.ibm.com</email>
</author>
<published>2020-03-27T03:30:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=40633cc752a4ffecac22c6134761464bdbc8e10a'/>
<id>urn:sha1:40633cc752a4ffecac22c6134761464bdbc8e10a</id>
<content type='text'>
(cherry picked from commit 351b19231554d4dba29c42c798176f1ff3286a32)
</content>
</entry>
</feed>
