public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/66896] ipa-prop.c:2479 runtime error: member call on null pointer of type 'struct ipa_polymorphic_call_context'
Date: Fri, 24 Jul 2015 11:34:00 -0000	[thread overview]
Message-ID: <bug-66896-4-3XuwDVZxNX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66896-4@http.gcc.gnu.org/bugzilla/>

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

Martin Jambor <jamborm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jamborm at gcc dot gnu.org

--- Comment #7 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to Vittorio Zecca from comment #6)
> I just found the same issue at line 2479:

As even the the gcc-5 branch is changing slightly, line numbers on
their own are not are not the best indicator of the position of the
code you refer to.

> dst_ctx->combine_with (ctx);
> dst_ctx is again NULL
> Maybe the same patch should be applied here? Namely:
> if (!dst_ctx)
>                         {
>                           vec_safe_grow_cleared
> (args->polymorphic_call_contexts,
>                                                  count);
>                           dst_ctx =
> ipa_get_ith_polymorhic_call_context (args, i);
>                         }
> immediately before?

I have looked at both occurrences of dst_ctx->combine_with (ctx) in
function update_jump_functions_after_inlining and they are all
guarded with the code just as you describe.

> Do you need a reproducer?

Yes please, I cannot see the error you describe.  Thanks.


  parent reply	other threads:[~2015-07-24 11:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16  8:11 [Bug c++/66896] New: " zeccav at gmail dot com
2015-07-16  9:37 ` [Bug ipa/66896] " marxin at gcc dot gnu.org
2015-07-16 14:48 ` marxin at gcc dot gnu.org
2015-07-16 14:53 ` marxin at gcc dot gnu.org
2015-07-17  6:36 ` zeccav at gmail dot com
2015-07-23  8:28 ` zeccav at gmail dot com
2015-07-24 11:34 ` jamborm at gcc dot gnu.org [this message]
2015-07-24 14:02 ` zeccav at gmail dot com
2015-07-24 14:03 ` zeccav at gmail dot com
2015-07-24 16:08 ` jamborm at gcc dot gnu.org
2015-07-24 17:24 ` zeccav at gmail dot com
2015-08-05 15:56 ` marxin at gcc dot gnu.org
2015-08-06  6:24 ` zeccav at gmail dot com

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-66896-4-3XuwDVZxNX@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).