diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2021-07-02 10:06:56 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2021-07-02 10:06:56 +0200 |
| commit | f7cad1a0ffe9f003ec347521dfd33f320f4c2b04 (patch) | |
| tree | e62ba6d6331f7d9fdcd16856b5df7fdcba78a6e6 /gcc/tree-ssa-loop-im.c | |
| parent | c4804ff24401733e3b470a49b8a6c9306e6cfcfa (diff) | |
| download | gcc-f7cad1a0ffe9f003ec347521dfd33f320f4c2b04.zip gcc-f7cad1a0ffe9f003ec347521dfd33f320f4c2b04.tar.gz gcc-f7cad1a0ffe9f003ec347521dfd33f320f4c2b04.tar.bz2 | |
i386: Punt on broadcasts from TImode integers [PR101286]
ix86_expand_vector_init_duplicate doesn't handle TImode -> V2TImode
or TImode -> V4TImode broadcasts, so I think we should punt on TImode
inner mode in ix86_broadcast_from_integer_constant, otherwise we ICE
in ix86_expand_vector_move when ix86_broadcast_from_integer_constant
returns non-NULL and ix86_expand_vector_init_duplicate returns false.
In theory TImode element broadcasts could be handled by some permutations,
but I'm not sure it is worth it.
2021-07-02 Jakub Jelinek <jakub@redhat.com>
PR target/101286
* config/i386/i386-expand.c (ix86_broadcast_from_integer_constant):
Return nullptr for TImode inner mode.
* gcc.target/i386/avx2-pr101286.c: New test.
Diffstat (limited to 'gcc/tree-ssa-loop-im.c')
0 files changed, 0 insertions, 0 deletions