https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|11.4|11.5
--- Comment #15 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
Richard Biener changed:
What|Removed |Added
Target Milestone|11.3|11.4
--- Comment #14 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
Richard Biener changed:
What|Removed |Added
Target Milestone|11.2|11.3
--- Comment #13 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|11.0|11.2
--- Comment #12 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
--- Comment #11 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:b80fefd626460fb8924248622ba59dd56246703e
commit r11-7115-gb80fefd626460fb8924248622ba59dd56246703e
Author: liuhongt
Date: Thu Jan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
--- Comment #10 from Hongtao.liu ---
(In reply to Hongtao.liu from comment #9)
> > .L3:
> > vmovupd (%rcx,%rax), %xmm3
> > vmovupd (%rsi,%rax), %xmm4
> > vinsertf128 $0x1, 16(%rcx,%rax), %ymm3, %ymm0
> > vinsertf128 $0x1,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
--- Comment #9 from Hongtao.liu ---
> .L3:
> vmovupd (%rcx,%rax), %xmm3
> vmovupd (%rsi,%rax), %xmm4
> vinsertf128 $0x1, 16(%rcx,%rax), %ymm3, %ymm0
> vinsertf128 $0x1, 16(%rsi,%rax), %ymm4, %ymm2
> vmovupd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
--- Comment #8 from H.J. Lu ---
-mtune=generic -mavx2 -mfma generates awful code:
[hjl@gnu-skx-1 tmp]$ cat y.c
#define DATA_ENTRIES 256
extern double *a, *x, *y, *z;
void work()
{
int i;
for (i = 0; i < DATA_ENTRIES; ++i)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
--- Comment #7 from H.J. Lu ---
GCC 11 will be system GCC 2 years from now. The current processors in 2020
will be 2 years old.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
--- Comment #6 from H.J. Lu ---
(In reply to Richard Biener from comment #3)
> Hmm, but rep movsb is only fast starting with Zen3 IIRC.
Are MOVSL/MOVSQ faster than MOVSB on Zen1/Zen2?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
--- Comment #5 from Jan Hubicka ---
> Hmm, but rep movsb is only fast starting with Zen3 IIRC.
Yep, I think we need to support zen1/2 well. I think we can regress
buldozers somehwat though.
Honza
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
--- Comment #4 from Jan Hubicka ---
> > What kind of updates you propose?
>
> For one thing, memcpy/memset should be expanded to REP MOVSB/STOSB, never
> MOVSL/MOVSQ.
For core cost tables we use:
/* core_cost should produce code tuned for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
--- Comment #3 from Richard Biener ---
Hmm, but rep movsb is only fast starting with Zen3 IIRC.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
H.J. Lu changed:
What|Removed |Added
Ever confirmed|0 |1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98172
Jan Hubicka changed:
What|Removed |Added
CC||hubicka at gcc dot gnu.org
--- Comment #1
15 matches
Mail list logo
