[Bug tree-optimization/109583] [13/14 Regression] ICE in related_vector_mode, at stor-layout.cc:537 since r14-22-g2349e69125335d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109583 Jakub Jelinek changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #5 from Jakub Jelinek --- Yes.
[Bug tree-optimization/109583] [13/14 Regression] ICE in related_vector_mode, at stor-layout.cc:537 since r14-22-g2349e69125335d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109583 --- Comment #4 from Martin Liška --- Fixed now?
[Bug tree-optimization/109583] [13/14 Regression] ICE in related_vector_mode, at stor-layout.cc:537 since r14-22-g2349e69125335d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109583 --- Comment #3 from CVS Commits --- The releases/gcc-13 branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:9b6bf076c11cba0f9ccdace63e8b4044b1a858ea commit r13-7234-g9b6bf076c11cba0f9ccdace63e8b4044b1a858ea Author: Jakub Jelinek Date: Sat Apr 22 10:24:29 2023 +0200 match.pd: Fix fneg/fadd optimization [PR109583] The following testcase ICEs on x86, foo function since my r14-22 improvement, but bar already since r13-4122. The problem is the same, in the if expression related_vector_mode is called and that starts with gcc_assert (VECTOR_MODE_P (vector_mode)); but nothing in the fneg/fadd match.pd pattern actually checks if the VEC_PERM type has VECTOR_MODE_P (vec_mode). In this case it has BLKmode and so it ICEs. The following patch makes sure we don't ICE on it. 2023-04-22 Jakub Jelinek PR tree-optimization/109583 * match.pd (fneg/fadd simplify): Don't call related_vector_mode if vec_mode is not VECTOR_MODE_P. * gcc.dg/pr109583.c: New test. (cherry picked from commit c58c0771b7a3dbd2a00cd4b6ca2301d74b6cd4e2)
[Bug tree-optimization/109583] [13/14 Regression] ICE in related_vector_mode, at stor-layout.cc:537 since r14-22-g2349e69125335d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109583 --- Comment #2 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:c58c0771b7a3dbd2a00cd4b6ca2301d74b6cd4e2 commit r14-163-gc58c0771b7a3dbd2a00cd4b6ca2301d74b6cd4e2 Author: Jakub Jelinek Date: Sat Apr 22 10:24:29 2023 +0200 match.pd: Fix fneg/fadd optimization [PR109583] The following testcase ICEs on x86, foo function since my r14-22 improvement, but bar already since r13-4122. The problem is the same, in the if expression related_vector_mode is called and that starts with gcc_assert (VECTOR_MODE_P (vector_mode)); but nothing in the fneg/fadd match.pd pattern actually checks if the VEC_PERM type has VECTOR_MODE_P (vec_mode). In this case it has BLKmode and so it ICEs. The following patch makes sure we don't ICE on it. 2023-04-22 Jakub Jelinek PR tree-optimization/109583 * match.pd (fneg/fadd simplify): Don't call related_vector_mode if vec_mode is not VECTOR_MODE_P. * gcc.dg/pr109583.c: New test.
[Bug tree-optimization/109583] [13/14 Regression] ICE in related_vector_mode, at stor-layout.cc:537 since r14-22-g2349e69125335d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109583 Jakub Jelinek changed: What|Removed |Added Target Milestone|14.0|13.0
[Bug tree-optimization/109583] [13/14 Regression] ICE in related_vector_mode, at stor-layout.cc:537 since r14-22-g2349e69125335d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109583
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Summary|[14 Regression] ICE in |[13/14 Regression] ICE in
|related_vector_mode, at |related_vector_mode, at
|stor-layout.cc:537 since|stor-layout.cc:537 since
|r14-22-g2349e69125335d |r14-22-g2349e69125335d
Status|NEW |ASSIGNED
--- Comment #1 from Jakub Jelinek ---
Change it to:
typedef float v8sf __attribute__((vector_size (8 * sizeof (float;
typedef int v8si __attribute__((vector_size (8 * sizeof (int;
v8sf
foo (v8sf x, v8sf y)
{
v8sf tem0 = x + y;
v8sf tem1 = x - y;
return __builtin_shuffle (tem0, tem1, (v8si) { 0, 9, 2, 11, 4, 13, 6, 15 });
}
and it started to ICE already in r13-4122-g1bc7efa948f751 (again -O1 -mno-avx
-Wno-psabi).
