public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102954] New: [12 regression] gcc.dg/vect/pr33804.c XPASSes Date: Tue, 26 Oct 2021 17:04:08 +0000 [thread overview] Message-ID: <bug-102954-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102954 Bug ID: 102954 Summary: [12 regression] gcc.dg/vect/pr33804.c XPASSes Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org Target Milestone: --- Target: sparc*-sun-solaris2.11, armeb-none-linux-gnueabihf Between 20210806 fd351c76c23187fdc74d9af6874a54e2e84c4d25() and 20210807 (f92f47785201d44cef91e2c4a9742fb503ce5316), gcc.dg/vect/pr33804.c began to XPASS on 64-bit Solaris/SPARC and armeb-*: XPASS: gcc.dg/vect/pr33804.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorized 1 loops" 1 XPASS: gcc.dg/vect/pr33804.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorizing stmts using SLP" 1 XPASS: gcc.dg/vect/pr33804.c scan-tree-dump-times vect "vectorized 1 loops" 1 XPASS: gcc.dg/vect/pr33804.c scan-tree-dump-times vect "vectorizing stmts using SLP" 1
next reply other threads:[~2021-10-26 17:04 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-26 17:04 ro at gcc dot gnu.org [this message] 2021-10-26 17:16 ` [Bug tree-optimization/102954] " ro at gcc dot gnu.org 2021-10-27 7:16 ` [Bug testsuite/102954] " rguenth at gcc dot gnu.org 2021-10-27 10:44 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-05-06 8:31 ` [Bug testsuite/102954] [12/13 " jakub at gcc dot gnu.org 2023-05-08 12:22 ` [Bug testsuite/102954] [12/13/14 " rguenth at gcc dot gnu.org 2024-02-28 15:17 ` ro at gcc dot gnu.org 2024-02-28 15:17 ` ro at gcc dot gnu.org 2024-05-22 11:42 ` [Bug testsuite/102954] [12/13/14/15 " ro 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-102954-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).