public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109639] [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283 since r14-249-g3c9372dfee0bb8 Date: Thu, 27 Apr 2023 05:45:48 +0000 [thread overview] Message-ID: <bug-109639-4-Hm5Is5LXoJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109639-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109639 Sam James <sjames at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[14 regression] Internal |[14 regression] Internal |compiler error: tree check: |compiler error: tree check: |expected integer_cst, have |expected integer_cst, have |addr_expr in to_wide, at |addr_expr in to_wide, at |tree.h:6283 |tree.h:6283 since | |r14-249-g3c9372dfee0bb8 Keywords|needs-bisection, | |needs-reduction | CC| |aldyh at gcc dot gnu.org --- Comment #7 from Sam James <sjames at gcc dot gnu.org> --- 3c9372dfee0bb893b99dd28658c98d397cda5b49 is the first bad commit commit 3c9372dfee0bb893b99dd28658c98d397cda5b49 Author: Aldy Hernandez <aldyh@redhat.com> Date: Mon Nov 21 00:54:21 2022 +0100 Remove deprecated range_fold_{unary,binary}_expr uses from ipa-*. gcc/ChangeLog: * ipa-cp.cc (ipa_vr_operation_and_type_effects): Convert to ranger API. (ipa_value_range_from_jfunc): Same. (propagate_vr_across_jump_function): Same. * ipa-fnsummary.cc (evaluate_conditions_for_known_args): Same. * ipa-prop.cc (ipa_compute_jump_functions_for_edge): Same. * vr-values.cc (bounds_of_var_in_loop): Same. gcc/ipa-cp.cc | 28 ++++++++++++++++++++++------ gcc/ipa-fnsummary.cc | 45 +++++++++++++++++++++++++++++---------------- gcc/ipa-prop.cc | 5 ++--- gcc/vr-values.cc | 6 ++++-- 4 files changed, 57 insertions(+), 27 deletions(-) bisect found first bad commit i.e. r14-249-g3c9372dfee0bb8
next prev parent reply other threads:[~2023-04-27 5:45 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-26 23:15 [Bug tree-optimization/109639] New: [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283 sjames at gcc dot gnu.org 2023-04-27 0:34 ` [Bug tree-optimization/109639] " sjames at gcc dot gnu.org 2023-04-27 2:56 ` sjames at gcc dot gnu.org 2023-04-27 3:00 ` pinskia at gcc dot gnu.org 2023-04-27 3:01 ` pinskia at gcc dot gnu.org 2023-04-27 4:22 ` pinskia at gcc dot gnu.org 2023-04-27 4:22 ` pinskia at gcc dot gnu.org 2023-04-27 5:13 ` sjames at gcc dot gnu.org 2023-04-27 5:14 ` sjames at gcc dot gnu.org 2023-04-27 5:45 ` sjames at gcc dot gnu.org [this message] 2023-04-27 6:13 ` [Bug tree-optimization/109639] [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283 since r14-249-g3c9372dfee0bb8 pinskia at gcc dot gnu.org 2023-04-27 6:14 ` pinskia at gcc dot gnu.org 2023-04-27 6:43 ` rguenth at gcc dot gnu.org 2023-04-27 9:01 ` [Bug ipa/109639] " aldyh at gcc dot gnu.org 2023-04-27 9:08 ` aldyh at gcc dot gnu.org 2023-04-27 9:11 ` aldyh at gcc dot gnu.org 2023-04-27 10:11 ` aldyh at gcc dot gnu.org 2023-04-27 11:59 ` cvs-commit at gcc dot gnu.org 2023-04-27 12:00 ` aldyh 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-109639-4-Hm5Is5LXoJ@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).