public inbox for jit@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>, jit@gcc.gnu.org
Subject: Backports to gcc 11 branch (analyzer and jit)
Date: Fri, 02 Jul 2021 15:27:05 -0400	[thread overview]
Message-ID: <373a35eaf158a25f062e297a1dd2e9bdaf8d0ba2.camel@redhat.com> (raw)

I've cherrypicked the following commits from trunk to the gcc 11
branch:
      analyzer: fix ICE on NULL change.m_expr [PR100244]
      analyzer: fix missing leak after call to strsep [PR100615]
      diagnostic-show-locus: tweak rejection logic
      analyzer: show types for poisoned_svalue and compound_svalue
      analyzer: remove unused prototypes
      analyzer: remove redundant typedef
      analyzer: split out struct bit_range from class concrete_binding
      analyzer: fix region::get_bit_size for bitfields
      analyzer: bitfield fixes [PR99212]
      analyzer: make various region_model member functions const
      analyzer: tweak priority of callstrings in worklist::key_t::cmp
      analyzer: fix bitfield endianness issues [PR99212,PR101082]
      analyzer: add region_model_manager::get_or_create_int_cst
      analyzer: fix issue with symbolic reads with concrete bindings
      jit: fix test-asm failures on i?86
      jit: fix test-vector-* failures

Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to releases/gcc-11 as 1187f297f7ef6a3dc86103b642d463f7a7bd6096
through d731870cb2aa23d2a753a2703410cef98ced3872.


Dave


                 reply	other threads:[~2021-07-02 19:27 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=373a35eaf158a25f062e297a1dd2e9bdaf8d0ba2.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jit@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).