* [Bug target/113115] ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler
2023-12-22 14:13 [Bug target/113115] New: ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler fkastl at suse dot cz
@ 2024-01-03 12:33 ` mjires at suse dot cz
2024-01-03 21:44 ` [Bug target/113115] [14 Regression] ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler from r14-3592-g9ea1248604d7b6 pinskia at gcc dot gnu.org
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: mjires at suse dot cz @ 2024-01-03 12:33 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113115
Michal Jireš <mjires at suse dot cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeevitha at gcc dot gnu.org,
| |mjires at suse dot cz
--- Comment #1 from Michal Jireš <mjires at suse dot cz> ---
Bisected to r14-3592-g9ea1248604d7b6.
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug target/113115] [14 Regression] ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler from r14-3592-g9ea1248604d7b6
2023-12-22 14:13 [Bug target/113115] New: ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler fkastl at suse dot cz
2024-01-03 12:33 ` [Bug target/113115] " mjires at suse dot cz
@ 2024-01-03 21:44 ` pinskia at gcc dot gnu.org
2024-01-08 13:57 ` rguenth at gcc dot gnu.org
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: pinskia at gcc dot gnu.org @ 2024-01-03 21:44 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113115
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |14.0
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug target/113115] [14 Regression] ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler from r14-3592-g9ea1248604d7b6
2023-12-22 14:13 [Bug target/113115] New: ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler fkastl at suse dot cz
2024-01-03 12:33 ` [Bug target/113115] " mjires at suse dot cz
2024-01-03 21:44 ` [Bug target/113115] [14 Regression] ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler from r14-3592-g9ea1248604d7b6 pinskia at gcc dot gnu.org
@ 2024-01-08 13:57 ` rguenth at gcc dot gnu.org
2024-01-08 20:50 ` bergner at gcc dot gnu.org
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: rguenth at gcc dot gnu.org @ 2024-01-08 13:57 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113115
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2024-01-08
Priority|P3 |P1
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed by bisection.
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug target/113115] [14 Regression] ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler from r14-3592-g9ea1248604d7b6
2023-12-22 14:13 [Bug target/113115] New: ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler fkastl at suse dot cz
` (2 preceding siblings ...)
2024-01-08 13:57 ` rguenth at gcc dot gnu.org
@ 2024-01-08 20:50 ` bergner at gcc dot gnu.org
2024-01-09 2:07 ` linkw at gcc dot gnu.org
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: bergner at gcc dot gnu.org @ 2024-01-08 20:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113115
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bergner at gcc dot gnu.org,
| |dje at gcc dot gnu.org,
| |linkw at gcc dot gnu.org,
| |segher at gcc dot gnu.org
--- Comment #3 from Peter Bergner <bergner at gcc dot gnu.org> ---
Ke Wen, is this just a duplicate of PR109987 and PR103627? I know it was
bisected to Jeevitha's commit, but it seems more like her commit exposed the
same latent issue as those other PRs, rather than causing it. Your thoughts?
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug target/113115] [14 Regression] ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler from r14-3592-g9ea1248604d7b6
2023-12-22 14:13 [Bug target/113115] New: ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler fkastl at suse dot cz
` (3 preceding siblings ...)
2024-01-08 20:50 ` bergner at gcc dot gnu.org
@ 2024-01-09 2:07 ` linkw at gcc dot gnu.org
2024-01-09 5:08 ` bergner at gcc dot gnu.org
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: linkw at gcc dot gnu.org @ 2024-01-09 2:07 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113115
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #4 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #3)
> Ke Wen, is this just a duplicate of PR109987 and PR103627? I know it was
> bisected to Jeevitha's commit, but it seems more like her commit exposed the
> same latent issue as those other PRs, rather than causing it. Your thoughts?
Yes, I agree it's duplicated of PR109987, Jeevitha's commit just exposed this
known issue, since we are in stage 3, I wonder if we can go with power9-vector
guarding first
(https://gcc.gnu.org/pipermail/gcc-patches/2021-December/587310.html) since
power9-vector still exists in this release, and we can try to remove these
workaround options in next release. (Sorry that I missed to follow up the
power{8,9}-vector removal)
*** This bug has been marked as a duplicate of bug 109987 ***
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug target/113115] [14 Regression] ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler from r14-3592-g9ea1248604d7b6
2023-12-22 14:13 [Bug target/113115] New: ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler fkastl at suse dot cz
` (4 preceding siblings ...)
2024-01-09 2:07 ` linkw at gcc dot gnu.org
@ 2024-01-09 5:08 ` bergner at gcc dot gnu.org
2024-01-09 7:54 ` segher at gcc dot gnu.org
2024-01-10 8:12 ` linkw at gcc dot gnu.org
7 siblings, 0 replies; 9+ messages in thread
From: bergner at gcc dot gnu.org @ 2024-01-09 5:08 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113115
--- Comment #5 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Kewen Lin from comment #4)
> Yes, I agree it's duplicated of PR109987, Jeevitha's commit just exposed
> this known issue, since we are in stage 3, I wonder if we can go with
> power9-vector guarding first
> (https://gcc.gnu.org/pipermail/gcc-patches/2021-December/587310.html) since
> power9-vector still exists in this release, and we can try to remove these
> workaround options in next release. (Sorry that I missed to follow up the
> power{8,9}-vector removal)
I really dislike the -mpower{8,9}-vector options, but maybe it's too late to
remove them for this release? I'm not sure how involved/invasive that patch
would be. Segher, do you have a preference on remove them now or use the
workaround above and remove in the next release?
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug target/113115] [14 Regression] ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler from r14-3592-g9ea1248604d7b6
2023-12-22 14:13 [Bug target/113115] New: ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler fkastl at suse dot cz
` (5 preceding siblings ...)
2024-01-09 5:08 ` bergner at gcc dot gnu.org
@ 2024-01-09 7:54 ` segher at gcc dot gnu.org
2024-01-10 8:12 ` linkw at gcc dot gnu.org
7 siblings, 0 replies; 9+ messages in thread
From: segher at gcc dot gnu.org @ 2024-01-09 7:54 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113115
--- Comment #6 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Using -mpower9-vector while not having -mcpu=power9 (or later) is wrong, and
should
not work. Using -mno-power9-vector is just weird.
If we can neuter the -mpower9-vector (etc.) options now, that would be good.
But
there are some complications with the testsuite at least?
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug target/113115] [14 Regression] ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler from r14-3592-g9ea1248604d7b6
2023-12-22 14:13 [Bug target/113115] New: ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler fkastl at suse dot cz
` (6 preceding siblings ...)
2024-01-09 7:54 ` segher at gcc dot gnu.org
@ 2024-01-10 8:12 ` linkw at gcc dot gnu.org
7 siblings, 0 replies; 9+ messages in thread
From: linkw at gcc dot gnu.org @ 2024-01-10 8:12 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113115
--- Comment #7 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #5)
> I really dislike the -mpower{8,9}-vector options, but maybe it's too late to
> remove them for this release? I'm not sure how involved/invasive that patch
> would be. Segher, do you have a preference on remove them now or use the
> workaround above and remove in the next release?
(In reply to Segher Boessenkool from comment #6)
> Using -mpower9-vector while not having -mcpu=power9 (or later) is wrong, and
> should
> not work. Using -mno-power9-vector is just weird.
>
> If we can neuter the -mpower9-vector (etc.) options now, that would be good.
> But
> there are some complications with the testsuite at least?
OK, it sounds that it's still acceptable to adjust this at this time point, so
I'm working on a patch to evaluate its impact, will post it after full testing.
^ permalink raw reply [flat|nested] 9+ messages in thread