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: Sat, 23 Oct 2021 00:10:53 +0000 (GMT) [thread overview] Message-ID: <20211023001053.8AFE93857827@sourceware.org> (raw) https://gcc.gnu.org/g:98abe025c6b18a5deb1ea9e1079fcdd0ab039704 commit 98abe025c6b18a5deb1ea9e1079fcdd0ab039704 Author: MS Automation <gnutools@microsoft.com> Date: Thu Oct 21 11:37:19 2021 +0000 Update xfail with new failures Diff: --- .../testsuite-management/x86_64-pc-linux-gnu.xfail | 21 ++++++++++++++++++++- 1 file changed, 20 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 e2e2a771a10..4fb7919e273 100644 --- a/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail +++ b/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail @@ -220,4 +220,23 @@ FAIL: libgomp.c/scan-21.c scan-tree-dump-times vect "vectorized [2-6] loops" 2 FAIL: libgomp.c/scan-22.c scan-tree-dump-times vect "vectorized [2-6] loops" 2 FAIL: libgomp.graphite/force-parallel-8.c scan-tree-dump-times graphite "5 loops carried no dependency" 1 UNRESOLVED: g++.dg/tsan/pthread_cond_clockwait.C -O0 compilation failed to produce executable -UNRESOLVED: g++.dg/tsan/pthread_cond_clockwait.C -O2 compilation failed to produce executable \ No newline at end of file +UNRESOLVED: g++.dg/tsan/pthread_cond_clockwait.C -O2 compilation failed to produce executable +FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++2a (internal compiler error) +FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++2a (test for excess errors) +FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++2b (internal compiler error) +FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++2b (test for excess errors) +FAIL: g++.dg/modules/xtreme-header-5_a.H module-cmi (gcm.cache/$srcdir/g++.dg/modules/xtreme-header-5_a.H.gcm) +FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++2a (test for excess errors) +FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++2b (test for excess errors) +FAIL: g++.dg/modules/xtreme-header-5_c.C -std=c++2a (test for excess errors) +FAIL: g++.dg/modules/xtreme-header-5_c.C -std=c++2b (test for excess errors) +FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++14 scan-tree-dump-not optimized "goto" +FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++14 (test for excess errors) +FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++17 scan-tree-dump-not optimized "goto" +FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++17 (test for excess errors) +FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++2a scan-tree-dump-not optimized "goto" +FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++2a (test for excess errors) +FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++98 scan-tree-dump-not optimized "goto" +FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++98 (test for excess errors) +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" \ No newline at end of file
next reply other threads:[~2021-10-23 0:10 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-23 0:10 Eugene Rozenfeld [this message] 2021-11-10 4:29 Eugene Rozenfeld 2022-01-13 2:54 Eugene Rozenfeld 2022-01-19 22:54 Eugene Rozenfeld 2022-03-29 1:20 Eugene Rozenfeld 2022-07-21 21:40 Eugene Rozenfeld 2022-08-29 22:29 Eugene Rozenfeld 2022-09-23 1:22 Eugene Rozenfeld 2022-10-02 7:13 Eugene Rozenfeld 2022-10-16 0:28 Eugene Rozenfeld 2022-11-12 2:23 Eugene Rozenfeld 2022-12-08 1:26 Eugene Rozenfeld 2023-01-27 1:32 Eugene Rozenfeld 2023-03-14 6:18 Eugene Rozenfeld 2023-04-27 23:29 Eugene Rozenfeld 2023-06-27 21:21 Eugene Rozenfeld 2023-09-19 6:43 Eugene Rozenfeld 2023-11-20 21:52 Eugene Rozenfeld 2024-02-21 3:04 Eugene Rozenfeld 2024-08-21 23:57 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=20211023001053.8AFE93857827@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).