public inbox for gcc-regression@sourceware.org help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@sc.intel.com> To: skpgkp2@gmail.com, hjl.tools@gmail.com, gcc-regression@gcc.gnu.org Subject: Regressions on native/releases/gcc-11 at commit r11-10173 vs commit r11-10152 on Linux/x86_64 Date: Sun, 24 Jul 2022 23:23:32 -0700 [thread overview] Message-ID: <20220725062332.597153E001E@gnu-clx-1.sc.intel.com> (raw) New failures: FAIL: gcc.dg/vect/pr103116-1.c -flto -ffat-lto-objects scan-tree-dump vect "Data access with gaps requires scalar epilogue loop" FAIL: gcc.dg/vect/pr103116-1.c -flto -ffat-lto-objects scan-tree-dump vect "Data access with gaps requires scalar epilogue loop" FAIL: gcc.dg/vect/pr103116-1.c -flto -ffat-lto-objects scan-tree-dump vect "Data access with gaps requires scalar epilogue loop" FAIL: gcc.dg/vect/pr103116-1.c scan-tree-dump vect "Data access with gaps requires scalar epilogue loop" FAIL: gcc.dg/vect/pr103116-1.c scan-tree-dump vect "Data access with gaps requires scalar epilogue loop" FAIL: gcc.dg/vect/pr103116-1.c scan-tree-dump vect "Data access with gaps requires scalar epilogue loop" FAIL: gcc.dg/vect/slp-perm-12.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorizing stmts using SLP" 1 FAIL: gcc.dg/vect/slp-perm-12.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorizing stmts using SLP" 1 FAIL: gcc.dg/vect/slp-perm-12.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorizing stmts using SLP" 1 FAIL: gcc.dg/vect/slp-perm-12.c scan-tree-dump-times vect "vectorizing stmts using SLP" 1 FAIL: gcc.dg/vect/slp-perm-12.c scan-tree-dump-times vect "vectorizing stmts using SLP" 1 FAIL: gcc.dg/vect/slp-perm-12.c scan-tree-dump-times vect "vectorizing stmts using SLP" 1 New passes:
reply other threads:[~2022-07-25 6:23 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220725062332.597153E001E@gnu-clx-1.sc.intel.com \ --to=hjl@sc.intel.com \ --cc=gcc-regression@gcc.gnu.org \ --cc=hjl.tools@gmail.com \ --cc=skpgkp2@gmail.com \ /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).