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 13:33:30 +0000 [thread overview] Message-ID: <bug-113734-4-yAIYAuuHmS@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 #22 from Tamar Christina <tnfchris at gcc dot gnu.org> --- (In reply to Richard Biener from comment #21) > loop->nb_iterations_upper_bound exactly is an upper bound on the number of > latch executions, so maybe I'm missing the point here. When we update it it > as > well has to reflect an upper bound on that, whether the last exit (the one > before the latch) is the IV exit or a vectorized early exit. Yes, but the issue here is that the bounds limit is coming from an exit other than the one being chosen as the IV exit. So the latch iterates X times not X - 1. > > But yes, if the last exit is an early one that last iteration might be > partial > (so we drop the -1), but that's what we already do? I don't see where. This code all seems to remove -1 from the iteration count and assuming the latch iteration count + 1 == nbounds. I don't really think this is about partial loops at all. Change parse_tables_n >>= 9; parse_tables_n += 11; to parse_tables_n >>= 9; parse_tables_n += 10; then loop->nb_iterations_upper_bound is 136 and there is no partial iterations here. You do 17 full vector iterations with no residuals.
next prev parent reply other threads:[~2024-02-12 13:33 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 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 [this message] 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-yAIYAuuHmS@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).