public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Eugene Rozenfeld <erozen@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/microsoft/heads/main)] Update xfail with new failures Date: Thu, 13 Jan 2022 02:54:17 +0000 (GMT) [thread overview] Message-ID: <20220113025417.4B35A3858D39@sourceware.org> (raw) https://gcc.gnu.org/g:4bc15d2236b405797fb61f4ea9fe553eb33331a2 commit 4bc15d2236b405797fb61f4ea9fe553eb33331a2 Author: MS Automation <gnutools@microsoft.com> Date: Tue Jan 11 09:46:10 2022 +0000 Update xfail with new failures Diff: --- .../testsuite-management/x86_64-pc-linux-gnu.xfail | 23 +++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail b/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail index fbf96246137..ffa5fbd6e7d 100644 --- a/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail +++ b/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail @@ -242,4 +242,25 @@ FAIL: gcc.dg/guality/pr54200.c -Og -DPREVENT_OPTIMIZATION line 20 z == 3 UNRESOLVED: gcc.dg/tree-ssa/ssa-dom-thread-7.c scan-tree-dump-not vrp-thread2 "Jumps threaded" XPASS: gcc.dg/guality/ipa-sra-1.c -O0 line 15 k == 3 XPASS: gcc.dg/guality/ipa-sra-1.c -O1 -DPREVENT_OPTIMIZATION line 15 k == 3 -XPASS: gcc.dg/guality/ipa-sra-1.c -Og -DPREVENT_OPTIMIZATION line 15 k == 3 \ No newline at end of file +XPASS: gcc.dg/guality/ipa-sra-1.c -Og -DPREVENT_OPTIMIZATION line 15 k == 3 +FAIL: g++.dg/vect/pr92595.cc -std=c++14 (internal compiler error: in operator[], at vec.h:889) +FAIL: g++.dg/vect/pr92595.cc -std=c++14 (test for excess errors) +FAIL: g++.dg/vect/pr92595.cc -std=c++17 (internal compiler error: in operator[], at vec.h:889) +FAIL: g++.dg/vect/pr92595.cc -std=c++17 (test for excess errors) +FAIL: g++.dg/vect/pr92595.cc -std=c++2a (internal compiler error: in operator[], at vec.h:889) +FAIL: g++.dg/vect/pr92595.cc -std=c++2a (test for excess errors) +FAIL: gcc.dg/guality/pr43051-1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions -DPREVENT_OPTIMIZATION line 34 c == &a[0] +FAIL: gcc.dg/guality/pr43051-1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions -DPREVENT_OPTIMIZATION line 39 c == &a[0] +FAIL: gcc.dg/vect/vect-tail-nomask-1.c -flto -ffat-lto-objects scan-tree-dump-times vect "LOOP EPILOGUE VECTORIZED \\(MODE=V16QI\\)" 2 +FAIL: gcc.dg/vect/vect-tail-nomask-1.c scan-tree-dump-times vect "LOOP EPILOGUE VECTORIZED \\(MODE=V16QI\\)" 2 +FAIL: gcc.target/i386/pr88531-1b.c scan-assembler-times vgatherqpd 4 +FAIL: gcc.target/i386/pr88531-1b.c scan-assembler-times vmulpd 4 +FAIL: gcc.target/i386/pr88531-1c.c scan-assembler-times vgatherqpd 4 +FAIL: gcc.target/i386/pr88531-1c.c scan-assembler-times vmulpd 4 +FAIL: gcc.target/i386/pr88531-2b.c scan-assembler-times vmulps 2 +FAIL: gcc.target/i386/pr88531-2c.c scan-assembler-times vmulps 2 +FAIL: gcc.target/i386/pr94494.c (internal compiler error: in operator[], at vec.h:889) +FAIL: gcc.target/i386/pr94494.c (test for excess errors) +FAIL: gcc.target/i386/vect-reduc-1.c scan-assembler-times padd 5 +FAIL: gcc.target/i386/vect-reduc-1.c scan-tree-dump vect "LOOP EPILOGUE VECTORIZED" +FAIL: maintainers-verify.sh \ No newline at end of file
next reply other threads:[~2022-01-13 2:54 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-13 2:54 Eugene Rozenfeld [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-08-21 23:57 Eugene Rozenfeld 2024-02-21 3:04 Eugene Rozenfeld 2023-11-20 21:52 Eugene Rozenfeld 2023-09-19 6:43 Eugene Rozenfeld 2023-06-27 21:21 Eugene Rozenfeld 2023-04-27 23:29 Eugene Rozenfeld 2023-03-14 6:18 Eugene Rozenfeld 2023-01-27 1:32 Eugene Rozenfeld 2022-12-08 1:26 Eugene Rozenfeld 2022-11-12 2:23 Eugene Rozenfeld 2022-10-16 0:28 Eugene Rozenfeld 2022-10-02 7:13 Eugene Rozenfeld 2022-09-23 1:22 Eugene Rozenfeld 2022-08-29 22:29 Eugene Rozenfeld 2022-07-21 21:40 Eugene Rozenfeld 2022-03-29 1:20 Eugene Rozenfeld 2022-01-19 22:54 Eugene Rozenfeld 2021-11-10 4:29 Eugene Rozenfeld 2021-10-23 0:10 Eugene Rozenfeld
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=20220113025417.4B35A3858D39@sourceware.org \ --to=erozen@gcc.gnu.org \ --cc=gcc-cvs@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).