https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
--- Comment #18 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:0f7945417f913c85bd556904c0c4e7bf77793488
commit r14-8498-g0f7945417f913c85bd556904c0c4e7bf77793488
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
--- Comment #17 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:96bc048d78f804bac0fa7b2ca3b6dd3a04c68217
commit r14-8497-g96bc048d78f804bac0fa7b2ca3b6dd3a04c68217
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
--- Comment #16 from Richard Biener ---
typedef double __attribute__ ((vector_size (16))) vec;
void
test (void)
{
register vec a asm("xmm1"), b asm("xmm2"), c asm("xmm3");
for (int i = 0; i < 2; i++)
c[i] = a[i] < b[i] ? 0.1 : 0.2;
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
--- Comment #15 from Richard Biener ---
(In reply to Jakub Jelinek from comment #11)
> I think it is most important we don't ICE and generate correct code. I
> doubt this is used too much in real-world code, otherwise it would have been
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
--- Comment #14 from Xi Ruoyao ---
(In reply to Jakub Jelinek from comment #13)
> (In reply to Xi Ruoyao from comment #12)
> > (In reply to Jakub Jelinek from comment #11)
> > > I think it is most important we don't ICE and generate correct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
--- Comment #13 from Jakub Jelinek ---
(In reply to Xi Ruoyao from comment #12)
> (In reply to Jakub Jelinek from comment #11)
> > I think it is most important we don't ICE and generate correct code. I
> > doubt this is used too much in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
--- Comment #12 from Xi Ruoyao ---
(In reply to Jakub Jelinek from comment #11)
> I think it is most important we don't ICE and generate correct code. I
> doubt this is used too much in real-world code, otherwise it would have been
> reported
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
--- Comment #11 from Jakub Jelinek ---
I think it is most important we don't ICE and generate correct code. I doubt
this is used too much in real-world code, otherwise it would have been reported
years ago, so how efficient it will be is less
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
--- Comment #10 from Richard Biener ---
(In reply to Jakub Jelinek from comment #8)
> Guess for an rvalue (if even that crashes) we want to expand it to some
> permutation or whole vector shift which moves the indexed elements first and
> then
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
--- Comment #8 from Jakub Jelinek ---
Guess for an rvalue (if even that crashes) we want to expand it to some
permutation or whole vector shift which moves the indexed elements first and
then extract it, for lvalue we need to insert it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
Andrew Pinski changed:
What|Removed |Added
CC||chenglulu at loongson dot cn
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
--- Comment #6 from Andrew Pinski ---
The assert by the way:
```
if (!MEM_P (to_rtx))
{
/* We can get constant negative offsets into arrays with broken
user code. Translate this to a trap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
--- Comment #5 from Andrew Pinski ---
Here is a "valid" x86_64 testcase:
```
typedef float __attribute__ ((vector_size (64))) vec;
register vec a asm("zmm2"), b asm("zmm0"), c asm("zmm1");
void
test (void)
{
for (int i = 0; i < 8; i++)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
Jakub Jelinek changed:
What|Removed |Added
Summary|ICE with vectors in named |[11/12/13/14 Regression]
15 matches
Mail list logo
