From: Jan Hubicka <hubicka@ucw.cz>
To: Ilya Enkovich <enkovich.gnu@gmail.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: ipa-cp heuristic tweek
Date: Fri, 03 Apr 2015 16:58:00 -0000 [thread overview]
Message-ID: <20150403165756.GK21276@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <CAMbmDYb7VkT0u8DaXogHksPZXXWH2aPCnDmcnN1m8KVYEF=RxA@mail.gmail.com>
> 2015-03-31 15:32 GMT+03:00 Ilya Enkovich <enkovich.gnu@gmail.com>:
> > 2015-03-29 18:43 GMT+03:00 Jan Hubicka <hubicka@ucw.cz>:
> >> +static bool
> >> +set_single_call_flag (cgraph_node *node, void *)
> >> +{
> >> + cgraph_edge *cs = node->callers;
> >> + /* Local thunks can be handled transparently, skip them. */
> >> + while (cs && cs->caller->thunk.thunk_p && cs->caller->local.local)
> >> + cs = cs->next_caller;
> >> + if (cs)
> >> + {
> >> + gcc_assert (!cs->next_caller);
> >
> > This assert assumes the only non-thunk caller is always at the end of
> > a callers list. Is it actually guaranteed?
> >
> >> + IPA_NODE_REF (cs->caller)->node_calling_single_call = true;
> >> + return true;
> >> + }
> >> + return false;
> >> +}
> >> +
> >> /* Initialize ipcp_lattices. */
> >
> >
> > Thanks,
> > Ilya
>
> Hi Honza,
>
> For chkp testing I see cases when gcc asserts in set_single_call_flag
> because instrumentation thunk is not the last one in a callers list. I
> want to install following patch to fix it. Is it OK?
>
> Thanks,
> Ilya
> --
> 2015-04-03 Ilya Enkovich <ilya.enkovich@intel.com>
>
> * ipa-cp (set_single_call_flag): Remove too
> restrictive assert.
OK (this is probably artifact of earlier version of the code, thanks for pointing
it out)
Honza
prev parent reply other threads:[~2015-04-03 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 15:43 Jan Hubicka
2015-03-30 12:11 ` Martin Jambor
2015-03-30 17:05 ` Jan Hubicka
2015-03-31 12:32 ` Ilya Enkovich
2015-04-03 16:33 ` Ilya Enkovich
2015-04-03 16:58 ` Jan Hubicka [this message]
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=20150403165756.GK21276@atrey.karlin.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=enkovich.gnu@gmail.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).