From: Jan Hubicka <hubicka@ucw.cz>
To: Jan Hubicka <hubicka@ucw.cz>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Make devirtualization use BINFO_VTABLE instead of BINFO_VIRTUALS
Date: Fri, 02 Sep 2011 13:43:00 -0000 [thread overview]
Message-ID: <20110902134301.GB28349@kam.mff.cuni.cz> (raw)
In-Reply-To: <20110902133854.GC21553@virgil.arch.suse.de>
> Hi,
>
> On Thu, Sep 01, 2011 at 08:52:30PM +0200, Jan Hubicka wrote:
> > > - Nevertheless, this method of devirtualization cannot automatically
> > > de-thunkize this-adjusting thunks and newly direct calls to them
> > > cannot be inlined because the inliner does not have this capability
> > > now. This is in fact a regression from 4.6, and testcases
> > > ivinline-7.C and ivinline-9.C had to be XFAILed exactly for this
> > > reason. The size of the memory savings and the fact that we do not
> > > devirtualize that much now make this an acceptable tradeoff, though.
> >
> > OK, the "dethunkization" was ugly anyway. I guess we will need to add support
> > for handling thunks in inliner but that can go incrementally.
>
> Do we actually have the offsets and indices necessary for
> de-thunkization available somewhere in the middle end structures (with
> BINFO_VIRTUALs being freed in free_lang_data now)?
They live in cgraph, at least for thunks that has been finalized in current compilation
unit. I wonder how much we care about de-thunkizing calls into other compilation unit,
but then C++ FE can just add the thunks into callgraph, too.
Honza
prev parent reply other threads:[~2011-09-02 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 17:48 Martin Jambor
2011-09-01 18:52 ` Jan Hubicka
2011-09-02 8:58 ` Richard Guenther
2011-09-02 13:39 ` Martin Jambor
2011-09-02 13:43 ` 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=20110902134301.GB28349@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--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).