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/114403] [14 regression] LLVM miscompiled with -O3 -march=znver2 -fno-vect-cost-model since r14-6822-g01f4251b8775c8 Date: Fri, 22 Mar 2024 13:50:12 +0000 [thread overview] Message-ID: <bug-114403-4-F9XPG01Dbr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114403-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114403 --- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> --- There are a few vectorizations in the dumps but only one early-exit where we vectorize <bb 2> [local count: 102053600]: first$I_39 = MEM[(struct value_op_iterator *)&first]; last$I_40 = MEM[(struct value_op_iterator *)&last]; seed_15 = llvm::hashing::detail::get_execution_seed (); if (first$I_39 != last$I_40) goto <bb 22>; [94.50%] <bb 22> [local count: 96440652]: <bb 3> [local count: 179229733]: # buffer_ptr_22 = PHI <_20(24), &buffer(22)> # first$I_24 = PHI <_29(24), first$I_39(22)> # ivtmp_226 = PHI <ivtmp_216(24), 9(22)> _20 = buffer_ptr_22 + 8; ivtmp_216 = ivtmp_226 - 1; if (ivtmp_216 == 0) goto <bb 5>; [51.12%] else goto <bb 4>; [48.88%] <bb 4> [local count: 87607493]: _30 = MEM[(const struct Use *)first$I_24].Val; _35 = (unsigned long) _30; MEM <unsigned long> [(char * {ref-all})buffer_ptr_22] = _35; _29 = first$I_24 + 32; if (_29 != last$I_40) goto <bb 24>; [94.50%] else goto <bb 5>; [5.50%] <bb 24> [local count: 82789081]: goto <bb 3>; [100.00%] <bb 5> [local count: 96440652]: # buffer_ptr_248 = PHI <_20(4), buffer_ptr_22(3)> # first$I_175 = PHI <last$I_40(4), first$I_24(3)> if (last$I_40 == first$I_175) ... as far as I can see that's a non-peeled case and from what I see it looks OK how we process that.
next prev parent reply other threads:[~2024-03-22 13:50 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-20 10:44 [Bug tree-optimization/114403] New: [14 regression] sjames at gcc dot gnu.org 2024-03-20 10:44 ` [Bug tree-optimization/114403] [14 regression] LLVM miscompiled with -O3 -march=znver2 -fno-vect-cost-model sjames at gcc dot gnu.org 2024-03-20 10:53 ` sjames at gcc dot gnu.org 2024-03-20 11:49 ` rguenth at gcc dot gnu.org 2024-03-20 17:23 ` [Bug tree-optimization/114403] [14 regression] LLVM miscompiled with -O3 -march=znver2 -fno-vect-cost-model since r14-6822-g01f4251b8775c8 sjames at gcc dot gnu.org 2024-03-20 21:27 ` sjames at gcc dot gnu.org 2024-03-21 3:23 ` sjames at gcc dot gnu.org 2024-03-22 9:47 ` sjames at gcc dot gnu.org 2024-03-22 9:50 ` sjames at gcc dot gnu.org 2024-03-22 10:56 ` sjames at gcc dot gnu.org 2024-03-22 11:26 ` rguenth at gcc dot gnu.org 2024-03-22 12:36 ` law at gcc dot gnu.org 2024-03-22 13:12 ` sjames at gcc dot gnu.org 2024-03-22 13:13 ` sjames at gcc dot gnu.org 2024-03-22 13:13 ` sjames at gcc dot gnu.org 2024-03-22 13:27 ` sjames at gcc dot gnu.org 2024-03-22 13:50 ` rguenth at gcc dot gnu.org [this message] 2024-03-22 13:52 ` rguenth at gcc dot gnu.org 2024-03-22 14:27 ` sjames at gcc dot gnu.org 2024-03-22 14:37 ` sjames at gcc dot gnu.org 2024-03-26 10:09 ` rguenth at gcc dot gnu.org 2024-04-02 13:26 ` tnfchris at gcc dot gnu.org 2024-04-02 16:41 ` tnfchris at gcc dot gnu.org 2024-04-11 21:40 ` tnfchris at gcc dot gnu.org 2024-04-11 21:52 ` tnfchris at gcc dot gnu.org 2024-04-12 10:12 ` rguenth at gcc dot gnu.org 2024-04-12 10:15 ` tnfchris at gcc dot gnu.org 2024-04-12 10:37 ` rguenth at gcc dot gnu.org 2024-04-12 10:40 ` tnfchris at gcc dot gnu.org 2024-04-12 11:27 ` rguenth at gcc dot gnu.org 2024-04-15 11:07 ` cvs-commit at gcc dot gnu.org 2024-04-15 11:08 ` tnfchris at gcc dot gnu.org 2024-04-16 19:56 ` cvs-commit 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-114403-4-F9XPG01Dbr@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).