https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #13 from Pat Haugen ---
Author: pthaugen
Date: Mon May 21 16:41:09 2018
New Revision: 260477
URL: https://gcc.gnu.org/viewcvs?rev=260477=gcc=rev
Log:
PR target/85698
* gcc.target/powerpc/vec-setup-be-long.c: Remove
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #12 from Pat Haugen ---
Author: pthaugen
Date: Mon May 21 16:34:44 2018
New Revision: 260476
URL: https://gcc.gnu.org/viewcvs?rev=260476=gcc=rev
Log:
PR target/85698
* config/rs6000/rs6000.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #11 from Pat Haugen ---
Author: pthaugen
Date: Mon May 21 16:23:20 2018
New Revision: 260475
URL: https://gcc.gnu.org/viewcvs?rev=260475=gcc=rev
Log:
PR target/85698
* config/rs6000/rs6000.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
Pat Haugen changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #9 from Pat Haugen ---
Author: pthaugen
Date: Thu May 17 16:19:16 2018
New Revision: 260329
URL: https://gcc.gnu.org/viewcvs?rev=260329=gcc=rev
Log:
PR target/85698
* config/rs6000/rs6000.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
Segher Boessenkool changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
Segher Boessenkool changed:
What|Removed |Added
CC||segher at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #7 from Pat Haugen ---
So the problem is that we're generating a stxvw4x insn to write to memory,
which corrupts the contents due to both endian behavior and element size (since
we're dealing with halfword/uint16_t elements).
Value
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #6 from Pat Haugen ---
(In reply to Richard Biener from comment #4)
> I can see what the patch does to this testcase on x86_64 - it enables BB
> vectorization of the first two loops after runrolling. I don't see anything
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #5 from Pat Haugen ---
(In reply to Richard Biener from comment #4)
>
> Can you claify whether test, ref or train inputs fail for you? I tried
> AVX256, AVX128 and plain old SSE sofar without any issue but ref takes some
> time...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #4 from Richard Biener ---
I can see what the patch does to this testcase on x86_64 - it enables BB
vectorization of the first two loops after runrolling. I don't see anything
suspicious here on x86_64 and 525.x264_r works fine for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #3 from Pat Haugen ---
(In reply to Richard Biener from comment #2)
>
> Can you help me with isolating this to a single function inside that file?
> Maybe try sticking __attribute__((optimize("no-tree-vectorize"))) on some
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
Richard Biener changed:
What|Removed |Added
Keywords||wrong-code
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |8.2
Summary|CPU2017
14 matches
Mail list logo
