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 with new failures.
Date: Thu, 27 Apr 2023 01:03:52 +0000 (GMT)	[thread overview]
Message-ID: <20230427010352.04ACB3858C36@sourceware.org> (raw)

https://gcc.gnu.org/g:81deaed9eaf1dd07947cdf7881aeda45b5088cf0

commit 81deaed9eaf1dd07947cdf7881aeda45b5088cf0
Author: Eugene Rozenfeld <erozen@microsoft.com>
Date:   Wed Apr 26 17:59:01 2023 -0700

    Update with new failures.

Diff:
---
 contrib/testsuite-management/x86_64-pc-linux-gnu.xfail | 5 ++++-
 1 file changed, 4 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 54940fe42d9..0383089ec3e 100644
--- a/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail
+++ b/contrib/testsuite-management/x86_64-pc-linux-gnu.xfail
@@ -183,4 +183,7 @@ FAIL: gcc.target/i386/pr89618.c scan-tree-dump vect "LOOP VECTORIZED"
 FAIL: gcc.dg/mla_1.c (test for excess errors)
 UNRESOLVED: g++.dg/cpp2a/concepts-lambda3.C -std=c++14 compilation failed to produce executable
 UNRESOLVED: g++.dg/cpp2a/concepts-lambda3.C -std=c++17 compilation failed to produce executable
-UNRESOLVED: g++.dg/cpp2a/concepts-lambda3.C -std=c++98 compilation failed to produce executable
\ No newline at end of file
+UNRESOLVED: g++.dg/cpp2a/concepts-lambda3.C -std=c++98 compilation failed to produce executable
+FAIL: std/time/time_zone/get_info_local.cc execution test
+FAIL: gcc.dg/analyzer/file-CWE-1341-example.c (test for excess errors)
+FAIL: gcc.dg/analyzer/pipe-glibc.c (test for excess errors)
\ No newline at end of file

                 reply	other threads:[~2023-04-27  1:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230427010352.04ACB3858C36@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: link
Be 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).