public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115936] [15 Regression] GCN vs. ivopts: replace constant_multiple_of with aff_combination_constant_multiple_p [PR114932] Date: Mon, 15 Jul 2024 16:17:17 +0000 [thread overview] Message-ID: <bug-115936-4-N2vx1x9Fyg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115936-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115936 --- Comment #6 from Tamar Christina <tnfchris at gcc dot gnu.org> --- (In reply to Richard Biener from comment #3) > iv->step should never be a pointer type This is created by SCEV. simple_iv_with_niters in the case where no CHREC is found creates an IV with base == ev, offset == 0; however in this case EV is a POINTER_PLUS_EXPR and so the type is a pointer. it ends up creating an unusable expression. following the remaining code, it looks like this should be diff --git a/gcc/tree-scalar-evolution.cc b/gcc/tree-scalar-evolution.cc index 5aa95a2497a..abb2bad7773 100644 --- a/gcc/tree-scalar-evolution.cc +++ b/gcc/tree-scalar-evolution.cc @@ -3243,7 +3243,11 @@ simple_iv_with_niters (class loop *wrto_loop, class loop *use_loop, if (tree_does_not_contain_chrecs (ev)) { iv->base = ev; - iv->step = build_int_cst (TREE_TYPE (ev), 0); + tree ev_type = TREE_TYPE (ev); + if (POINTER_TYPE_P (ev_type)) + ev_type = sizetype; + + iv->step = build_int_cst (ev_type, 0); iv->no_overflow = true; return true; } So I think there are two bugs here. I also think the IVopts one is a bug, as it's clearly changing the type and introducing a mismatch there too. I'm regression testing both changes.
next prev parent reply other threads:[~2024-07-15 16:17 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-15 10:50 [Bug target/115936] New: " tschwinge at gcc dot gnu.org 2024-07-15 11:23 ` [Bug target/115936] " tnfchris at gcc dot gnu.org 2024-07-15 12:33 ` tnfchris at gcc dot gnu.org 2024-07-15 13:35 ` rguenth at gcc dot gnu.org 2024-07-15 13:40 ` tnfchris at gcc dot gnu.org 2024-07-15 16:17 ` tnfchris at gcc dot gnu.org 2024-07-15 16:17 ` tnfchris at gcc dot gnu.org [this message] 2024-07-17 15:22 ` [Bug tree-optimization/115936] " cvs-commit at gcc dot gnu.org 2024-07-17 15:27 ` tnfchris 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-115936-4-N2vx1x9Fyg@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).