public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113167] New: [14 Regression] gcc.dg/tree-ssa/gen-vect-26.c started failing many targets after recent change Date: Fri, 29 Dec 2023 03:55:33 +0000 [thread overview] Message-ID: <bug-113167-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113167 Bug ID: 113167 Summary: [14 Regression] gcc.dg/tree-ssa/gen-vect-26.c started failing many targets after recent change Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: law at gcc dot gnu.org Target Milestone: --- Many targets are now seeing this failure: FAIL: gcc.dg/tree-ssa/gen-vect-26.c scan-tree-dump-times vect "Alignment of access forced using peeling" 1 Which has been bisected to: commit 01f4251b8775c832a92d55e2df57c9ac72eaceef (HEAD) Author: Tamar Christina <tamar.christina@arm.com> Date: Sun Dec 24 19:18:12 2023 +0000 middle-end: Support vectorization of loops with multiple exits. Hi All, This patch adds initial support for early break vectorization in GCC. In other words it implements support for vectorization of loops with multiple exits. The support is added for any target that implements a vector cbranch optab, this includes both fully masked and non-masked targets. [ ... ] The regression is seen on just about every cross target I'm testing. So just to pick one, fr30-elf. Since this is a scan failure, you don't need a full toolchain to reproduce, just the compiler proper.
next reply other threads:[~2023-12-29 3:55 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-29 3:55 law at gcc dot gnu.org [this message] 2023-12-29 4:22 ` [Bug testsuite/113167] " pinskia at gcc dot gnu.org 2023-12-29 4:24 ` pinskia at gcc dot gnu.org 2023-12-29 4:40 ` pinskia at gcc dot gnu.org 2023-12-29 4:50 ` cvs-commit at gcc dot gnu.org 2023-12-29 4:51 ` pinskia at gcc dot gnu.org 2023-12-29 8:40 ` tnfchris at gcc dot gnu.org 2023-12-29 16:29 ` law 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-113167-4@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).