public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113703] ivopts miscompiles loop Date: Tue, 06 Feb 2024 11:33:32 +0000 [thread overview] Message-ID: <bug-113703-4-pDHTLHiXOu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113703-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113703 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- It's going wrong in iv_elimination_compare_lt which tries to exactly handle this kind of loop: We aim to handle the following situation: sometype *base, *p; int a, b, i; i = a; p = p_0 = base + a; do { bla (*p); p++; i++; } while (i < b); Here, the number of iterations of the loop is (a + 1 > b) ? 0 : b - a - 1. We aim to optimize this to p = p_0 = base + a; do { bla (*p); p++; } while (p < p_0 - a + b); This preserves the correctness, since the pointer arithmetics does not overflow. More precisely: 1) if a + 1 <= b, then p_0 - a + b is the final value of p, hence there is no overflow in computing it or the values of p. 2) if a + 1 > b, then we need to verify that the expression p_0 - a does not overflow. To prove this, we use the fact that p_0 = base + a. there's either a hole in that logic or the implementation is off. /* Finally, check that CAND->IV->BASE - CAND->IV->STEP * A does not overflow. */ offset = fold_build2 (MULT_EXPR, TREE_TYPE (cand->iv->step), cand->iv->step, fold_convert (TREE_TYPE (cand->iv->step), a)); if (!difference_cannot_overflow_p (data, cand->iv->base, offset)) return false; where 'A' is 'i', CAND->IV->BASE is 'p + i' and CAND->IV->STEP is 1 as 'sizetype'. That just checks that (p + i) - i doesn't overflow. Somehow it misses to prove p + b doesn't overflow since we end up with p' < (p + i) + (n - i) aka p' < p + n.
prev parent reply other threads:[~2024-02-06 11:33 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-01 11:17 [Bug tree-optimization/113703] New: " kristerw at gcc dot gnu.org 2024-02-01 14:12 ` [Bug tree-optimization/113703] " rguenth at gcc dot gnu.org 2024-02-01 15:01 ` kristerw at gcc dot gnu.org 2024-02-01 15:30 ` kristerw at gcc dot gnu.org 2024-02-05 10:04 ` rguenth at gcc dot gnu.org 2024-02-06 11:33 ` rguenth at gcc dot gnu.org [this message]
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-113703-4-pDHTLHiXOu@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).