[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2024-02-22 Thread patrick at rivosinc dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 Patrick O'Neill changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2024-01-25 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #23 from GCC Commits --- The master branch has been updated by Robin Dapp : https://gcc.gnu.org/g:660e17f00658b68115282e6de38243e3c6cc1ee2 commit r14-8430-g660e17f00658b68115282e6de38243e3c6cc1ee2 Author: Robin Dapp Date: Mon

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2024-01-10 Thread rdapp at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #22 from Robin Dapp --- Yes, going to the thread soon.

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2024-01-10 Thread juzhe.zhong at rivai dot ai via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #21 from JuzheZhong --- Hi, Robin. Will you continue on this issue ? I have seen a benchmark has the same ICE. Thanks.

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-14 Thread juzhe.zhong at rivai dot ai via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #20 from JuzheZhong --- Hi, Andrew. I saw this code which seems to cause infinite loop: if (TREE_CODE (arg1) == VECTOR_CST && TREE_CODE (arg2) == VECTOR_CST && known_eq (TYPE_VECTOR_SUBPARTS (TREE_TYPE (arg1)),

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-14 Thread juzhe.zhong at rivai dot ai via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #19 from JuzheZhong --- OK. I think we can't reproduce same issue on ARM SVE since VNx8HI is poly size [4,4] SI mode. Wheras, RVV with zvl256b is [8,8] SImode that ARM SVE never has such size scalable SI mode. I guess Robin is

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-14 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #18 from Andrew Pinski --- (In reply to JuzheZhong from comment #17) > Ok. Thanks for confirm it. > enough ? If it can fix our RISC-V ICE. No, that is actually the wrong place to fix it. This was just to see if that would fix the

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-14 Thread juzhe.zhong at rivai dot ai via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #17 from JuzheZhong --- Ok. Thanks for confirm it. Hi, Andrew. Is this following: ``` /* x & 0 -> 0 */ (simplify (bit_and @0 integer_zerop@1) @1) ``` to ``` /* x & 0 -> 0 */ (simplify (bit_and:c @0 integer_zerop@1) @1) ```

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-14 Thread patrick at rivosinc dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 Patrick O'Neill changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-14 Thread patrick at rivosinc dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 Patrick O'Neill changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-14 Thread juzhe.zhong at rivai dot ai via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #14 from JuzheZhong --- Oh, I just take a look again. It seems that the issue is fixed on the trunk ? Hi, Patrick. https://godbolt.org/z/f1rnsYxf9 Could you confirm it ? If it is fixed, could you send a patch with the test ?

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-14 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #13 from Andrew Pinski --- (In reply to JuzheZhong from comment #12) > Thanks Andrew. > > Will you send the patch to fix this ICE for RISC-V ? I doubt I will have time to work on it really. I have not figured out just yet to

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-14 Thread juzhe.zhong at rivai dot ai via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #12 from JuzheZhong --- Thanks Andrew. Will you send the patch to fix this ICE for RISC-V ? It's important for risc-v since it is ICE bug that we should land it in GCC-14 release.

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-12 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #11 from Andrew Pinski --- (In reply to Andrew Pinski from comment #9) > The real fix will be to const_binop . > Right now const_binop only handles a few cases for VLA's VECTOR_CST and it > seems like it really only handles +, -,

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-12 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-12 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #9 from Andrew Pinski --- The real fix will be to const_binop . Right now const_binop only handles a few cases for VLA's VECTOR_CST and it seems like it really only handles +, -, and sometimes * and sometimes left shit .

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-12 Thread rdapp at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #8 from Robin Dapp --- Yes, can confirm that this helps.

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-12 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #7 from Andrew Pinski --- Can you modify: ``` /* x & 0 -> 0 */ (simplify (bit_and @0 integer_zerop@1) @1) ``` to ``` /* x & 0 -> 0 */ (simplify (bit_and:c @0 integer_zerop@1) @1) ``` That in theory should not matter but I

[Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1

2023-12-12 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971 --- Comment #6 from Andrew Pinski --- Looks like `{ 0, ... } & { -9, -8, -7, ... }` is not simplifying down to just `{ 0, ...}`