[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-05-28 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=406256 Carl Love changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because:

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-05-28 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=406256 Carl Love changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-05-27 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=406256 --- Comment #12 from Julian Seward --- > Updated patch to fix issues with dnormal values v5 (27.44 KB, patch) > 2019-05-15 21:27 UTC, Carl Love Details > Update test case, add new test (1.81 MB, patch) > 2019-05-15 21:28 UTC, Carl Love Carl,

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-05-27 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=406256 Julian Seward changed: What|Removed |Added Attachment #119920|0 |1 is obsolete|

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-05-27 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=406256 Julian Seward changed: What|Removed |Added Attachment #119940|0 |1 is obsolete|

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-05-15 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=406256 --- Comment #11 from Carl Love --- Julian: > https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.kde.org_sho > w-5Fbug.cgi-3Fid-3D406256=DwIFaQ=jf_iaSHvJObTbx- > siA1ZOg=RFEmMkZAk > -- >

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-05-15 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=406256 --- Comment #10 from Carl Love --- Created attachment 120090 --> https://bugs.kde.org/attachment.cgi?id=120090=edit Update test case, add new test The test case patch that goes with the subnormal changes in VEX. -- You are receiving this mail

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-05-15 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=406256 --- Comment #9 from Carl Love --- Created attachment 120089 --> https://bugs.kde.org/attachment.cgi?id=120089=edit Updated patch to fix issues with dnormal values v5 Updated the patch per latest comments from Julian. Split patch into VEX patch and

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-05-14 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=406256 --- Comment #8 from Julian Seward --- Thanks for the respin. I have mostly only minor comments about it. Is OK to land provided all the comments below are addressed, except for the one about vectorising negateVF32, which would be nice to fix if you

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-05-09 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=406256 --- Comment #7 from Carl Love --- Created attachment 119940 --> https://bugs.kde.org/attachment.cgi?id=119940=edit Updated patch to fix issues with dnormal values v5 Updated patch after finding issues on Power 7. The new assembly code was

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-05-08 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=406256 --- Comment #6 from Carl Love --- Additional testing shows that the mtvsrd and mfvsrd instructions which are used in the assembly interface functions are not supported on P7 and earlier. Will need to rework current patch. -- You are receiving this

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-05-08 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=406256 Carl Love changed: What|Removed |Added Attachment #119918|0 |1 is obsolete||

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-05-08 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=406256 Carl Love changed: What|Removed |Added Attachment #119504|0 |1 is obsolete||

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-04-19 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=406256 Carl Love changed: What|Removed |Added Attachment #119258|0 |1 is obsolete||

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-04-08 Thread Will Schmidt
https://bugs.kde.org/show_bug.cgi?id=406256 --- Comment #2 from Will Schmidt --- I have no input into a different better spot for getRRegUniverse_PPC changes. A few other patch comments: +++ b/Makefile.all.am the "-mvsx -maltivec" combo can be shrunk to just "-mvsx" . (mvsx is a superset

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-04-05 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=406256 Carl Love changed: What|Removed |Added CC||will_schm...@vnet.ibm.com -- You are receiving

[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting

2019-04-05 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=406256 --- Comment #1 from Carl Love --- Created attachment 119258 --> https://bugs.kde.org/attachment.cgi?id=119258=edit Proposed fix for making the subnormal results track the VSCR[NJ] bit The attachment is a proposed fix for the issue. The Iops to