* [Bug target/100941] wrong code with __builtin_shufflevector() with -mavx512f
2021-06-07 5:46 [Bug target/100941] New: wrong code with __builtin_shufflevector() with -mavx512f zsojka at seznam dot cz
@ 2021-06-07 7:37 ` crazylht at gmail dot com
2021-06-07 7:39 ` zsojka at seznam dot cz
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: crazylht at gmail dot com @ 2021-06-07 7:37 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100941
Hongtao.liu <crazylht at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |crazylht at gmail dot com
--- Comment #1 from Hongtao.liu <crazylht at gmail dot com> ---
The issue seems to be related to generic part, not target specific
006t.gimple
U foo (V v, W w)
{
U D.2852;
_1 = {v, { 0, 0, 0, 0 }};
_2 = BIT_INSERT_EXPR <_1, { 0, 0, 0, 0 }, 0>; <--- why bit position is 0 but
not 256?
D.2852 = BIT_FIELD_REF <_2, 64, 0>;
return D.2852;
}
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/100941] wrong code with __builtin_shufflevector() with -mavx512f
2021-06-07 5:46 [Bug target/100941] New: wrong code with __builtin_shufflevector() with -mavx512f zsojka at seznam dot cz
2021-06-07 7:37 ` [Bug target/100941] " crazylht at gmail dot com
@ 2021-06-07 7:39 ` zsojka at seznam dot cz
2021-06-07 7:58 ` zsojka at seznam dot cz
2021-06-07 8:50 ` jakub at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: zsojka at seznam dot cz @ 2021-06-07 7:39 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100941
--- Comment #2 from Zdenek Sojka <zsojka at seznam dot cz> ---
(In reply to Hongtao.liu from comment #1)
> The issue seems to be related to generic part, not target specific
>
> 006t.gimple
>
> U foo (V v, W w)
> {
> U D.2852;
>
> _1 = {v, { 0, 0, 0, 0 }};
> _2 = BIT_INSERT_EXPR <_1, { 0, 0, 0, 0 }, 0>; <--- why bit position is 0
> but not 256?
> D.2852 = BIT_FIELD_REF <_2, 64, 0>;
> return D.2852;
> }
Thank you for having a look.
I will re-check with the PR100887 fix applied.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/100941] wrong code with __builtin_shufflevector() with -mavx512f
2021-06-07 5:46 [Bug target/100941] New: wrong code with __builtin_shufflevector() with -mavx512f zsojka at seznam dot cz
2021-06-07 7:37 ` [Bug target/100941] " crazylht at gmail dot com
2021-06-07 7:39 ` zsojka at seznam dot cz
@ 2021-06-07 7:58 ` zsojka at seznam dot cz
2021-06-07 8:50 ` jakub at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: zsojka at seznam dot cz @ 2021-06-07 7:58 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100941
--- Comment #3 from Zdenek Sojka <zsojka at seznam dot cz> ---
(In reply to Zdenek Sojka from comment #2)
> (In reply to Hongtao.liu from comment #1)
> > The issue seems to be related to generic part, not target specific
> >
> > 006t.gimple
> >
> > U foo (V v, W w)
> > {
> > U D.2852;
> >
> > _1 = {v, { 0, 0, 0, 0 }};
> > _2 = BIT_INSERT_EXPR <_1, { 0, 0, 0, 0 }, 0>; <--- why bit position is 0
> > but not 256?
> > D.2852 = BIT_FIELD_REF <_2, 64, 0>;
> > return D.2852;
> > }
>
> Thank you for having a look.
> I will re-check with the PR100887 fix applied.
No longer fails with r12-1256 , so perhaps fixed by the other PR100887 fix.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/100941] wrong code with __builtin_shufflevector() with -mavx512f
2021-06-07 5:46 [Bug target/100941] New: wrong code with __builtin_shufflevector() with -mavx512f zsojka at seznam dot cz
` (2 preceding siblings ...)
2021-06-07 7:58 ` zsojka at seznam dot cz
@ 2021-06-07 8:50 ` jakub at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: jakub at gcc dot gnu.org @ 2021-06-07 8:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100941
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
CC| |jakub at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yes, that fixed it.
^ permalink raw reply [flat|nested] 5+ messages in thread