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: Wed, 19 Jan 2022 22:54:45 +0000 (GMT) [thread overview] Message-ID: <20220119225445.4A30E3857C66@sourceware.org> (raw) https://gcc.gnu.org/g:0e8fc2610ebdfafccfd3b9421a8dc1896c716c9a commit 0e8fc2610ebdfafccfd3b9421a8dc1896c716c9a Author: MS Automation <gnutools@microsoft.com> Date: Wed Jan 19 10:12:58 2022 +0000 Update xfail with new failures Diff: --- contrib/testsuite-management/x86_64-pc-linux-gnu.xfail | 13 ++++++++++++- 1 file changed, 12 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 ffa5fbd6e7d..f766a124abb 100644 --- a/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail +++ b/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail @@ -263,4 +263,15 @@ FAIL: gcc.target/i386/pr94494.c (internal compiler error: in operator[], at vec. 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 +FAIL: maintainers-verify.sh +ERROR: g++.dg/gcov/gcov-17.C : error executing dg-final: can't read "script": no such variable +ERROR: g++.dg/gcov/pr98273.C : error executing dg-final: can't read "script": no such variable +FAIL: g++.dg/asan/asan_test.C -O2 (test for excess errors) +FAIL: g++.dg/cpp0x/constexpr-compare2.C -std=c++14 (test for excess errors) +FAIL: g++.dg/cpp0x/constexpr-compare2.C -std=c++17 (test for excess errors) +FAIL: g++.dg/cpp0x/constexpr-compare2.C -std=c++20 (test for excess errors) +FAIL: g++.dg/warn/pr104025.C -std=gnu++14 (test for excess errors) +FAIL: g++.dg/warn/pr104025.C -std=gnu++17 (test for excess errors) +FAIL: g++.dg/warn/pr104025.C -std=gnu++20 (test for excess errors) +FAIL: g++.dg/warn/pr104025.C -std=gnu++98 (test for excess errors) +UNRESOLVED: g++.dg/asan/asan_test.C -O2 compilation failed to produce executable \ No newline at end of file
next reply other threads:[~2022-01-19 22:54 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-19 22: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-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=20220119225445.4A30E3857C66@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).