public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/114985] [15 regression] internal compiler error: in discriminator_fail during stage2 Date: Thu, 16 May 2024 10:07:29 +0000 [thread overview] Message-ID: <bug-114985-4-EfgvOHs9Tl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114985-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114985 --- Comment #25 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- prange has been enabled again, after testing on x86-64 and ppc64le linux. Aarch has no space to run tests on the compile farm, and sparc bootstrap was already broken. The problem in this PR can be triggered by commenting the two new operand_check_p conditionals: diff --git a/gcc/ipa-cp.cc b/gcc/ipa-cp.cc index 09cab761822..76548f31853 100644 --- a/gcc/ipa-cp.cc +++ b/gcc/ipa-cp.cc @@ -1744,7 +1744,7 @@ ipa_value_range_from_jfunc (vrange &vr, pointer type to hold the result instead of a boolean type. Avoid trapping in the sanity check in fold_range until this is fixed. */ - || !handler.operand_check_p (vr_type, srcvr.type (), op_vr.type ()) + /*|| !handler.operand_check_p (vr_type, srcvr.type (), op_vr.type ())*/ || !handler.fold_range (op_res, vr_type, srcvr, op_vr)) op_res.set_varying (vr_type); @@ -2556,9 +2556,11 @@ propagate_vr_across_jump_function (cgraph_edge *cs, ipa_jump_func *jfunc, pointer type to hold the result instead of a boolean type. Avoid trapping in the sanity check in fold_range until this is fixed. */ + /* || !handler.operand_check_p (operand_type, src_lats->m_value_range.m_vr.type (), op_vr.type ()) + */ || !handler.fold_range (op_res, operand_type, src_lats->m_value_range.m_vr, op_vr)) op_res.set_varying (param_type); You can reproduce on x86-64 as well as ppc64le, and the problem can be seen with and without prange support enabled.
next prev parent reply other threads:[~2024-05-16 10:07 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-08 12:59 [Bug bootstrap/114985] New: " seurer at gcc dot gnu.org 2024-05-08 15:00 ` [Bug bootstrap/114985] " seurer at gcc dot gnu.org 2024-05-08 15:35 ` aldyh at gcc dot gnu.org 2024-05-08 16:34 ` seurer at gcc dot gnu.org 2024-05-08 16:34 ` aldyh at gcc dot gnu.org 2024-05-08 17:06 ` [Bug ipa/114985] " pinskia at gcc dot gnu.org 2024-05-08 20:33 ` aldyh at gcc dot gnu.org 2024-05-08 22:28 ` seurer at gcc dot gnu.org 2024-05-09 14:21 ` seurer at gcc dot gnu.org 2024-05-09 16:27 ` dje at gcc dot gnu.org 2024-05-09 21:54 ` aldyh at gcc dot gnu.org 2024-05-09 22:36 ` aldyh at gcc dot gnu.org 2024-05-10 9:27 ` aldyh at gcc dot gnu.org 2024-05-10 12:13 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-05-10 12:49 ` hubicka at gcc dot gnu.org 2024-05-10 14:38 ` segher at gcc dot gnu.org 2024-05-10 16:15 ` jamborm at gcc dot gnu.org 2024-05-11 9:47 ` aldyh at gcc dot gnu.org 2024-05-11 9:48 ` aldyh at gcc dot gnu.org 2024-05-13 14:06 ` jamborm at gcc dot gnu.org 2024-05-15 20:49 ` jamborm at gcc dot gnu.org 2024-05-15 21:06 ` amacleod at redhat dot com 2024-05-16 8:16 ` aldyh at gcc dot gnu.org 2024-05-16 9:59 ` cvs-commit at gcc dot gnu.org 2024-05-16 9:59 ` cvs-commit at gcc dot gnu.org 2024-05-16 10:07 ` aldyh at gcc dot gnu.org [this message] 2024-05-16 10:58 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-05-16 11:49 ` aldyh at gcc dot gnu.org 2024-05-16 11:58 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-05-16 12:50 ` aldyh at gcc dot gnu.org 2024-05-16 12:56 ` aldyh at gcc dot gnu.org 2024-05-16 13:04 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-05-16 14:24 ` aldyh at gcc dot gnu.org 2024-05-16 19:06 ` segher at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-114985-4-EfgvOHs9Tl@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).