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/96147] New: [11 regression] gcc.dg/vect/slp-43.c etc. FAIL Date: Fri, 10 Jul 2020 08:23:55 +0000 [thread overview] Message-ID: <bug-96147-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96147 Bug ID: 96147 Summary: [11 regression] gcc.dg/vect/slp-43.c etc. FAIL Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: rguenth at gcc dot gnu.org Target Milestone: --- Target: sparc-sun-solaris2.11 Created attachment 48855 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48855&action=edit 32-bit sparc-sun-solaris2.11 slp-43.c.163t.vect Between 20200708 (30fdaead5b7880c4e9f140618e26ad1c545642d5) and 20200709 (fab263ab0fc10ea08409b80afa7e8569438b8d28), a couple of testcases regressed on Solaris/SPARC, both 32 and 64-bit: +XPASS: gcc.dg/vect/bb-slp-32.c -flto -ffat-lto-objects scan-tree-dump slp2 "vectorization is not profitable" +XPASS: gcc.dg/vect/bb-slp-32.c scan-tree-dump slp2 "vectorization is not profitable" +XPASS: gcc.dg/vect/bb-slp-9.c -flto -ffat-lto-objects scan-tree-dump-times slp2 "basic block vectorized" 1 +XPASS: gcc.dg/vect/bb-slp-9.c scan-tree-dump-times slp2 "basic block vectorized" 1 +FAIL: gcc.dg/vect/slp-43.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorized 1 loops" 2 +FAIL: gcc.dg/vect/slp-43.c scan-tree-dump-times vect "vectorized 1 loops" 2 +FAIL: gcc.dg/vect/slp-45.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorized 1 loops" 13 +FAIL: gcc.dg/vect/slp-45.c scan-tree-dump-times vect "vectorized 1 loops" 13 There's a similar regression reported on ia64-suse-linux-gnu. Dumps for the FAILs attached.
next reply other threads:[~2020-07-10 8:23 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-10 8:23 ro at gcc dot gnu.org [this message] 2020-07-10 8:25 ` [Bug tree-optimization/96147] " ro at gcc dot gnu.org 2020-07-10 8:25 ` ro at gcc dot gnu.org 2020-10-16 11:57 ` rguenth at gcc dot gnu.org 2020-12-08 11:54 ` rguenth at gcc dot gnu.org 2020-12-08 12:21 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-01-15 12:51 ` cvs-commit at gcc dot gnu.org 2021-01-15 12:53 ` cvs-commit at gcc dot gnu.org 2021-01-15 13:05 ` cvs-commit at gcc dot gnu.org 2021-01-15 13:05 ` cvs-commit at gcc dot gnu.org 2021-01-15 13:06 ` rguenth at gcc dot gnu.org 2024-02-28 14:49 ` ro at gcc dot gnu.org 2024-02-28 14:49 ` ro at gcc dot gnu.org 2024-03-19 10:08 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-03-22 9:07 ` cvs-commit at gcc dot gnu.org 2024-03-22 9:12 ` 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-96147-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).