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, 12 Nov 2022 02:23:45 +0000 (GMT) [thread overview] Message-ID: <20221112022345.EECE23858025@sourceware.org> (raw) https://gcc.gnu.org/g:d029af1dbe6b827021c3f0b91982a657537519de commit d029af1dbe6b827021c3f0b91982a657537519de Author: MS Automation <gnutools@microsoft.com> Date: Fri Nov 11 11:52:16 2022 +0000 Update xfail with new failures Diff: --- contrib/testsuite-management/x86_64-pc-linux-gnu.xfail | 6 +++++- 1 file changed, 5 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 596bd8b80d3..e41be8a9662 100644 --- a/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail +++ b/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail @@ -172,4 +172,8 @@ FAIL: c-c++-common/goacc/struct-component-kind-1.c -std=c++17 at line 68 (test FAIL: c-c++-common/goacc/struct-component-kind-1.c -std=c++20 at line 68 (test for errors, line 67) FAIL: c-c++-common/goacc/struct-component-kind-1.c -std=c++98 at line 68 (test for errors, line 67) FAIL: c-c++-common/goacc/struct-component-kind-1.c at line 68 (test for errors, line 67) -FAIL: gcc.dg/tree-ssa/forwprop-19.c scan-tree-dump-not forwprop1 "VEC_PERM_EXPR" \ No newline at end of file +FAIL: gcc.dg/tree-ssa/forwprop-19.c scan-tree-dump-not forwprop1 "VEC_PERM_EXPR" +FAIL: g++.dg/pr71488.C (test for excess errors) +FAIL: gcc.dg/guality/pr54693-2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 21 x == 10 - i +FAIL: gcc.dg/guality/pr54693-2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 21 y == 20 - 2 * i +FAIL: gcc.dg/guality/pr54693-2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 21 z == 30 - 3 * i \ No newline at end of file
next reply other threads:[~2022-11-12 2:23 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-12 2:23 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-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 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=20221112022345.EECE23858025@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).