public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-4254] Grow non_null_ref bitmap when num_ssa_names increases.
Date: Fri,  8 Oct 2021 14:36:57 +0000 (GMT)	[thread overview]
Message-ID: <20211008143657.1B8233857C56@sourceware.org> (raw)

https://gcc.gnu.org/g:946486ab4f84a5380e1a18e37e4fb9614f5d7992

commit r12-4254-g946486ab4f84a5380e1a18e37e4fb9614f5d7992
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Fri Oct 8 15:42:42 2021 +0200

    Grow non_null_ref bitmap when num_ssa_names increases.
    
    The strlen pass changes the IL as it works with the ranger.  This
    causes the non_null_ref code to sometimes get asked questions about new
    SSA names.
    
    Tested on x86-64 Linux.
    
    gcc/ChangeLog:
    
            * gimple-range-cache.cc (non_null_ref::non_null_deref_p): Grow
            bitmap if needed.

Diff:
---
 gcc/gimple-range-cache.cc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gcc/gimple-range-cache.cc b/gcc/gimple-range-cache.cc
index 7d994798e52..9cbc63d8a40 100644
--- a/gcc/gimple-range-cache.cc
+++ b/gcc/gimple-range-cache.cc
@@ -61,6 +61,9 @@ non_null_ref::non_null_deref_p (tree name, basic_block bb, bool search_dom)
     return false;
 
   unsigned v = SSA_NAME_VERSION (name);
+  if (v >= m_nn.length ())
+    m_nn.safe_grow_cleared (num_ssa_names + 1);
+
   if (!m_nn[v])
     process_name (name);


                 reply	other threads:[~2021-10-08 14:36 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=20211008143657.1B8233857C56@sourceware.org \
    --to=aldyh@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).