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 middle-end/113734] [14 regression] libarchive miscompiled (fails libarchive_test_read_format_rar5_extra_field_version test) since r14-8768-g85094e2aa6dba7 Date: Mon, 12 Feb 2024 11:47:21 +0000 [thread overview] Message-ID: <bug-113734-4-ZFcCE9hQpD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113734-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113734 --- Comment #19 from Tamar Christina <tnfchris at gcc dot gnu.org> --- Ok, removing all the noise shows that this is the same issue as I saw before. The code out of the vectorizer is correct, but cunroll does a dodgee unrolling. -fdisable-tree-cunroll confirms it's the unrolling. cunroll claims: Loop 4 iterates at most 16 times. Loop 4 likely iterates at most 16 times. Analyzing # of iterations of loop 4 exit condition [1, + , 1](no_overflow) < bnd.157_285 ... ;; Guessed iterations of loop 4 is 7.347979. New upper bound 16. Making edge 23->36 impossible by redistributing probability to other edges. Original probability: 93.8% (guessed) misc.c:147:31: optimized: loop with 16 iterations completely unrolled (header execution count 2859449) Last iteration exit edge was proved true. Not peeling: number of iterations is not estimated but the i is bounded by i < 306. and VF=8. so binding loop iteration to 16 means it just cut off half the loop. so it looks like the upper bounds is wrong. Checking what we write out during loop vect.
next prev parent reply other threads:[~2024-02-12 11:47 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-03 0:49 [Bug middle-end/113734] New: " sjames at gcc dot gnu.org 2024-02-03 8:20 ` [Bug middle-end/113734] " sjames at gcc dot gnu.org 2024-02-03 11:29 ` tnfchris at gcc dot gnu.org 2024-02-03 21:50 ` pinskia at gcc dot gnu.org 2024-02-05 12:19 ` tnfchris at gcc dot gnu.org 2024-02-05 14:46 ` sjames at gcc dot gnu.org 2024-02-06 17:53 ` tnfchris at gcc dot gnu.org 2024-02-07 8:19 ` rguenth at gcc dot gnu.org 2024-02-07 9:10 ` rguenth at gcc dot gnu.org 2024-02-07 9:21 ` rguenth at gcc dot gnu.org 2024-02-07 9:25 ` tnfchris at gcc dot gnu.org 2024-02-08 11:59 ` rguenth at gcc dot gnu.org 2024-02-10 14:51 ` sjames at gcc dot gnu.org 2024-02-11 13:49 ` sjames at gcc dot gnu.org 2024-02-12 5:43 ` sjames at gcc dot gnu.org 2024-02-12 9:06 ` tnfchris at gcc dot gnu.org 2024-02-12 9:56 ` sjames at gcc dot gnu.org 2024-02-12 9:58 ` tnfchris at gcc dot gnu.org 2024-02-12 10:34 ` tnfchris at gcc dot gnu.org 2024-02-12 11:47 ` tnfchris at gcc dot gnu.org [this message] 2024-02-12 13:16 ` tnfchris at gcc dot gnu.org 2024-02-12 13:25 ` rguenth at gcc dot gnu.org 2024-02-12 13:33 ` tnfchris at gcc dot gnu.org 2024-02-12 16:07 ` tnfchris at gcc dot gnu.org 2024-02-13 4:33 ` tnfchris at gcc dot gnu.org 2024-02-13 8:24 ` [Bug tree-optimization/113734] " tnfchris at gcc dot gnu.org 2024-02-13 8:42 ` jakub at gcc dot gnu.org 2024-02-13 8:49 ` sjames at gcc dot gnu.org 2024-02-13 11:05 ` cvs-commit at gcc dot gnu.org 2024-02-13 11:06 ` 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-113734-4-ZFcCE9hQpD@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).