public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6465] testsuite: remove XFAIL in gcc.dg/analyzer/pr99716-1.c [PR108988]
Date: Fri,  3 Mar 2023 22:48:23 +0000 (GMT)	[thread overview]
Message-ID: <20230303224823.C7271385559E@sourceware.org> (raw)

https://gcc.gnu.org/g:d3ef73867e3f70a343ad5aa4e00b270be85fa572

commit r13-6465-gd3ef73867e3f70a343ad5aa4e00b270be85fa572
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Fri Mar 3 17:48:04 2023 -0500

    testsuite: remove XFAIL in gcc.dg/analyzer/pr99716-1.c [PR108988]
    
    Jakub's r13-6441-gdbeccab7a1f5dc fix for PR tree-optimization/108988
    has fixed this failing analyzer test.
    
    gcc/testsuite/ChangeLog:
            PR tree-optimization/108988
            * gcc.dg/analyzer/pr99716-1.c (test_2): Remove xfail.
    
    Signed-off-by: David Malcolm <dmalcolm@redhat.com>

Diff:
---
 gcc/testsuite/gcc.dg/analyzer/pr99716-1.c | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/analyzer/pr99716-1.c b/gcc/testsuite/gcc.dg/analyzer/pr99716-1.c
index 4fae368f321..2ccdcc73a5c 100644
--- a/gcc/testsuite/gcc.dg/analyzer/pr99716-1.c
+++ b/gcc/testsuite/gcc.dg/analyzer/pr99716-1.c
@@ -27,11 +27,7 @@ test_2 (void)
     FILE *fp = fopen ("/tmp/test", "w");
     fprintf (fp, "hello");
   }
-} /* { dg-warning "leak of FILE 'fp'" "" { xfail *-*-* } } */
-/* TODO: fails on some targets due to fprintf call being optimized to
-   __builtin_fwrite with a size argument (idx 2) that fails
-   gimple_builtin_call_types_compatible_p, and thus the known_function
-   for __builtin_fwrite not being used (PR middle-end/108988).  */
+} /* { dg-warning "leak of FILE 'fp'" } */
 
 FILE *fp3;

                 reply	other threads:[~2023-03-03 22:48 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=20230303224823.C7271385559E@sourceware.org \
    --to=dmalcolm@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).