public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Backports of various patches to gcc 12 branch (mostly analyzer)
Date: Wed, 27 Jul 2022 18:04:10 -0400	[thread overview]
Message-ID: <37500a66f6c6295b590a2c5054901d0d9ad43187.camel@redhat.com> (raw)

I've backported the following patches to the releases/gcc-12 branch:

r12-8631-g1321183a13540b:
  "analyzer: add .fpath.txt dumps to -fdump-analyzer-feasibility"
    from r13-6-gd8586b00dd00a1783862da5f0c8811a740400074

r12-8632-g05530fcea07a9e:
  "analyzer: handle repeated accesses after init of unknown size [PR105285]"
     from r13-7-g00c4405cd7f6a144d0a439e4d848d246920e6ff3

r12-8633-g1d38fa564edeae:
  "analyzer: fix memory leaks"
     from r13-334-g99988b0e8b57b3

r12-8634-g6fd39b06042012:
  "json: fix escaping of '\'"
     from r13-965-g4f9ad0b4b0a8c7

r12-8635-g4eac9fa087f4ef:
  "analyzer: add more uninit test coverage"
     from r13-1116-g44681d45473883

r12-8636-g9fa11419ef59fd:
  "analyzer: show saved diagnostics as nodes in .eg.dot dumps"
     from r13-1117-gc540077a3bf600

r12-8637-g09cb9c88ef8e2c:
  "analyzer: fix uninit false positive with -ftrivial-auto-var-init= [PR106204]"
     from r13-1517-gb33dd7874523af

r12-8638-g71a4f739c21874:
  "analyzer: fix false positives from -Wanalyzer-tainted-divisor [PR106225]"
     from r13-1562-g897b3b31f0a94b

r12-8639-g7455e982f09832:
  "analyzer: fix stray get_element decls"
     from r13-1847-g0460ba622e833d


Dave


                 reply	other threads:[~2022-07-27 22:04 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=37500a66f6c6295b590a2c5054901d0d9ad43187.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc-patches@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).