public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93355] Missing diagnostic for missing fclose in intl/localealias.c
Date: Thu, 24 Sep 2020 01:26:32 +0000	[thread overview]
Message-ID: <bug-93355-4-daUEDZOeIZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93355-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93355

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:

https://gcc.gnu.org/g:6b828f69519a50e6e2961b62ea552bf89d287199

commit r11-3415-g6b828f69519a50e6e2961b62ea552bf89d287199
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Thu Dec 19 16:15:09 2019 -0500

    analyzer: add testcases for PR 93355 (intl/localealias.c leak)

    PR analyzer/93355 reports a missing diagnostic about a FILE leak in
    intl/localealias.c.  This appears to be due to a issue in the
    feasibility-checking code, though there is also a state explosion.

    This patch adds test cases that I've been using when investigating this,
    two of them currently requiring -fno-analyzer-feasibility, and one
    currently requiring -Wno-analyzer-too-complex.

    gcc/testsuite/ChangeLog:
            PR analyzer/93355
            * gcc.dg/analyzer/pr93355-localealias-feasibility.c: New test.
            * gcc.dg/analyzer/pr93355-localealias-simplified.c: New test.
            * gcc.dg/analyzer/pr93355-localealias.c: New test.

  parent reply	other threads:[~2020-09-24  1:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93355-4@http.gcc.gnu.org/bugzilla/>
2020-09-21 22:49 ` cvs-commit at gcc dot gnu.org
2020-09-24  1:26 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-26 21:33 ` dmalcolm at gcc dot gnu.org
2021-02-02  2:53 ` cvs-commit at gcc dot gnu.org
2021-02-02  2:55 ` cvs-commit at gcc dot gnu.org
2021-02-02 14:38 ` dmalcolm at gcc dot gnu.org
2021-03-04  0:27 ` dmalcolm at gcc dot gnu.org
2021-03-05 23:54 ` dmalcolm at gcc dot gnu.org
2021-03-11 22:48 ` cvs-commit at gcc dot gnu.org
2021-03-11 23:18 ` dmalcolm at gcc dot gnu.org
2021-03-12 20:10 ` [Bug analyzer/93355] Analyzer -Wanalysis-too-complex on intl/localealias.c due to poor call summarization dmalcolm at gcc dot gnu.org

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=bug-93355-4-daUEDZOeIZ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).