[Bug target/111753] [14 Regression] ICE: in extract_constrain_insn, at recog.cc:2692 insn does not satisfy its constraints: {*movsf_internal} with -O2 -mavx512bw -fno-tree-ter starting with r14-4499

2023-10-22 Thread sjames at gcc dot gnu.org via Gcc-bugs 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111753

Sam James  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED
 CC||sjames at gcc dot gnu.org

--- Comment #7 from Sam James  ---
Let's close then

[Bug target/111753] [14 Regression] ICE: in extract_constrain_insn, at recog.cc:2692 insn does not satisfy its constraints: {*movsf_internal} with -O2 -mavx512bw -fno-tree-ter starting with r14-4499

2023-10-22 Thread haochen.jiang at intel dot com via Gcc-bugs 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111753

--- Comment #6 from Haochen Jiang  ---
Fixed on trunk.

[Bug target/111753] [14 Regression] ICE: in extract_constrain_insn, at recog.cc:2692 insn does not satisfy its constraints: {*movsf_internal} with -O2 -mavx512bw -fno-tree-ter starting with r14-4499

2023-10-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111753

--- Comment #5 from CVS Commits  ---
The master branch has been updated by Haochen Jiang :

https://gcc.gnu.org/g:1df490edd48042b07aa780b088148a9118cbcb46

commit r14-4841-g1df490edd48042b07aa780b088148a9118cbcb46
Author: Haochen Jiang 
Date:   Thu Oct 19 16:39:16 2023 +0800

i386: Prevent splitting to xmm16+ when !TARGET_AVX512VL

Currently, there will be a chance in split to use x/ymm16+ w/o AVX512VL,
which finally leads to an ICE as pr111753 does.

This patch aims to fix that.

gcc/ChangeLog:

PR target/111753
* config/i386/i386.cc (ix86_standard_x87sse_constant_load_p):
Do not split to xmm16+ when !TARGET_AVX512VL.

gcc/testsuite/ChangeLog:

PR target/111753
* gcc.target/i386/pr111753.c: New test.

[Bug target/111753] [14 Regression] ICE: in extract_constrain_insn, at recog.cc:2692 insn does not satisfy its constraints: {*movsf_internal} with -O2 -mavx512bw -fno-tree-ter starting with r14-4499

2023-10-20 Thread haochen.jiang at intel dot com via Gcc-bugs 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111753

--- Comment #4 from Haochen Jiang  ---
Proposed patch:

https://gcc.gnu.org/pipermail/gcc-patches/2023-October/633677.html

[Bug target/111753] [14 Regression] ICE: in extract_constrain_insn, at recog.cc:2692 insn does not satisfy its constraints: {*movsf_internal} with -O2 -mavx512bw -fno-tree-ter starting with r14-4499

2023-10-18 Thread haochen.jiang at intel dot com via Gcc-bugs 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111753

--- Comment #3 from Haochen Jiang  ---
It seems like caused by I changed the behavior when trying to use x/ymm16+ w/o
avx512vl specified.

Working on a solution for that.

[Bug target/111753] [14 Regression] ICE: in extract_constrain_insn, at recog.cc:2692 insn does not satisfy its constraints: {*movsf_internal} with -O2 -mavx512bw -fno-tree-ter starting with r14-4499

2023-10-18 Thread jakub at gcc dot gnu.org via Gcc-bugs 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111753

Jakub Jelinek  changed:

   What|Removed |Added

Summary|[14 Regression] ICE: in |[14 Regression] ICE: in
   |extract_constrain_insn, at  |extract_constrain_insn, at
   |recog.cc:2692 insn does not |recog.cc:2692 insn does not
   |satisfy its constraints:|satisfy its constraints:
   |{*movsf_internal} with -O2  |{*movsf_internal} with -O2
   |-mavx512bw -fno-tree-ter|-mavx512bw -fno-tree-ter
   ||starting with r14-4499
 CC||haochen.jiang at intel dot com,
   ||jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek  ---
Started with r14-4499-gc1eef66baa8dde706d7ea6921648e6016dc7c93d

[Bug target/111753] [14 Regression] ICE: in extract_constrain_insn, at recog.cc:2692 insn does not satisfy its constraints: {*movsf_internal} with -O2 -mavx512bw -fno-tree-ter

2023-10-17 Thread rguenth at gcc dot gnu.org via Gcc-bugs 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111753

Richard Biener  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Last reconfirmed||2023-10-17
 Status|UNCONFIRMED |NEW
   Priority|P3  |P1

--- Comment #1 from Richard Biener  ---
Confirmed.