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: Mon, 29 Aug 2022 22:29:21 +0000 (GMT) [thread overview] Message-ID: <20220829222921.EAF15385382B@sourceware.org> (raw) https://gcc.gnu.org/g:ef43dc9a58980f86a5150b8d7f2b07cbcbaea7fb commit ef43dc9a58980f86a5150b8d7f2b07cbcbaea7fb Author: MS Automation <gnutools@microsoft.com> Date: Sun Aug 28 11:59:38 2022 +0000 Update xfail with new failures Diff: --- contrib/testsuite-management/x86_64-pc-linux-gnu.xfail | 15 ++++++++++++++- 1 file changed, 14 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 f81bf5b3531..b4df32bff5b 100644 --- a/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail +++ b/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail @@ -149,4 +149,17 @@ FAIL: gcc.dg/pr23911.c scan-tree-dump-times dce3 "__complex__ \\(1.0e\\+0, 0.0\\ FAIL: gcc.dg/pr56837.c scan-tree-dump-times optimized "memset ..c, 68, 16384.;" 1 XPASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for bogus messages, line 198) XPASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for bogus messages, line 198) -XPASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++20 (test for bogus messages, line 198) \ No newline at end of file +XPASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++20 (test for bogus messages, line 198) +FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++17 (test for excess errors) +FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++2a (test for excess errors) +FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++2b (test for excess errors) +FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++17 (test for excess errors) +FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++2a (test for excess errors) +FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++2b (test for excess errors) +FAIL: g++.dg/modules/xtreme-header_b.C -std=c++17 (test for excess errors) +FAIL: g++.dg/modules/xtreme-header_b.C -std=c++2a (test for excess errors) +FAIL: g++.dg/modules/xtreme-header_b.C -std=c++2b (test for excess errors) +FAIL: gcc.dg/tree-prof/cmpsf-1.c scan-tree-dump-not dom2 "Invalid sum" +FAIL: libstdc++-prettyprinters/48362.cc print t2 +FAIL: libstdc++-prettyprinters/cxx11.cc print rtpl +FAIL: libstdc++-prettyprinters/cxx11.cc print tpl \ No newline at end of file
next reply other threads:[~2022-08-29 22:29 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-29 22:29 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-07-21 21:40 Eugene Rozenfeld 2022-03-29 1:20 Eugene Rozenfeld 2022-01-19 22:54 Eugene Rozenfeld 2022-01-13 2: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=20220829222921.EAF15385382B@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).